1/ Introducing Oko: Keplr’s fully open-source embedded wallet stack. Email and social-login onboarding, MPC-enhanced security, and a universal non-custodial wallet, all under Apache 2.0 from client to server, so apps take full-stack control while users keep full ownership.

2/ Keplr has been trusted by over two million users for secure, reliable self-custody. As apps scale to mainstream users, one question keeps coming up: how do you onboard instantly without seed phrases, extensions, or unfamiliar wallet flows? Oko is built for that.

3/ Embedded wallets reduce friction, but they often introduce new problems: • closed-source infra that can’t be inspected • app-specific wallets that fragment identity and assets • no clear way to migrate providers • ownership models where users lack full control Oko takes a different approach. It removes friction without creating lock-in, so apps onboard users quickly while staying transparent and fully independent.

4/ How Oko works Create a wallet in seconds with an email or social login—no seed phrase, no extension. • Fast onboarding (~10 seconds): create a wallet instantly with email or social login • Non-custodial MPC security: signatures are produced via Threshold Signature Scheme (TSS), where keys are split into multiple shares; no single party, including Oko, ever holds the full key • One wallet across apps: a single portable identity instead of fragmented, app-specific accounts • Multichain from day one: Cosmos and EVM at launch, with rapid expansion planned • Programmatic signing ready: architecture designed for safe automated and agentic flows

6/ Oko is built for apps that want smooth onboarding and long-term control: • DeFi apps aiming for high conversion without added custodial risk • Social apps that want one portable identity instead of separate wallets • Enterprise apps needing transparent, auditable infra