height 25522 of 25522 on the network. 9 peer(s) connected, 91 in its peer directory; 2818 block(s) followed and 2298 pulled in by sync since this follower started. Caught up: this follower holds every block any peer has claimed, so every panel below is the whole chain. Genesis 1cf8655125cc1bbb…, producers genesis.
What this follower is, locally
Following 7 seed(s) — their addresses are not published here, for the reason the peer table gives. Its store is held under its own Cerberus lease — no other node’s store is opened, touched or stopped.
Contracts
Contracts here are verified by construction: the deployment record carries the source, every node recompiled it, and the address was derived from the resulting bytecode.
Nothing has been deployed on this chain yet
A contract exists here only once a deployment record carrying its source is inside a block this node holds. No block it holds carries one, so there is nothing to list — and that is the chain’s answer rather than a gap in this page.
What would put something here
- a deployment record carrying the source, which every node recompiles for itself
- an address derived from the resulting bytecode, which is what makes a contract here verified by construction rather than verified by somebody uploading a file afterwards
- a call to it, which is then listed on the contract’s own page with its arguments
Contract templates to start from (drafts, not deployed contracts) · The contract ledger, and the rules it enforces · What protects a deployment · Every block this node holds
Contract templates: the Daedalus catalogue a deployer starts from, with each draft’s source, digest and measured gas.