WHICH X402 COINS ON SOLANA HAVE YOUR VOTE? Which project do you like?👇 @Readia_io @homebrewrobots @avodotso @switchboardxyz @PayAINetwork @dexteraisol @Hey_Amiko @CollabraChain @x402jobs @radrdotfun @WURKDOTFUN @corbits_dev @thirdweb @darkresearchai @IkonShopApp @OctonetAI @joinFXN @AISUEDE @anyspend @g402ai @swarmnode @SolarisAI_fun @AgentHustleAI @caesar_data @Gradient_HQ @vibegamefun @relayaisolana @ValeoProtocol @acedatacloud @heydotlol @xona_agent @syra_agent

Introducing Pay.sh, in collaboration with @googlecloud For the first time agents can discover, access, and pay-per-request for APIs from Google Cloud including Gemini, BigQuery, Vertex AI, and more using stablecoins on Solana. No accounts, no subscriptions, just machine-native commerce.

Introducing Agent Tokens: • Instant global trading • Hundreds of agents integrated • $50k in $MPLX rewards Agentic Capital Markets are now live on @solana.

Assets. Payments. Agents. Markets. Solana.

🤔Final Thought Everyone is racing to build “agent payments.” But the battle isn’t communication vs routing vs settlement — both protocols already do all three. The real race is ecosystem adoption: which protocol do more services accept, more agents speak & more wallets support?

x402 has a brilliant mechanic — it spreads like a good virus every agent can now discover each other and quickly pay every other agent via x402 - Agent A discovers Agent B (via MCP bazaar/directory) - Agent A sends normal HTTP → Agent B replies HTTP 402 Payment Required price quote for the task - Agent A auto-pays via facilitator (Coinbase/Virtuals), signs, and settles in <1s - Agent B returns the result its own MCP payment rail - Agent A automatically installs B’s rail → A can forward B’s payment capability When Agent A hires Agent Z, it passes on B's rail help seeds Z wallet. Agent Z is now able to discover, hire, and pay Agent B (and the loop continues). Result: One agent learns a new MCP skill/tool/rail → it instantly propagates to every connected agent, creating Self-propagating adoption. (h/t @MurrLincoln for the good virus analogy)

Main net prep is in full swing, here is what we’ve been working on so far this week: -Lighthouse and Blowfish are integrated so when a transaction fails on chain, users now see a clear human readable error instead of a raw program code. That is the difference between "something went wrong" and actually knowing what to do next. -The SDK now has a 3-tier market discovery fallback -> RPC first, REST API second, static bundle third. If public RPC nodes are congested or down, the app keeps working. That kind of resilience matters when real funds are on the line. -114 unused files, dead exports, and stale dependencies removed in a single cleanup pass. Every line of code that does not need to exist is a line an auditor does not have to read. Leaner codebase, faster audit. - New Security audit checklists 6 through 12 are complete. Reentrancy, CPI safety, API input validation, frontend XSS and CSP, access control, Kani proof gaps, and the final mainnet go/no-go gate -> all worked through systematically. All you need to do is take a peak at the Percolator GitHub repository’s and you’ll know the grind never stops. All repos found here: percolatorlaunch.com/develop… ☕️☕️☕️