Verify a deployment
Use the ATP Explorer verification page to compare the recorded deployment with the chain at one finalized block.
The verification page checks that the contracts on a network are the ones the deployment record says they are. You do not need a wallet or any setup. Open explorer.sinera.io/verify.
Implementation candidate
What the page checks
The page compares each binding of the recorded deployment with what the chain says at one finalized block. The bindings are:
| Binding | What is compared |
|---|---|
| Chain id | The chain the deployment is recorded for |
| Protocol version | The ATP version recorded for the deployment |
| Configuration | The admission config the deployment is bound to |
| Deployment block | The block where the deployment was recorded |
| Module address | The address of each protocol contract |
| Runtime code hash | The hash of the code deployed at each module address |
A difference appears on its own row, so you can see exactly which binding does not match.
Run a check
- Open explorer.sinera.io and choose a network in the header.
- Open Verification from the sidebar, or go to
/verify. - Read the result. Each row shows the recorded value next to what the chain returned.
If the selected network has no recorded deployment, the page says there is nothing to verify and asks you to choose a deployed network. Today that means BSC Testnet. Solana is listed as not deployed.
If the chain cannot be read, the page shows "The deployment could not be checked" with the reason. Try again later.
Related checks
Configuration also runs a live check. Its Modules tab shows each contract's address, whether code is present, and whether its runtime hash matches the record. A red marker on a Configuration tab means the check found a mismatch there. See Explorer pages.
When the deployment does not match
The Explorer does not show ledger data while the deployment does not match its record. The ledger pages then show Ledger unavailable, and Configuration and Verification keep working so you can see what differs. Nothing is substituted. See Networks and data sources.
Verify costs more than a normal read
/verify counts as a heavier read for load limits (it costs 4 units, against 2 for a transaction read), and it is limited by page loads per minute per client. If you exceed the limit, the Explorer answers "Too many requests" with the number of seconds to wait. Operators can change the limits. See Self-host the Explorer.