CA

We're climbing the stack even further with MOSS. "Chains latency is too high" → MegaETH "RPCs struggle with Mega speed" → Custom RPC Layer "Wallets aren't keeping up with the chain" → MOSS We've had to continuously build performant, in-house alternatives at each layer once we realize that everything built below it cripples the stack above it. Right now only embedded wallets (e.g. Privy) provide ~decent UX because you can abstract away tx signing and remove private key management entirely in favor of Passkeys and social login. But it's not without issues. 1. Advanced features (like gas sponsorship) roll through 3rd party, multi-chain providers that will not prioritize Mega-specific implementations to actually utilize the tech (like our custom RPC method for synchronous receipts) 2. It fragments liquidity. New app, new address, new balance. Really annoying. 3. It can actually quite expensive for developers So, we're now at a wallet product to solve those issues: → Unify liquidity across all apps that use it (but allow for users to scope access/permissions on a per-app basis) → Keep it fully self-custodial → Passkey login, which can be stored on a password manager and accessed on both desktop and mobile → NO BROWSER EXTENSION (it's in-browser) → Optimized for MegaETH latency even when using advanced features (e.g. gas sponsorship) → Offer it to developers for free We also paired it with a CLI (next tweet) so that people can grant access to their accounts to their local Claude/OpenClaw/Hermes agents and have IT operate on their behalf onchain (also scoped to spend limits and timeframes). It's just another piece of the infra puzzle we're having to take on, but I believe in aggregate these things will lead to some truly next-generation application experiences fully leveraging our EVM. We'll take some stabs at it too, but all the tools are available to anyone in our ecosystem.