Contract testing
Foundry unit, fuzz, and invariant tests verify immutable terms, exact transfers, claim limits, and failed-transfer behavior.
Audit program
Verify before a mainnet release.
The independent smart-contract audit is deferred for Development. A future mainnet release requires a separate approval and published release evidence.
Static analysis
The release plan requires Slither analysis and a review of each reported contract risk.
Published evidence
A future release record must identify the audited commit, contract artifacts, deployed bytecode, and report hash.
View contract records