Shipped: payment links on BASEUSDP. , recipient + amount + token + memo encoded in the URL itself. stateless, no backend writes. Opens in any wallet via the ethereum: uri on base. qr scan for cross-device. or sign through BASEUSDP directly. Want to support a builder? they drop a link with their monthly ask in the url. you click, pay from any wallet on base, done. they get usdc encrypted on their side.

Ship ➡️ shore In 📍 northern Queensland, the @AustralianArmy's 10th Fires Brigade’s high mobility artillery rocket system (HIMARS) took to the beach with the help of HMAS Choules. Having earlier exceeded expectations by firing various missile types ahead of schedule, and at distances new to Army, attention has turned to the deployability of HIMARS on aircraft and ships to extend the ADF’s ability to defend Australia’s northern approaches. The platform has been certified to deploy on @AusAirForce C-130 and C-17 aircraft and on board the @Australian_Navy’s landing helicopter docks (LHDs). Now it was time to prove the ability to transport the platform from ship to shore. Read more ➡️ #YourADF#

Shipping 3 SMS payment tiers this weekend. Full Private: ZK-encrypted, zero on-chain footprint. Semi-Private: amount hidden, relay protected. Standard: fast, visible, lowest fee. You choose your privacy. You choose your cost. $USDP

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!

Shipped 4 releases this week at @TrustWallet: 2 features + 2 hotfixes — Hyperliquid support, Solana & Aptos address updates, DeFiLlama dApp data integration, and more. App Stores are accelerating. So are we. Ship daily, not weekly.