The smart contract security checklist we run before every mainnet launch

Smart contracts are immutable and hold real value. A single bug can be catastrophic, so every contract we ship passes this checklist.

Design

• Minimal, well-documented roles with explicit access control
• Clear upgrade strategy (or none) agreed before writing code
• Emergency pause and recovery paths for high-value protocols

Implementation

1. Checks-effects-interactions and reentrancy guards everywhere value moves
2. Safe math and explicit handling of token decimals
3. No reliance on tx.origin or block timestamps for critical logic
4. Oracle manipulation resistance with TWAPs or multiple sources

Testing

We target 100% line and branch coverage, run property-based fuzzing with Foundry and simulate attacks on a mainnet fork.

Launch

Deploy to testnet first, verify source code on the explorer, use a multisig for admin keys and monitor events from block one.

Security isn’t a phase at the end — it’s the way the contract is written from the first line.