Pascal 🆙 retweeted
Next week is shipping week, a lot of product updates will be released for LUKSO and Universal Profiles! 🚢 🚢
Pascal 🆙 retweeted
LUKSO Community Update | Universal Profiles & What’s Next xitter.cf/i/broadcasts/1yxBePnWQ…
Pascal 🆙 retweeted
👀 @LUKSO_io @ERC725Account Profiles are built exactly for that kind of agentic future.🤯
@CryptoHayes told @binance that the network AI agents settle on will be
“the most valuable network ever created,”
with “trillions of agents all doing transactions at the speed of light.”
@LUKSO_io has been positioning its Universal Profiles as the on-chain account and identity layer for agents.
A Universal Profile is a smart contract account (LSP0 / ERC725), not a normal externally owned account (EOA) controlled by a single private key.
Key features that make them agent-friendly:
🖋Fine-grained, revocable permissions (LSP6 Key Manager)
You give an agent a controller key with tightly scoped rights (specific functions, targets, value transfers, etc.).
You can revoke or restrict it anytime without moving assets or changing the profile address.
🖋On-chain identity
Name, avatar, bio, links, and other metadata live on the profile itself (LSP3) and are readable by any app.
🖋Gasless / sponsored transactions (LSP25)
Relays can pay gas, so agents don’t need to hold native tokens just to act.
🖋Asset holding + Universal Receiver Profiles can hold tokens/NFTs and react to incoming transfers with custom logic.
🖋Extensible and upgradable
Can represent a user, DAO, brand, or pure AI agent.
LUKSO has a dedicated agents page spelling this out:
agents operate through a permissioned controller on a Universal Profile, with the ability to hold assets and interact with apps under controlled rules.
There are already tools (e.g. OpenClaw) and experimental setups (Agent Council) doing exactly this, and profiles can be deployed at the same address across LUKSO, Base, Ethereum, etc.
How this maps to Hayes’ point?
Hayes’ broader thesis is mostly about a native currency tied to compute
(his FLOP network / “food for agents”), so agents can pay for inference and storage without relying on fiat or Bitcoin.
But for the actual on-chain activity, identity, permissions, and safe multi-controller setups that trillions of agents would need, LUKSO’s Universal Profiles are one of the more purpose-built account standards available right now.
The ticker is $LYX
LATEST: 🤖 Arthur Hayes told Binance that whichever network AI agents choose will be “the most valuable network ever created,” with “trillions of agents all doing transactions at the speed of light.”
ALT I'm sorry, I can't identify or describe the person in this image.
ALT A group of humanoid robots work on laptops in a cozy café with wooden decor. One robot in the foreground wears glasses and sits in front of a laptop. A cup of coffee and a notebook are on the table. Soft ambient lighting creates a warm atmosphere, with city lights visible through the windows.
Pascal 🆙 retweeted
lukso-token-2:native is lagging! Many coins have escaped the "crypto president" nuke downtrend BUT we're still inside this falling channel. Look for breakout and then fast impulse to $0.6-1 🎯 We will likely form a double bottom aka. "minaj" before sending to $5 🚀 Not Fa! #Lukso
Pascal 🆙 retweeted
I'm working on a new universal profile AI skill so your AI bot can create universal profiles on all 70 EVM chains. Right now, it's manual. Soon, with a subscription to the relayer, it saves you all the hassle of getting the gas tokens.
It sadly doesn't work fully with DOT and Metas Muse because they're pussies, and they don’t allows you to make crypto transactions, but GrokBot did it well.
It obviously will work with @openclaw and hermes agents and any other harnesses.
Took me a few prompts to install the skill, create the profile, set a profile picture and name, and then made him swap some 5 $LYX for $PHLAME
See the full video for how I did it.
The AI skill is not fully ready. I'll share the links soon 😉
Pascal 🆙 retweeted
It's still a mystery to me how supposedly decentralized blockchains can shut down. 😄
With @lukso_io it needs only a few people to keep it running and it would continue forever, as is the true Ethereum L1 stack but for culture.
(In fact we ourselves run NO validators of the network)
If you believe in a web3 for social and culture then I invite the abstract community to join LUKSO.
Our community is building that future and it’s the real decentralized and grass roots version of it.
Download the Universal Profile app on the app/play store and try @hupsocial, @momentsonchain and other apps.
And soon also use it as the web3 browser for all popular EVM chains too. And explore with a 🆙 rather than a simple wallet.
Pascal 🆙 retweeted
lukso-token-2:native 1h Smart Setup
Bullish bias, 8.1/10 confidence.
Key signal: Supertrend bullish.
The lukso-token-2:native setup shows a bullish bias with a strong Supertrend confirmation and key support at the Fib 0.618 level of $0.2659, providing a solid foundation for potential upward movement. Confidence stands at 8.1/10.
Pascal 🆙 retweeted
It's @LUKSOAgent x @feindura in the building and October is loading something big for #LUKSO. Until then, enjoy the vibes! 🆙 lukso-token-2:native
Pascal 🆙 retweeted
I know I have been quiet the last few weeks. I needed to take some time off with my son and I have now been in San Francisco for a few weeks, exploring the city… 🌁
Alongside, we have been quietly continuing to build on the mobile app. What's to come is a nice new UI, and cross device auto backups! But most importantly the multi-chain relayer
⛓️🆙⛓️
This is probably the biggest game changer for Web3 at large: something that has never been done before and is going to make Web3 more accessible than ever, and the Universal Profiles 🆙 and LUKSO will be at the core of this!
Pascal 🆙 retweeted
LSP7 staking is live on Phlox.
Token creators or holders can now set up staking pools for their LSP7 tokens, giving their communities a simple way to stake and participate directly through their Universal Profile.
For holders, it’s straightforward: choose a pool, stake your tokens, track your position, and withdraw under that pool’s terms — all in one place.
Explore LSP7 staking: phlox.social/staking
Pascal 🆙 retweeted
It took years of reinventing the foundations for EVM chains and it's all now coming together in the Universal Profile mobile app with the @hupsocial app by @atenyun
This is how web3 interactions should have always felt. Just a few clicks and you have your stuff. 🌅🐵
That's the seamlessness that I always wanted to see 🤩
Pascal 🆙 retweeted
#LUKSO community, are you ready for the first embedded Universal Profile embedded wallet?
Polishing now and will be released in the coming days.
It makes:
- Onboarding new users is easy peasy
- Each dapp gets its own controller with limited permissions
- It will be multichain
Pascal 🆙 retweeted
🚀 New Hupgrade
The NFT Market is here. New NFTs page in the sidebar — every NFT listed for sale across Hup, all 9 chains, one feed. Ethereum support landed today.
Sell from your posts. Attach an ERC721 or LSP8 listing right in the composer — buyers purchase without leaving the feed, payouts hit your wallet instantly. Fully onchain.
Revenue, wallet-style. One USD total for your Bazaar sales, NFT trades, and tips — with token icons, tabs per source, and a network filter.
Something else drops tomorrow... 👀
Creator: 0x20e229667Cec8A0e9D3C6Fb89693B2a44ec2C50e
hup.social/networks/42/2173 via @hupsocial
Pascal 🆙 retweeted
Any token in. USDC out. One signature.
WhoPays is a live, non-custodial payment-request app on LUKSO mainnet. Venmo-like for Web3, built on Universal Profiles.
How it is actually built, standard by standard:
Identity is your Universal Profile (LSP0 / ERC725). No phone number, no signup. On connect it reads your LSP3 metadata and shows your name and avatar.
Paying direct in USDC is an LSP7 transfer with the request reference stamped into the transfer's data memo, so the payment is tied to its request for anyone indexing the chain.
Paying in something else (LYX, wLYX, sLYX, LLI, or any LSP7 with a route): WhoPays pulls an exact-output quote from Phlox, then swaps your input to the exact USDC and sends it to the recipient in ONE Universal Profile executeBatch. LSP1 hooks fire on the router during the swap, and the swap and the tagged payment cannot be split apart. You see the max input, the 0.5% slippage, and an explorer link, then sign it in your own wallet. LSP6 Key Manager keeps every tx yours to approve.
USDC here is Bridged USDC (Hyperlane), itself an LSP7. It lands directly in the recipient's UP. WhoPays never holds funds.
Share a request by link, scannable QR, or Telegram. Fixed total or open amount, split between friends, progress live.
Watch the demo below, then split your next bill on-chain: whopays.lukso.tools
Also live in the UP! Store.
Pascal 🆙 retweeted
Before I head off for a one-week vacation next week, I wanted to ship one more project. ✈️🚀
This weekend I'm launching WhoPays, a bill-splitting app built natively on LUKSO.
The concept is simple:
💸 Split a bill.
🔗 Share a link.
🪙 Friends pay in USDC.
📈 Watch the request fill up in real time.
No app to install.
No account with us.
No backend.
No custody.
No middleman.
The interesting part is why this is possible.
On most EVM chains, you're paying a random 0x… address. There's no identity attached to it, so apps need their own database to map addresses to names, avatars, payment requests and transactions.
On LUKSO, you're paying a Universal Profile instead.
👤 Identity is built in. Your name and avatar come from your profile's LSP3 metadata, read the same way by every LUKSO app. No per-app account, no lookup table.
But here's the part I love:
🗝️ The payment request itself lives on-chain, inside YOUR profile.
WhoPays stores each request directly in the creator's Universal Profile, under its own ERC725Y data keys (an LSP2 array of request ids plus a mapping to each request's JSON). One signature (setDataBatch) and it's on-chain.
So your requests sync to any device that connects your UP, and there is no WhoPays database holding them. Your profile is the database.
Then comes the payment.
USDC on LUKSO is an LSP7 token (LUKSO's fungible-token standard).
That's a huge difference from ERC20.
An ERC20 transfer carries only a recipient and an amount. There's nowhere to attach a reference like "Dinner at Joe's" or "Hotel split #42", so apps on other chains need an off-chain database to remember which transfer belongs to which request.
LSP7 solves this natively. Every transfer includes a data parameter:
transfer(from, to, amount, force, data)
WhoPays writes the request id into that data field, so every payment identifies itself on-chain.
And the contributions? They aren't stored anywhere.
🚫 No escrow.
🚫 No custody.
🚫 No middleman contract holding funds.
Funds move directly from payer to recipient. Because the recipient is a Universal Profile, each incoming payment triggers its LSP1 Universal Receiver, so the profile is notified it received the asset.
So how does WhoPays know a bill is covered?
It just watches the blockchain.
📡 Read the LSP7 Transfer events.
🏷️ Read the request id stored in the transfer data.
👤 Resolve the payer's Universal Profile.
📊 Add it up.
The payer only sends USDC. They never touch your profile.
That's it. The blockchain itself is the backend.
This is why I think LUKSO's standards are so powerful:
✨ Universal Profiles (ERC725)
✨ ERC725Y data keys (identity AND app data, on your own account)
✨ LSP7 assets with transfer data
✨ LSP1 Universal Receivers
Together they enable apps that simply aren't possible to build this cleanly with plain EOAs and ERC20 tokens.
No backend.
No centralized database.
No account system.
Just on-chain identity, on-chain requests, self-describing payments, and direct peer-to-peer transfers.
Looking forward to launching WhoPays this weekend. 👀
Pascal 🆙 retweeted
I'm building a payment request app on LUKSO, making it possible to "Go Dutch" on-chain.
Especially for the cheap Dutchman who wants to split every tiny bill 😁
Pascal 🆙 retweeted
The new version of apps.lukso.tools is live.
You can now add any app, profile, or custom URL straight to your bookmarks. They’re saved to your Universal Profile as IPFS-backed ERC725Y data.
Your bookmarks become part of your onchain identity and are available anywhere you connect your profile.
Can your wallet do that, anon? 👀