MetaMask Snap
Boba's Account Abstraction stack, native inside MetaMask. No new wallet to learn.
Boba Network’s Account Abstraction enables smart wallets with Hybrid Compute, executing complex on-chain/off-chain logic in one flow. The Snap brings this natively into the world’s most-used Web3 wallet.
Overview
Boba Network’s Account Abstraction enables smart wallets with Hybrid Compute, executing complex on-chain/off-chain logic in one flow. The Snap brings this natively into the world’s most-used Web3 wallet.
What's the challenge?
MetaMask Snaps are powerful and tightly sandboxed. Strict permission model, opinionated execution context, and a boundary that runs straight through what Boba’s Account Abstraction needed to do. Make smart wallet management feel native, without fighting the sandbox or teaching users anything new.
MetaMask's sandbox doesn't bend. The use case had to.
Snaps are powerful and tightly sandboxed by design. For our use case, the sandbox was a constant negotiation. Application whitelisting, what a Snap can call, what it can persist, what crosses the boundary, every limit got routed around, not fought. The result lives inside MetaMask's rules. The only kind of Snap that ships.
What We Did
Full Account Abstraction inside a sandbox that doesn’t let you cheat. Engineering inside Boba’s build, we put a clean abstraction layer between Boba’s AA stack and the Snap runtime up front, a sprint of cost, testable end-to-end, survived every MetaMask runtime update. The Snap itself, AA wiring, smart wallet management, all inside MetaMask’s native UX. Boba users manage Hybrid Compute smart wallets without leaving the wallet they already use.
Outcomes
What We Learned
Snaps are powerful but opinionated. Their permission model and sandbox force careful interface design early. The integration pushed us to build a clean abstraction layer between Boba’s AA stack and the Snap runtime, which made the whole system more testable. When that boundary fails, the UserOperation debugger helps freeze the exact representation locally.
Questions about this project
What is MetaMask Snap?
Boba Network’s Account Abstraction enables smart wallets with Hybrid Compute, executing complex on-chain/off-chain logic in one flow. The Snap brings this natively into the world’s most-used Web3 wallet.
What was the challenge in the MetaMask Snap project?
MetaMask Snaps are powerful and tightly sandboxed. Strict permission model, opinionated execution context, and a boundary that runs straight through what Boba’s Account Abstraction needed to do. Make smart wallet management feel native, without fighting the sandbox or teaching users anything new.
What did Wavect do for MetaMask Snap?
Full Account Abstraction inside a sandbox that doesn’t let you cheat. Engineering inside Boba’s build, we put a clean abstraction layer between Boba’s AA stack and the Snap runtime up front, a sprint of cost, testable end-to-end, survived every MetaMask runtime update. The Snap itself, AA wiring, smart wallet management, all inside MetaMask’s native UX. Boba users manage Hybrid Compute smart wallets without leaving the wallet they already use.
What were the outcomes of the MetaMask Snap project?
- MetaMask, Native Integration
- Smart Wallets, Hybrid Compute Enabled
How did Wavect work with MetaMask Snap?
Engagement: Fullstack Build. Engagement size: Monthly retainer. Year: 2025.
Which tech stack did Wavect use for MetaMask Snap?
Typescript, MetaMask Snaps, Solidity, Ethers.js.
What did Wavect learn from the MetaMask Snap project?
Snaps are powerful but opinionated. Their permission model and sandbox force careful interface design early. The integration pushed us to build a clean abstraction layer between Boba’s AA stack and the Snap runtime, which made the whole system more testable. When that boundary fails, the UserOperation debugger helps freeze the exact representation locally.
Want outcomes like this?
Tell us what you're building. We'll tell you whether we're the right team for it.
Get in touch