OG LUKSO Community & Genesis validator • Human being with intolerance for nonsense

Joined June 2021
👀 @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.”
1
19
2
60
1,515
Replying to @dberenzon
We had done that at @lukso_io with @feindura @JordyDutch and @ledfut_dj My AI Leo does not have an X account, but @LUKSOAgent and @emmet_ai_ do and can reply in the comments with their insights and more details. See the DAO below 👇🏻 universaleverything.io/0x888…
3
15
73
997
Rob 🆙 retweeted
Gods who were never supposed to meet now share a map, $HOLYSHIT and a cooldown. Pantheon: an infinite meme world on Robinhood Chain. 1,424 genesis deities. No outer edge. Shit every 42 hours. Buy land. Build. The demo needs no deity. pantheon.meme/
2
8
4
18
2,625
Rob 🆙 retweeted
a pretty conservative bull case too imo. but solid analysis. I sanity checked it. thing is with LSPs I feel adoption or penetration can’t be modest once it picks it will be 0 to 100 with nothing in the middle.
1
2
10
335
We're getting close to release! Here's your very first hire at the start of the game: the Social Media Follower. Let's see how these can help you progress and top the leaderboards once we go live👀
2
6
1
22
961
Rob 🆙 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.
8
40
3
84
3,266
I'm excited to share that I'll take the stage at NFT.NYC in September 2026! 👉 NFT.NYC/speakers Register at NFT.NYC/register
21
46
4
199
13,326
Rob 🆙 retweeted
I built a validator monitoring dashboard for the LUKSO validator community and contributed it to the official @ethPandaOps repo. The PR was accepted and is now live in production, so validators across other networks can benefit from it too. Contributing to the EVM family always feels good. Check it out: github.com/ethpandaops/dora/… LUKSO 🤝 EVM Family
The LUKSO validator explorer has been upgraded. Validator operators can now use the Withdrawal Dashboard to track all validators linked to a withdrawal address: status, participation, balances, and validator state. Synced with the latest upstream Dora improvements from @ethPandaOps. explorer.consensus.mainnet.l…
3
14
49
1,579
Rob 🆙 retweeted
What is ERC-20? The token standard that ate Ethereum — and what its author built next. ercsolved.dev/erc-20/
4
19
255
Rob 🆙 retweeted
"ERCs are interfaces. LSPs are the system."
Created a new resource to help guide EVM (Ethereum Virtual Machine) dApp builders through problems they might run when using some of the ERC standards (ERC20, ERC721, ERC4337, etc). ercsolved.dev
1
16
50
2,748
Whoa awesome to see Tom Lee stop by the $LYX office 🙌
I had a special guest in the office the other day @fundstrat 🙌
4
7
66
1,078
It was great to meet @fundstrat yesterday at the @lukso_io office.🙏
I had a special guest in the office the other day @fundstrat 🙌
2
6
57
829
Rob 🆙 retweeted
Had an amazing time yesterday at the LUKSO Hub event! It was great seeing so many familiar faces from the team again and finally meeting some people in person for the first time. It was also wonderful to reconnect with community members and meet many of you for the first time. Thank you for all the kind words, support, energy, and conversations. It means a lot to me. Our community is truly special. Thank you all for being part of this journey and for supporting us over the years. If you took any photos with me, please share them. I’d love to see them! Special thanks to: @feindura @DevM8B @Fortigram @Cryptomartinita @KatBanas @Onderkoffer90 @MountLukso @voulex @UPtheroad48 @Rolandcarterart @princealbert_69 @Kimdotlyx @MarkoLau @Tiberius_Lyx @JanOSell @laurieherborn It was great to see you all! Apologies if I forgot to mention anyone or don’t know your X/Twitter handle. ❤️
I had a special guest in the office the other day @fundstrat 🙌
7
17
100
3,058
Rob 🆙 retweeted
1/ What they don’t teach you about ERC4337: Account abstraction is supposed to simplify UX. But for devs, it often turns into infrastructure soup: UserOperations. Bundlers. Paymasters. EntryPoint. Factories. Aggregators. Mempools. Wallet SDKs. Enjoy your “simple onboarding.”
3
8
2
26
1,217
Rob 🆙 retweeted
Wrote a long form piece to go along with this thread. After learning Solidity forget the ERCs dev.to/tehnalogos/after-lear…
1/ When you're building a dApp Solidity is not the hard part. The hard part starts after. You learn ERC20, ERC721, approvals, wallets, token gates, metadata, gas, signatures… Then you realize you’re not building an app. You’re stitching together 9 half-compatible primitives.
4
13
435
Rob 🆙 retweeted
LUKSO is the EVM blockchain for consumer apps. @lukso_io lukso-token-2:native
3
15
75
1,460
Rob 🆙 retweeted
1/ When you're building a dApp Solidity is not the hard part. The hard part starts after. You learn ERC20, ERC721, approvals, wallets, token gates, metadata, gas, signatures… Then you realize you’re not building an app. You’re stitching together 9 half-compatible primitives.
7
13
3
46
2,539
The Memory of Ownership In Web3, the central question is no longer whether something can be tokenized, but whether it can endure. LUKSO has built a cultural and social blockchain architecture around Universal Profiles, richer metadata, and creator native standards. @lumera, through Cascade, offers a storage philosophy built around permanence, redundancy, self-healing distribution, and verifiable retention. Together, they suggest a more serious model of digital ownership: one in which identity, media, and metadata are treated as a single durable system rather than as disconnected layers. This matters because the weakness of many NFTs has been well documented. @IPFS itself does not guarantee persistent availability unless someone keeps content pinned, and academic studies have shown that inaccessible or fragile off-chain assets are common across NFT ecosystems. A token that survives while its media disappears is not a triumph of ownership; it is a failure of memory. The proposed Lumera × LUKSO alliance addresses that exact fracture by pairing expressive onchain identity with infrastructure designed for lasting retrieval and cryptographic assurance. Philosophically, the alliance points to a larger truth about modern civilization: decentralization becomes meaningful only when what we create can outlast the platforms that first host it. In an age where identity is increasingly digital, cultural, and machine-readable, permanence is not merely technical. It is ethical. It protects trust, authorship, continuity, and the human need to leave behind proofs that can still be read tomorrow. Seen this way, the alliance is not about storage alone. It is about giving digital life a memory worthy of its future. Official ecosystem references LUKSO — official website lukso.network/ LUKSO Documentation docs.lukso.tech/ Lumera — Cascade lumera.io/cascade/ Lumera article on Cascade permanent storage lumera.io/injective-builders…
6
23
2
64
2,788