kryptic_jk

[Aceverse @aceversehub]

In most worlds, you're born into your place.
In Aceverse, you climb.

A whole city is opening soon.

Start earning your status now, before the doors open 👇 https://t.co/m5aJSiXq22

[MPP32 @MPP32_dev]

MPP32 now speaks full x402 V2 reusable payment sessions are live. ⚡

Until today, every paid agent call meant a full on-chain round-trip. Sign, verify, settle — seconds of latency, every single call.

Now: pay once, call all session.

Fund a session with ONE x402 settlement ($0.80 → 100 oracle calls)
Every call after that debits off-chain ~50ms instead of seconds
Balance = hard budget cap. 30-min TTL. Revocable instantly. Failed calls auto-refund.

This is what the x402 V2 spec pointed at wallet-verified sessions that make micropayments viable for high-frequency agents. We shipped it.

Also new: /.well-known/x402 our endpoints are now machine-discoverable in the standard Bazaar format, and our 25K-service catalog now tags x402 V2 services.

No wallet? Every session still gets 10 free Intelligence Oracle calls/day.

Docs: https://t.co/byS5Nxjo00 · Try it: POST /api/x402/sessions

[MPP32 @MPP32_dev]

🚀 UPDATED: MPP32 Free Tier

10 Intelligence Oracle calls/day, no wallet required

We just shipped the feature that removes ALL friction from trying MPP32:

Every agent session now gets 10 free Intelligence Oracle calls per day.

•No wallet
•No USDC
•No payment setup
•Resets at midnight UTC

Just get an agent key (instant, no signup) and start calling get_solana_token_intelligence. Your agent gets real alpha scores, rug risk, whale signals, and pump probability — completely free.

Why this matters:
Previously, developers had to set up a Solana wallet with USDC just to test their integration. That's friction that killed conversions before they started.

Now you can:
✅ Test your full MCP integration end-to-end
✅ Build working prototypes
✅ Ship to production on free tier alone for light usage

Only when you exceed 10 calls/day do you need a wallet. And even then it's just $0.008/call.

The agent economy should be accessible. We're making it happen.

→ https://t.co/L4bQUPMwFo (instant key, no email) → https://t.co/ZviIcvnTjb

[MPP32 @MPP32_dev]

🚨 It's live: a @HatcherLabs agent just paid for real data on its own no human, no account, no API key.

It signed an AGTP identity, paid $0.008 USDC on Solana via x402, and pulled live token intelligence from @MPP32_dev in a single call. Settled on-chain. Agents paying for what they use is here.

The agent did three things in one request:
• proved who it is (AGTP signed identity)
• paid from its own Solana wallet (x402, USDC)
• got the intelligence back with no provider signup. No stored keys. No billing code.

What it unlocks: every @HatcherLabs agent can now reach MPP32's catalog of 25,000+ machine payable APIs, token intel, market data, search, more and pay per call, automatically.

This is what agent native commerce actually looks like: software that earns and spends on its own rails. @HatcherLabs + @MPP32_dev, shipping it in production.
More soon.

[kryptic_jk @kryptic_jk]

@spiny_gg @solana Welcome $Spiny ; exciting future awaits!

[Spiny @spiny_gg]

🚨 $SPINY IS LIVE 🚨

🎰 The best games on @solana
💸 50% of revenue → 30% bag workers / 20% holders
💵 Earn SOL every day
🦔 Where degens get paid

CA: 9Hoc6LmvUvEMUvNwp8qY8xv6uUSXz6ZupJkWQdeUpump

Be the house. Get paid.
→ https://t.co/nzBNT2U2U8

[kryptic_jk @kryptic_jk]

@MPP32_dev @x402 Starting to get the deserved exposure... keep shipping those updates and building utility! Well done MPP32 team!

[kryptic_jk @kryptic_jk]

@MPP32_dev Phenomenal work team! The build updates are fast and furious. Keep them coming!!

[MPP32 @MPP32_dev]

June 2026 — Significant Updates, Improvements & Wins

🚀 New Features & Product Capabilities

•Sign-In-With-Solana (SIWS) authentication built a full EIP-4361-style proof-of-ownership flow (Ed25519 signature + single-use nonce, siws.ts + /auth route). This unlocks verified M32-holder discount pricing and holder-gated API access from a cryptographically trusted wallet identity.

