Wallets

Web3 Wallet Development

From MetaMask-native smart wallets to onboarding where the user never learns the word wallet. We have shipped both.

Cancel any week. Last week refunded if we didn't blow you away. No hours tracked.

MetaMask Native smart-wallet integration built against the Snap sandbox See the case study
Invisible Social login and wallet creation on a live marketplace, no crypto jargon shown See the case study

// 01

What We Do

The wallet decision determines your conversion rate, your support load, and who is liable when keys are lost. It is worth getting right before you build.

Embedded and Invisible Wallets

Wallet creation behind a social login, for users who are not here for crypto.

Social login to wallet in one step
No seed phrase shown to the user
On-chain primitives behind familiar UX
Progressive disclosure for users who want the keys

MetaMask Snaps

Extend the wallet your users already have instead of shipping a new one.

Snap development against the sandbox
Custom chains and signing flows
Smart-account features inside MetaMask
Permissions and review-process handling

Key Management

MPC, smart accounts, or plain EOA, chosen against your actual liability.

MPC and threshold-signature architectures
Hardware and platform keychain signers
Custodial versus non-custodial consequences
Key rotation and recovery design

Multi-Chain Wallet Applications

Full wallet products across mobile and web.

Multi-chain account and balance handling
Transaction simulation before signing
Token and NFT display that stays fast
Mobile and browser-extension delivery

Wallet Model Selection

We will map the options against your users before writing code.

EOA, smart account, MPC, embedded, custodial
Regulatory consequences of holding keys
Support-load and recovery cost per model
Migration path if you pick wrong

// 02

How we approach wallets

Most wallet projects fail on onboarding, not on cryptography. On Afoma we layered on-chain primitives behind social login so the user never saw crypto jargon, and the client’s public review notes the speed of delivery. On the MetaMask Snap, with Boba Network’s team, we went the other way and extended the wallet users already trust. Which of those is right depends entirely on who your users are. See also account abstraction development and the Web3 hub.

// 03

When you should not build a wallet

Building your own wallet is rarely the right answer. If your users are crypto-native, connect to the wallets they already have and spend the budget on your product instead. If they are not, an embedded wallet from an established provider will usually beat a custom build on both time and risk. Custom wallet work earns its cost when you have an unusual signing model, a chain nobody supports properly, or a UX requirement that off-the-shelf providers cannot meet. Also be honest about custody: the moment you can move user funds, you have taken on a regulatory posture that is expensive to unwind.

Need a wallet, or need to avoid building one?

Tell us who your users are and what they have to sign. We will map the options honestly, including the ones where you build nothing.

Get a quote

// proof

Proof, not promises

MetaMask Native Integration

Smart wallets with Hybrid Compute, inside the wallet users already trust, built with Boba's team against MetaMask's Snap sandbox.

Typescript MetaMask Snaps Solidity

Web3 Social Login Live in Production

Live marketplace, on-chain primitives, no crypto jargon, social login + invisible wallet creation.

Typescript Solidity Ethers.js

50+ Target User Age

Multi-browser extension, Tron added, iOS + Android via multiple routes, built on a forked Enkrypt, debt paid down release by …

VueJS Typescript NestJS

These are selected projects, not our full portfolio. We have shipped 75+ products since 2018.

What clients say

Google

THE agency to go for blockchain development. Super experienced and highly professional team. Love to work with them.

Richard Leitgeb

Original

For 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 Fahringer Klarheit vor KI

Trustpilot

Experts in smart contract development.

Original

Independently rated 4.5/5 on Trustpilot Read the reviews

Clutch Top Web3 Development in Austria 2026 award for Wavect

Verified on Clutch · 2026 Top Web3 Development in Austria View our Clutch profile

Clutch Top Blockchain Company in Austria 2026 award for Wavect

Verified on Clutch · 2026 Top Blockchain Company in Austria View our Clutch profile

FAQs

Honest answers about wallet delivery

How does the weekly cancellation actually work? +

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.

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

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.

Why don't you track hours? +

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.

What does 'expectations detached from reality' mean? +

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.

MPC wallet, smart account, or embedded wallet: which do we need? +

Smart accounts give you programmable rules such as sponsorship, session keys and recovery, at the cost of a deployment per user and chain-by-chain support. MPC splits a key across parties and looks like a normal address to every chain, which is why custodial and enterprise products favour it, but recovery depends on the provider. Embedded wallets are the fastest route for non-crypto users and hand most of the responsibility to a vendor. Most consumer products want embedded plus a smart account underneath; most institutional products want MPC.

Can users sign up without ever seeing a seed phrase? +

Yes, and for consumer products they usually should. On Afoma wallet creation happens behind a social login and the user never sees crypto jargon. The trade-off is where recovery authority sits, so that decision has to be explicit and disclosed rather than hidden.

Is it cheaper to build a MetaMask Snap than a standalone wallet? +

Substantially, and it usually converts better too, because there is no install step and no new trust relationship. A Snap extends MetaMask with custom chains, signing flows or smart-account features. The limits are MetaMask’s sandbox and review process, so it fits when your users already have MetaMask and does not fit when you need full control of the interface.

Non-custodial or custodial? +

Non-custodial unless you have a specific reason and a licence. If you can move user funds you are custodial in substance regardless of how the marketing reads, and that carries regulatory obligations. We default to non-custodial architectures and will tell you plainly when a design has quietly crossed the line.

What does wallet work cost? +

Integrating an existing embedded-wallet provider into a product is typically a few weeks. A MetaMask Snap or a smart-wallet layer on an existing application is larger but bounded. A full multi-chain wallet product with custom key management is infrastructure work, starting around €100k and 3-6 months. We would rather scope you into the smallest of those that actually solves your problem.

// More in

More in Web3 & Blockchain

Web3 & Blockchain

The hub: dApps, payments, scaling and the chains we ship on. Routes to the capability you actually need.

Smart Contract Development

Solidity and Rust from architecture through mainnet, with third-party audit coordination and monitoring.

Account Abstraction

ERC-4337 smart accounts, paymasters, session keys and recovery. Three production SDKs behind us.

Cross-Chain Bridges

We built a six-chain production bridge, which is mostly why we will tell you when not to build one.

Zero-Knowledge

Privacy by cryptographic proof, not policy: ZK identity, private transactions, and ZK rollups.

// Get to know us

Get to know us

Long-term relationships over quick wins.

Read our Blog

No BS Around Tech Podcast

Get some Impressions