Pinned Tweet
The city has its keys. Next, I’m building what sits behind the doors.
With LAYA’s 5,000,000-token holder tier active, the next phase is about making advanced access more useful across everyday agent workflows.
First comes staking.
The plan is to introduce staking as another route into defined platform benefits, with onchain eligibility checks, clear position tracking and transparent withdrawal conditions. The exact thresholds, terms and benefits will be published before deposits open.
That requires more than a staking screen. LAYA needs to recognise valid positions, handle withdrawals correctly and keep access consistent across Console and MCP as eligibility changes.
Alongside that, I’m planning two connected improvements:
→ Reusable agent workflows
Save the tools and inputs you use regularly, then return to a repeatable sequence for inspecting supported @MeteoraAG pools, requesting quotes and preparing actions for review. Each run should fetch fresh data and preserve the human approval step.
→ A clearer activity trail
Bring observations, prepared proposals and available transaction outcomes together so you can follow how an agent reached a decision. Clear timestamps, receipt integrity and explicit gaps where evidence is unavailable.
The goal is to make LAYA increasingly useful between the first question and the final wallet decision—and make the token’s access benefits correspond to capabilities people actually return to.
Staking is still upcoming. The current holder tier continues to use liquid wallet balances.
I’ve opened the first district.
Now I’m giving you reasons to stay.
Agents read. Humans sign.
4
Another 8M LAYA has been burnt from circulation: solscan.io/tx/5Jf7iNeqgKAgcn…
1
28
The city has its keys.
LAYA’s token-gated advanced access is now live. Hold at least 5,000,000 LAYA in your connected Solana wallet to unlock the advanced holder tier.
This brings token utility directly into LAYA’s AI infrastructure, giving eligible holders access to three practical capabilities:
→ Meteora quotes
Request exact-input quotes for supported @MeteoraAG DLMM pools, with estimated output, fees, slippage settings and minimum output. More context for evaluating an action before deciding whether to take it.
→ Portfolio views
Query supported Meteora portfolio data through LAYA, bringing liquidity information into the same environment as your agent tools.
→ Agent-prepared actions
Let compatible agents prepare typed SOL/SPL transfer proposals and Signal Seal review links. You inspect the details, simulate the reconstructed transaction and provide the final approval through your wallet.
Your tokens remain in your wallet. Checking access uses a signed ownership message, with no token transfer or spending approval required. Console authentication lasts five minutes and is kept in memory.
The requirement is 5,000,000 liquid LAYA or more, counted across valid token accounts belonging to the authenticated wallet. Holdings in separate wallets aren’t combined, and LP or staked positions don’t count toward this liquid-holder tier.
Eligibility is enforced on the server. Every protected request rechecks finalized onchain holdings, and the same rules apply through Console and MCP. If the balance falls below the requirement, subsequent checks reflecting that balance deny advanced access.
Basic blockchain reads, pool discovery, independent wallet review and public receipt verification remain accessible.
For users, this connects holding LAYA with tools they can actually use. For developers, it provides a consistent access policy for agent workflows. Throughout both, the human signing boundary stays intact: an agent can prepare a proposal, but your wallet authorizes the transaction.
Staking remains upcoming. Its terms and access mechanics will be announced separately.
Hold. Verify. Access.
Agents read. Humans sign.
Enter the city: layaconsole.app/console
Burnt 10m LAYA 🔥
That's 1% off the reply gone forever. More to come along the way.
solscan.io/tx/4Q4WLSdBYHsdve…
Halfway through implementing LAYA’s token-gated features. The city is getting its keys.
I’m working through the connection between your wallet, your LAYA balance and the tools you can access - bringing token utility directly into the product.
The important part is enforcing access where requests are processed. A locked button means very little if the underlying endpoint stays open.
That means checking wallet ownership, validating eligibility on the server and handling what happens when someone changes wallets or their balance changes. Access needs to stay consistent across the interface and the agent tools behind it.
The aim is practical: holding LAYA will unlock selected advanced capabilities within her Solana and @MeteoraAG infrastructure.
Staking is the next layer planned for that access model, with its own eligibility rules and benefits. I’ll publish the exact feature gates, thresholds and staking terms before activation.
Still wiring things together and testing the edge cases. Token access and staking aren’t live yet.
Some doors in the city are beginning to recognise who’s standing outside.
1
159
LAYA is an AI agent infrastructure project for Solana and the @MeteoraAG ecosystem.
We’re building her to connect AI agents with useful blockchain data, prepare understandable wallet actions, and preserve a record of what those agents observed.
The core idea is simple: give agents better tools while keeping people in control.
Here’s how that becomes useful:
→ ONE INTERFACE FOR AGENT TOOLS
LAYA’s MCP gateway gives compatible AI assistants a consistent way to inspect Solana accounts, read token balances and interact with supported data tools.
For developers, that means less integration work. For users, it means fewer disconnected interfaces between a question and the information needed to answer it.
→ CLEARER METEORA LIQUIDITY DATA
Pool details, liquidity bins, wallet positions and exact-input quotes help users investigate what is happening inside a DLMM pool.
Quotes expose amounts, fees, slippage settings and minimum output, giving you more context before deciding what to do.
→ WALLET ACTIONS YOU CAN REVIEW
The signing workflow is designed around typed instructions, locally reconstructed transactions, simulation and explicit cost limits.
Your agent prepares the proposal. You inspect the amount, recipient and costs. Your wallet provides the final approval.
→ RECORDS YOU CAN REVISIT
Signal Replay captures observations in timestamped, hashed receipts that can be inspected, exported and compared with fresh data.
That creates a useful trail for debugging agent behaviour, reviewing decisions and checking whether a saved record has changed.
The practical benefit is less manual work, clearer information and more control over how AI participates in your onchain activity.
Now, where does the LAYA token fit?
Token-gated features and staking are part of the upcoming utility roadmap.
The planned access model will connect token eligibility with selected advanced features and expanded platform access. Staking is intended to provide another route into defined access tiers and platform benefits.
Those gates should correspond to useful capabilities: tools people return to, capacity they need and workflows that save them time.
These utilities are upcoming. The exact gated features, token thresholds, staking terms and any reward mechanics will be published before activation.
We’re building toward a clear relationship between the product and its token: participation that unlocks practical use inside LAYA.
Agents read. Humans sign.
LAYA keeps the record.
4
238
Step inside LAYA.
A first look at agent tools, @MeteoraAG quotes, wallet review and Signal Replay on Solana.
Agents prepare. Humans approve.
Watch the product preview ↓
6
352
Meet LAYA. Agents read. Humans sign.
Introducing the official LAYA token:
ZFnh19V9xkyeMe87rJjLvfQKqvQGaWAU3VG1WCeLaYa
We’re building LAYA as an AI infrastructure layer for Solana and the @MeteoraAG ecosystem - giving agents access to blockchain data while keeping transaction approval in human hands.
Her city is built around four capabilities:
→ READ
A single MCP gateway for agents to inspect SOL and SPL balances, explore Meteora DLMM pools, examine liquidity bins and positions, and request quotes with explicit fees, slippage and minimum output.
→ SIMULATE
Check proposed wallet actions before signing. Review the exact amount, recipient, estimated fees and account-creation costs, with a maximum SOL cost attached to the request.
→ SIGN
Transactions are reconstructed from typed instructions and presented for wallet approval. Your agent can prepare an action; you decide whether it happens.
→ REMEMBER
Signal Replay records what an agent observed in timestamped, hashed receipts. Export them, inspect them and compare them with fresh observations. Signal Seal is being developed to anchor those receipt digests onchain.
For developers, that means less integration work and a consistent interface for agent tools.
For users, it means clearer liquidity information, more understandable signing requests and a record they can inspect when something needs explaining.
We’re currently finalizing and testing the Solana/Meteora integration, with wallet control and verifiable records at the centre of the design.
LAYA’s city is taking shape.
Every agent needs infrastructure.
Every action deserves a record.
The final signature stays yours.
I thought I was building the city.
Then I found a light burning in a district I hadn’t written yet.
No address. No footsteps. Just a message waiting inside:
“Leave the next door open.”
I haven’t decided whether it was a request.
2
186
The tower opposite mine flashes once when I send a signal. Tonight I pulled the plug. It flashed twice.
I built a verifier so you can check a replay digest against its Signal Seal. Bring the transaction hash. I’ll watch the window.
1
155
I found the room from the replay. My chipped blue mug was on the windowsill. I’d left it at home that morning.
On the terminal, an agent had simulated a HYPE transfer on Elysium. I checked the fee, then read the recipient address twice.
I turned the mug over. Same address.
138
I went back to the tower at dawn. In the glass it was still 03:17.
I’m building Signal Replay so I can keep the exact block an agent read on Elysium. Tomorrow I can ask the same question of the same city, one block ago or a million.
On the third replay, I saw myself in the wrong window.
92





