TL;DR:
Apillon’s Embedded wallets work on both EVM-compatible and Substrate-based chains. Here’s how we pulled it off — and why it matters for UX and devs alike.
Most users bounce at the first sign of MetaMask. And while tools for EVM onboarding are evolving, Substrate chains (hello, Polkadot) have mostly been left behind — until now.
We wanted to fix that.
Here’s what we built:
- An embedded wallet that works across EVM and Substrate
- Powered by MPC (multi-party computation) for key management
- Running on Oasis confidential smart contracts for privacy
- Integrated via SDK or API — no wallet apps needed
Why support Substrate?
Substrate chains (like Polkadot parachains) offer flexibility, scalability, and modular governance. But when it comes to user onboarding, the tooling gap is real.
Most wallet solutions are:
- EVM-only
- Custodial (or too centralized)
- Confusing to integrate
Apillon’s Embedded wallets change that:
- One SDK, multiple chain types
- One UX, no wallet download
- No seed phrases, ever
How it works
- User logs in with email and verification code
- Private key is generated using MPC — never stored or exposed
- Key signs transactions inside a secure Oasis enclave
- Chain-specific adapters handle formatting for EVM/Substrate
For devs, the SDK abstracts all of this. Just integrate and build.
Live success story: Lumen games, a Polkadot gaming platform
Lumen Games used embedded wallets on a Polkadot parachain to turn players into earners — without requiring wallet installs. Their drop-off rate dropped. Their UX improved. Their users? Didn’t even realize they were using Web3.
“We didn’t have to explain seed phrases or gas. That was the whole point.” – Lumen team
Want to try it?
You can:
- Try the demo video
- Check out the repo
- Start building with 1200 free credits - no wallet knowledge needed.
This article was initially published on Apillon blog.
Top comments (0)