Question 1

How does the weekly cancellation actually work?

Accepted Answer

End 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.

Question 2

What if I'm not blown away by the work?

Accepted Answer

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.

Question 3

Why don't you track hours?

Accepted Answer

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.

Question 4

What does 'expectations detached from reality' mean?

Accepted Answer

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.

Question 5

How much does an ERC-4337 implementation cost?

Accepted Answer

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.

Question 6

Should we build a smart account or use Safe, Kernel or ZeroDev?

Accepted Answer

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.

Question 7

Who pays the gas, and what stops people from draining the paymaster?

Accepted Answer

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.

Question 8

Can you make this work inside MetaMask rather than a new wallet?

Accepted Answer

Yes. That is exactly what the MetaMask Snap does: 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.

Question 9

What happens when a user loses their device?

Accepted Answer

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.

Account Abstraction Development

What We Do

How we approach account abstraction

When account abstraction is not worth it

Building smart accounts, or fixing some?

Proof, not promises

What clients say

FAQs

More in Web3 & Blockchain

Get to know us