Account Abstraction Development Company | Wavect
HomeServicesWeb3 & BlockchainAccount AbstractionAccount AbstractionSmart accounts, gas sponsorship and recovery that survive contact with real users. We have shipped account abstraction to production. . .
HomeServicesWeb3 & BlockchainAccount AbstractionAccount AbstractionSmart accounts, gas sponsorship and recovery that survive contact with real users. We have shipped account abstraction to production alongside Boba Network's team, including natively inside MetaMask. Cancel any week. Last week refunded if we didn't blow you away. No hours tracked. 3 SDKsBackend, contract and frontend, reverse-engineered from undocumented infrastructure and still liveSee the case studyMetaMaskAccount abstraction brought natively into the wallet users already trustSee the case study// 01What We DoAccount abstraction is easy to demo and hard to operate. The difficulty is not the smart account, it is sponsorship economics, abuse, and recovery when a real user loses a device. Smart Account ImplementationERC-4337 accounts, either from a proven base or custom where you need it. Safe, Kernel and ZeroDev evaluated against your caseCustom validation logic where the base does not fitDeterministic addresses and counterfactual deploymentMigration from existing EOA usersPaymasters and SponsorshipGasless is a business decision before it is a technical one. Sponsorship policy tied to real unit economicsAbuse prevention and rate limitingERC-20 paymasters for pay-in-token flowsSpend caps, alerting and kill switchesBundler and Infrastructure IntegrationThe parts that break quietly in production. Bundler selection and fallbackEntryPoint version handlingUserOperation debugging and observabilitySelf-hosted versus managed trade-offsSession Keys, Passkeys and RecoveryThe UX that makes a smart account worth having. Scoped session keys with real expiryPasskey and WebAuthn signersSocial and guardian recoveryDevice loss handled as a normal caseProduction SupportWe have run this against infrastructure that changed under us without notice. Monitoring on sponsorship spend and failure ratesUpgrades across EntryPoint revisionsIncident response under retainerSDK maintenance as the spec moves// 03When account abstraction is not worth itSkip it when your users are already comfortable with a wallet and the transaction volume per user is low. The smart-account deployment cost, the paymaster balance you have to fund, and the extra failure surface all have to be paid for by something. If your product has few high-value transactions from crypto-native users, a plain EOA and a good signing UX will beat a smart account on both cost and reliability. Sponsorship in particular is a recurring expense that scales with abuse, not with revenue, unless you design the policy carefully. Building smart accounts, or fixing some?Tell us the wallet, the chain and who your users are. You get an architecture recommendation and a number. // proofProof, not promises3 SDKsBackend · Contract · FrontendThree-layer Hybrid Compute SDK suite (backend, contract, frontend), built with Boba's team against undocumented infra, still in …TypescriptSolidityHardhatMetaMaskNative IntegrationSmart wallets with Hybrid Compute, inside the wallet users already trust, built with Boba's team against MetaMask's Snap sandbox. TypescriptMetaMask SnapsSolidity50+Target User AgeMulti-browser extension, Tron added, iOS + Android via multiple routes, built on a forked Enkrypt, debt paid down release by …VueJSTypescriptNestJSThese are selected projects, not our full portfolio. We have shipped 75+ products since 2018. What clients sayGoogleTHE agency to go for blockchain development. Super experienced and highly professional team. Love to work with them. Richard LeitgebOriginalLinkedInFor technical questions on blockchain and NFT, I always come back to Kevin. He has familiarized himself very well in this area, and the expertise he brings is certainly essential for projects like these. I can only recommend everyone get in touch with Kevin on these topics. Fritz FahringerKlarheit vor KITrustpilotExperts in smart contract development. CJOriginalIndependently rated 4. 5/5 on TrustpilotRead the reviewsFAQsHonest answers about ERC-4337 deliveryEnd any week, with one message. No notice period, no exit interview, no fine print. We invoice weekly, so the most you’re ever committed to is the current week. It’s in your contract: tell us, and we refund that week. No questions, no invoices to dispute, no calls to escalate. The only rule: refunds apply to the most recent week. Because hours are the wrong metric. If we’re optimizing for hours billed, we’re not optimizing for your outcome. The deal is simpler: every week, we earn the next one. If we don’t, you don’t pay. We’re free to spend zero hours or sixty. What matters is whether you’re blown away. We work with operators, not lottery winners. If a request would require breaking physics, the law, or a third party’s systems, we say so, and if we can’t align, we walk. The guarantee is mutual: you can fire us any week; we can also fire ourselves. A straightforward integration on an existing account implementation with a managed bundler and a simple sponsorship policy is typically four to eight weeks. A custom account with its own validation logic, a paymaster with real abuse controls, and a cross-platform wallet is more like three to six months. Production-grade account abstraction sits in the same band as our other infrastructure work, starting around €100k. The largest cost drivers are custom validation, sponsorship policy, recovery, and integration with an application that already has users. Use the existing implementation unless you have a specific reason not to. They are audited, widely deployed, and someone else maintains them across EntryPoint upgrades. Custom becomes justified when your validation logic genuinely does not fit, for example unusual multi-party signing or compliance constraints. We will tell you which case you are in before you pay us to build anything. You do, and nothing, unless the policy is designed for it. A paymaster is a funded account that strangers can spend. We scope sponsorship to specific contracts and function selectors, cap spend per user and per period, add rate limiting, and alert on burn rate. Treat the sponsorship budget as a line item with a monthly number, not as a technical detail. Yes. That is exactly what theMetaMask Snapdoes: it brings Boba Network’s account abstraction and Hybrid Compute smart wallets into the wallet users already have, built with Boba Network’s team against MetaMask’s Snap sandbox. Asking users to install a new wallet is a real conversion cost, and often an avoidable one. Whatever you designed for, which is why it has to be designed. Options are guardian-based social recovery, a passkey synced through the platform keychain, or a time-locked recovery key. Each trades security against support burden differently. Picking one late, after users hold real balances, is considerably more expensive than picking one early. // More inMore in Web3 & Blockchain// Get to know usGet to know usLong-term relationships over quick wins.