

Archon public report
ArchonProofRegistry
Mantle Mainnet · scan depth full-report · generated 6/16/2026, 1:07:18 AM
Risk Score
25
Archon completed a read-only Mantle Mainnet audit of ArchonProofRegistry and found 4 deterministic findings. The highest-priority issue is Timestamp, with risk score 25/100 based on severity-weighted findings. The contract uses block timestamps for proof anchoring, which can be manipulated by miners. Review the recommended fixes and run regression tests before deployment.
Findings
| Severity | Finding | Location | Confidence |
|---|---|---|---|
| low | Timestamp The contract uses block timestamps for proof anchoring, which can be manipulated by miners. | ArchonProofRegistry.sol:37 | 60% |
| low | Timestamp The function checks if a proof is anchored based on the timestamp, which can be influenced by miners. | ArchonProofRegistry.sol:65 | 60% |
| low | Review calldata parameter width The function proofHashAt uses a uint256 parameter which may be optimized for gas usage. | ArchonProofRegistry.sol:73 | 70% |
| info | Cache repeated storage read The function checks the timestamp of a proof in storage multiple times, which can be optimized. | ArchonProofRegistry.sol:44 | 80% |

