Web3
Put on-chain only what needs to be on-chain, and secure all of it.
A Web3 product is mostly ordinary software around a small on-chain core. We define that boundary, build both sides and review the security of the contracts, keys, wallets and backend that connect them.
Contracts, keys and wallets
Smart-contract review, key management and custody boundaries, and control over admin and upgrade functions.
Product around the chain
The backend, APIs and user interface around the on-chain core, including indexing and event handling.
Operations and audit
Node and RPC dependencies, monitoring, and the records auditors and regulators ask for.
Where discovery starts
What should a user be able to do, and why does it need an on-chain component?
Follow-up questions depend on your answer. Not sure is always a valid answer.
Systems we usually work with
- Business use case and on-chain boundary
- Wallet and identity integration
- Smart-contract review
- Key management and custody
- Node and RPC dependencies
- Audit trails
We do not advise on asset value or investment returns.
Describe what users need to do.
Discovery records the use case, what has to be on-chain and who holds which keys. We do not advise on asset value or investment returns.