System status
Every deployed contract and linked library is read from the chain and its runtime code hash is compared with the hash recorded when it was deployed.
Checking
Environment
–
Chain
–
Head block
–
Chain time
–
Code checks
–
Last checked
–
every 15s
Deployed contracts
| Contract | Kind | Address | Runtime code hash | Check |
|---|---|---|---|---|
| Waiting for the deployment evidence. | ||||
Build evidence
- Source commit
- –
- Evidence generated
- –
- Compiler
- –
- EVM
- –
- Pipeline
- –
- Optimizer runs
- –
- Metadata hash
- –
What this checks
- The RPC answers with the chain ID recorded in the deployment evidence.
- Every contract and linked library has code, and its keccak-256 runtime hash equals the recorded hash.
- Chain time comes from the pending block, which is the clock order deadlines and countdowns use.
- Explorer verification recompiles with the same profile shown under build evidence.