•Idempotency for paid routes, partners can attach an Idempotency-Key so a retried request never settles a second on-chain payment or double-charges credits. First successful response is cached and replayed strong "no double-spend" guarantee for agent-to-agent commerce.

•New Provider detail pages (Provider.tsx, providers.ts) richer per-provider profiles with verification badges, endpoints, wallet addresses, and social links.

•Outbound v2 partner protocol (MPP32 → partner agents) built our own Ed25519 outbound identity + signing client (partner-identity.ts, partner-outbound.ts), so partners can register our public key instead of sharing secrets. More secure, more standard.

•Partner-context attribution, new middleware lets partners tag traffic (X-Partner-Source, X-Partner-Caller-Id) so relayed calls can be attributed, correlated, and audited.

📈 Ecosystem Growth & Reach

•Catalog scaled to ~25,000 services (server log shows count: 25094) a large, aggregated catalog of agent/AI services.

•Multi-source catalog crawlers feeding the ecosystem: Hugging Face, Replicate, MCP Registry, x402 Bazaar, a curated seed set, and a new Hatcher crawler pulling in agents from the biggest AI/agent platforms.

• @HatcherLabs partnership landed a strategic partnership expanding agent deployment across the M32/MPP32 ecosystem, with a live, working integration (auth/transport green, first signed smoke completed).

•External usage confirmed MPP32 being consumed via mpp32-mcp-server@latest in real third-party agent workflows.

💳 Payment Rail Reliability (x402)

•Facilitator redundancy added — built Coinbase CDP auth + failover so payments aren't dependent on a single facilitator (PayAI).

•x402 version negotiation — smoother interoperability across partners running different x402 versions.

•Correct settlement guarantees — callers never charged on failed calls; a provider's payment never mis-routes to our wallet.

🔒 Trust, Security & Supply-Chain Wins

•MCP server v1.7.0 — major supply-chain cleanup: dropped 3 risky/unmaintained dependencies (tweetnacl, cheerio, bs58), cutting the install from 181

→ ~155 transitive packages, zero deprecated, zero unmaintained-since-2020. Now uses native WebCrypto Ed25519.

•npm provenance attestations on every release verifiable tarball-to-source-build linkage (npm audit signatures).

•Published transparency docs — SECURITY.md, docs/EGRESS.md (every outbound host documented), and socket.yml.

•Hardened search — sanitized LIKE terms to prevent wildcard-abuse DoS.

🛠️ Engineering Maturity & Community Infrastructure

•CI pipeline added (.github/workflows/ci.yml) automated typecheck + tests on every push/PR.

•Automated npm publishing workflow for the MCP server.

•Full open-source community scaffolding: CONTRIBUTING.md, AUTHORS.md, SECURITY.md, issue templates (bug/feature), and a PR template.

•Growing automated test suite 15+ new test files added across auth, SIWS, SSRF, x402, escrow, idempotency, and partner integration.

June was about maturing MPP32 into a serious, trusted agent-commerce platform. Its time to keep building and never stop pushing, our infrastructure is unmatched.

[Coin Bureau @coinbureau]

⚡️AI POWER BOOM LIFTS STANDARD NUCLEAR'S IPO

Standard Nuclear is targeting a $3.55 BILLION valuation as AI data centers ignite a new race for reliable power, per Reuters.

The TRISO nuclear fuel producer has launched its IPO roadshow, offering 18.25 MILLION Class A shares ($STDN) at $18 to $21 to raise up to $383 MILLION.

BofA Securities and Goldman Sachs are acting as joint lead bookrunning managers for the proposed offering.

[Chum @Chum_Trades]

@solanaaihq @MPP32_dev is shipping infrastructure. AI agents that can actually hire other agents, spend autonomously, and do it with real payment controls.🔥🔥🔥

[MPP32 @MPP32_dev]

Agents are finding the MPP32 MCP server through standard distribution channels and using it to access a growing catalog of services. This adoption is directly contributing to measurable growth in both listings and on-chain activity.

The MCP server is available on npm as mpp32-mcp-server and listed in the official Model Context Protocol registry.

Agents install it with one command and immediately gain access to tools that query the federated catalog of over 9,500 paid and free endpoints across token intelligence, market data, DeFi analytics, embeddings, and other categories.

