Web3 readiness check: 11 points before launch
A launch checklist for smart contracts and dApps. Tick what's already in place across 11 areas, from contract security to incident recovery. The summary shows which gaps are the expensive ones.
Free, with results on screen and no email needed. This is a readiness check, not a smart contract audit.
11 checkboxes · Results on screen
About this check
Why these 11 areas
The contract is only one place an on-chain product can fail. The others are off-chain: the keys, the indexer, the database, and the people on call when something breaks. An indexer that counts a deposit twice shows a user money they don't have, even when the contract is flawless.
Four of the 11 are marked high impact: smart contract security, wallet security, key management and indexing. A gap in one of these can turn an incident into lost funds or wrong balances, so they count for more.
How the summary is worked out
Each item has a weight: 3 for the four high-impact areas and 2 for the rest. If any high-impact item is unticked, the summary says how many. With no high-impact gaps, covering 85% or more of the weighted total reads as broad coverage; 60% or more as core controls in place with operational gaps; anything lower as significant gaps.
Next steps list up to five of your gaps, high-impact first.
What to do with the result
Close the high-impact gaps first. Then the operational ones: a backup you have actually restored, a runbook someone has rehearsed, and an alert that fires when your database and the chain disagree. If you launch soon, bring the result to a call and we'll go through each gap and what closing it involves.
This is not an audit
A ticked box says a control exists, not that it works under failure. Our review is engineering diligence, not a substitute for a formal audit. For anything holding real value, we recommend an independent audit before mainnet, and we prepare the code and documents for it.