Wallet and custody audit
Where the keys live is where the money is lost.
What it is
A wallet is not one artefact. It is key generation, storage, the signing flow, the recovery path, the policy engine that decides what a signature is allowed to authorise, and the interface a human reads before approving.
Most wallet losses come from that last part and from recovery, not from the cryptography. We review all of it, including the parts that are not on chain.
What we examine
- Multisig configuration: thresholds, signer sets, and what one compromised signer achieves.
- Smart accounts and account abstraction: session keys, paymasters, validation logic.
- Key generation, storage and backup, including the hardware and the humans around it.
- Recovery and rotation paths, which are the most common route to total loss.
- Spending policies and allow-lists: what a signature can authorise and what it cannot.
- Signing interface review: what the approver actually sees against what they are signing.
- Blind-signing exposure and transaction simulation before approval.
What you get
Severity-ranked findings across contracts, key handling and the signing flow.
A signer and threshold map with the compromise scenarios each configuration allows.
Recovery procedure review, written so the people who would run it can follow it.
A re-audit of your fixes, included.
How the engagement runs
- 01
Scope
Wallet type, key architecture, policies and recovery design. Fixed quote.
- 02
Review
Contracts, key handling, policy engine and signing path, examined together.
- 03
Attack
Compromised signer, stolen device, malicious transaction, lost key.
- 04
Report
Findings with proof of concept, then verification of your fixes.
What we cover
Languages
- Solidity
- Vyper
- Rust
- Move
- Cairo
- Go
- TypeScript
- Huff
- Yul
Chains
- Ethereum
- Solana
- BNB Chain
- Polygon
- Avalanche
- Arbitrum
- Base
- TRON
- Optimism
- Cardano
- Polkadot
- Cosmos
- NEAR
- Aptos
- Sui
- TON
- Hedera
- Algorand
- Stellar
- Starknet
- ZKsync Era
- Linea
- Sei
- Sonic
- Scroll
- Mantle
- Injective
- Cronos
- Celo
- Gnosis
- Fantom
- Kaia
- Ronin
- Immutable
- Blast
- Berachain
- Monad
- Hyperliquid EVM
- Stacks
- Rootstock
- Kava
- Osmosis
- MultiversX
- Conflux
- Telos
- Theta
- Chiliz
- XDC Network
- Filecoin FVM
- Ontology
- WEMIX
- Fuel
- Taiko
- Polygon zkEVM
- BOB
- Fraxtal
- Mode
- ZetaChain
- Metis
- Manta Pacific
- IOTA EVM
- Neo X
- Unichain
- World Chain
- Soneium
- Abstract
- Ink
- Movement
- Plume
- Etherlink
- EOS
- Flow
- Zilliqa
- Harmony
- Moonbeam
- Astar
- Aurora
Not listed? Ask. If it runs smart contracts, we almost certainly review it.
Questions we get asked
Do you need our private keys?
Never, under any circumstances. Everything is reproduced on test keys and forks. Anyone asking a client for production keys is the threat, not the auditor.
Do you review hardware wallets?
We review how your system uses them: derivation, approval flow, what the device displays. Auditing the device firmware itself is the vendor's own scope.
Is account abstraction covered?
Yes: validation logic, session keys, paymasters and bundler assumptions, which is where most novel account-abstraction bugs have appeared.
Often bought with
Web3 and protocol audit
Line-by-line review of contracts, chain layer and upgrade paths, with proof-of-concept for every finding.
Penetration testing
Web, mobile, API, cloud and key infrastructure tested the way a real intruder would.
Neutral transaction verification
A neutral third party checks both sides of a large transfer before it happens.
Tell us what you are building and when you launch. Fixed quote in 48 hours.
Get a fixed quote