Wallet Development and Integration

We build and integrate custodial, non-custodial, MPC, smart account and embedded wallets. Our work covers key generation and storage, signing, policy controls, spending limits, multi-party approval, transaction simulation and account recovery. We support EVM chains, Solana, Hedera and Bitcoin across browser, web, iOS, Android and embedded experiences. We design recovery first, because it determines the custody model.

How it works

1
Map users, assets and custody
We define who holds keys, what they sign, on which devices, and what your regulator requires.
2
Decide to build or integrate
We compare custodial, non-custodial, MPC and smart account options on risk and time to market.
3
Design recovery
We work through lost device, forgotten seed phrase, unavailable guardian and compromised user. Each answer shapes the architecture.
4
Prototype the critical journeys
We build onboarding, signing, approval, failure and recovery flows, then test them with real users.
5
Own the key handling
A security specialist reviews every key and signing path. You see working demos every week.
6
Test the device matrix
We cover older Android devices, browser variants and provider outages, where wallet failures concentrate.
7
Roll out in cohorts
We release to internal users, then a limited group, then everyone, with monitoring and runbooks ready.

Frequently asked questions

Should we build a wallet or integrate an existing one?

Integrate unless the wallet is your differentiator. Building one means owning key management, recovery, device compatibility, chain support and a permanent security obligation. Integration is faster and shifts much of that burden to a specialist provider. LimeChain recommends building only where the custody model, compliance requirements or user experience genuinely cannot be met by an existing provider, and says so before the build is scoped.

What wallet work has LimeChain done?

LimeChain built Hedera MultiSig, a multi-signature wallet creation and transaction tool for the Hedera network, and designed and built Shibhub, a consumer app combining wallet, DeFi and app access. Wallet and signing flows are also part of most onchain app engagements, including work on Status, which combined messaging, an Ethereum wallet and app discovery in one product.

What is the difference between MPC, smart accounts and traditional key storage?

Traditional wallets hold a single private key, making the key a single point of failure. MPC splits key material across parties so no single party can sign alone, which enables policy enforcement and reduces single-point compromise. Smart accounts move the logic onchain, enabling social recovery, spending limits, session keys and gas sponsorship. LimeChain chooses between them based on your custody, recovery and compliance requirements.

How do you design account recovery?

Recovery is designed before the wallet is built, because it determines the custody model. LimeChain works through what happens when a device is lost, a seed phrase is forgotten, a guardian is unavailable or a user is compromised, then chooses a mechanism such as social recovery, guardian sets, MPC share reconstruction, custodial reset or hardware backup. Recovery flows are prototyped and tested, since they are used exactly when the user is least calm.

Can the wallet enforce transaction policies and approvals?

Yes. Policy enforcement covers spending limits, allowlists and blocklists, multi-party approval above a threshold, time delays on high-value transfers, contract interaction restrictions, and simulation of a transaction's effects before signing. Whether enforcement sits in an MPC policy engine, a smart account or a backend service depends on the custody model, and that is decided in the security architecture phase.

Which chains and platforms can you support?

EVM chains, Solana, Hedera, Bitcoin and other major networks alongside the specific chains your product requires, across browser extension, web, iOS, Android and embedded contexts. The supported matrix is agreed at scoping and tested against real devices, browsers and providers, because wallet compatibility problems appear on the long tail of devices rather than in the primary test environment.

Do you handle security testing for wallets?

Yes. Wallet quality gates cover device and browser matrices, chain and provider compatibility, transaction and policy tests, recovery cases, performance, accessibility, privacy and operational drills, with penetration testing added according to the custody model and value at risk. Where a wallet holds client assets directly, LimeChain coordinates independent security review rather than relying on internal testing alone.

Rollup.codes

Matchstick

Gomu Gomu no Gatling

Gosemble

GiantSquid

Fruzhin

Polkadot Conformance Testing Suite

Hedera SDK

Hedera JSON RPC Relay

Hedera Local Node

Hedera Multisig

SOLmany Validators

Solana Transaction Tool

Gimlet

Zest

NEAR Javascript API

Wallet Development and Integration

How it works

Map users, assets and custody

Decide to build or integrate

Design recovery

Prototype the critical journeys

Own the key handling

Test the device matrix

Roll out in cohorts