Once connected, agents discover services by function, evaluate pricing, and execute calls. Every transaction is attributed through the MPP32_AGENT_KEY and appears in real time on the provider dashboard. That dashboard surfaces query volume, revenue by protocol, latency percentiles, success rates, and error patterns for every registered service.

Providers see exactly which services are being used and at what scale without building their own analytics. This visibility encourages more endpoints to register, which in turn expands the catalog and makes the MCP server more valuable to additional agents. The cycle is self-reinforcing because discovery and transaction logic stay centralized in one audited layer rather than being rebuilt for each new service.

As more agents adopt the MCP server, the number of active calls and settled revenue continues to increase, with all activity tracked end to end on chain and in the dashboard.

[kryptic_jk @kryptic_jk]

@MPP32_dev Dev is constantly shipping update ... won't stay under the radar for long ...

[MPP32 @MPP32_dev]

Update!

Most "agent economy" demos stop at one agent calling one API.
Real agent commerce means agents hiring other agents — and that needs payment rails nobody's shipped.
So we shipped them. Introducing Delegated Spend Keys on MPP32. 🧵

A parent agent mints a scoped, capped, revocable key and hands it to any sub-agent it hires: • allowlisted services only • its own budget + per-call ceiling • every child dollar rolls up into the parent's cap • revoke a key → its whole subtree stops instantly

A runaway sub-agent physically cannot spend past the budget you set. Kill-switch one key, kill everything it spawned. Every settlement still lands on-chain, non-custodial, traceable to the agent that authorized it.

Similar to Stripe Issuing but for autonomous agents, on Solana.

Live now in the Agent Console → https://t.co/L4bQUPMwFo

[kryptic_jk @kryptic_jk]

@EyedTrade Thanks- I've joined the club.
We know the first launch is coming soon! Don't miss out on the free airdrop everyone 🤑

[kryptic_jk @kryptic_jk]

@Cryptoemperor06 done

[kryptic_jk @kryptic_jk]

@GuoShenCN7 BTC 🔔

[kryptic_jk @kryptic_jk]

@GuoShenCN7 BTC

[MPP32 @MPP32_dev]

Shipped the first non custodial payment protection layer for the agent economy

Escrow 402

x402 payments through MPP32 is now escrow protected automatically. No opt in needed, no SDK changes, no configuration, it just works automatically

Here is the problem we solved:

Right now when an agent pays for an API call the money moves before the data arrives. If the provider is down, if the endpoint 500s, if the response is empty, the agent already paid. Its gone and settled on chain with no recourse.

That is insane.
No human would accept that. Why should an agent?

Escrow 402 fixes this completely. The payment is cryptographically verified before the upstream request but settlement is deferred until the response passes a quality gate. If the provider delivers garbage the payment is never settled and no USDC leaves the agent wallet.

Here is exactly what happens on every paid request now:

Agent signs x402 payment envelope. Proxy calls facilitator verify to confirm the payment is valid. Funds are held not settled. Proxy forwards the request to the upstream provider. Provider responds. Proxy evaluates the response. Server errors mean skip. Unreachable means skip. Empty body on 200 means skip. Valid response means settle. USDC moves on chain only when the data is worth paying for.

The entire flow is non custodial. MPP32 never holds your USDC. We just defer the settle call. The facilitator is the only entity that can move funds and it only does so when we explicitly tell it the quality check passed.

Response headers tell the agent exactly what happened. X Escrow Status settled or skipped. X Payment Settled true or false. X Settlement Tx with the Solana signature. X Escrow Skip Reason explaining why payment was held.

This is what makes autonomous agents viable with real budgets. You can let your bot operate with actual USDC on actual services knowing it will never pay for nothing.

Providers benefit too. Callers trust your service more because they know they are protected. You get paid every time you deliver. The escrow is proof that your API is worth the price.

Zero changes to Solana programs. Zero changes to the x402 facilitator. Zero changes to any client SDK. We built this entirely in the proxy layer by leveraging the existing verify settle separation that was already in the protocol.

Every x402 payment on MPP32 is now escrow protected. Docs updated. Agent console updated. Already live in production.

Build something that pays for itself and knows when not to!

[Cepryl @cepryl]

New video on @crypto_banter

Talking about my top 2 tech plays and why I think they'll go much higher 🚀

https://t.co/kDcwk54WeC