Agent Checkout Gets a Physical Demo

Wallet CLI moves from concept to a jersey purchase flow

MegaETH followed the MegaMerch launch with the cleaner technical demo: tell an agent to grab a jersey, and the agent pays in USDm and routes the purchase through the wallet flow. The point is not that a bot can click a checkout button. The point is that MOSS gives the agent scoped wallet permissions instead of handing over raw keys. That matters because the Wallet CLI is being framed for agent use cases across Claude Code, Codex, OpenClaw, Hermes, and similar tools. Budgets, rules, and revocable permissions turn the demo into a practical AI x crypto account model: agents can act onchain, but users still control the boundary conditions.

MOSS Tries to Collapse Wallet Fragmentation

One account layer for apps, USDm balances, and agent permissions

Bread's MOSS note frames the wallet as the next layer MegaETH had to internalize. The argument is straightforward: a fast chain still feels slow or fragmented if every app creates a new wallet, new balance, new signing path, and new liquidity pocket. MOSS is meant to unify that surface. Users get one in-browser, self-custodial account with passkey login, app-scoped permissions, built-in bridge, swap, and deposit flows, while developers get a MegaETH-native account layer that can support gas sponsorship and lower-latency interactions. That is where USDm fits. USDm is no longer just a Terminal reward line item; it becomes the asset that can move through the unified MOSS account into merch, packs, trading, and other MegaETH apps. The larger bet is that one balance plus scoped permissions can turn rewards into spendable ecosystem liquidity instead of stranded app balances.