Scan
Read a contract's entries through Soroban RPC: what remains, what expires first, what it costs to keep alive, and whether the code entry is shared — or whether that cannot be determined.
The four kinds of entry
Three are recoverable. One is not.
instance
The contract's own state pointer.
archived
code
The compiled Wasm. Every contract built from it shares this one entry.
archived
persistent
Durable stored values.
archived
temporary
Disposable stored values. Gone permanently, with no restore.
deleted
Read from the network's own configuration: a temporary entry's minimum is 720 ledgers, about an hour. Our own temporary entry had 688 left when it was first sampled.
The thesis
One entry. Every contract built from that Wasm. They fail together.
A contract's instance can be healthy until December while the code it runs expires in October. Without the code it cannot execute, so the real expiry is the earliest entry — and that entry is shared by every contract deployed from the same Wasm.
of the rent
98%
is that one shared code entry — 8,116,648 of 8,264,289 stroops, across all four of guinea-pig A's entries. Scanning only its instance and code, the same entry is 99%: identical rent, different denominator. The scope travels with the number.
What the tool actually prints
The honest parts are the persuasive parts
A real scan of guinea-pig A. It reports what it read, says that a single-contract scan cannot settle whether the code entry is shared, and says that storage it was not given keys for is unread.
Coverage: known keys only — contract storage has NOT been fully enumerated.
CANZNTAW7DYMCZ6EAY5BP672H4AL2O2HVRBP4O4HRUEZRATHQRRLXL6L: 0 explicit data key(s)
No data keys were supplied, so any further entries are unread. A clean result covers only what was asked for, never the whole contract.
HEALTHY instance AAAABgAAAA…
contracts: CANZNTAW7DYMCZ6EAY5BP672H4AL2O2HVRBP4O4HRUEZRATHQRRLXL6L
remaining: 1,400,453 ledgers — live
ends at: ledger 6,025,589
approx: 2026-12-01T18:58:52.518Z (estimate — ledgers are the truth)
observed: ledger 4,625,136
health: HEALTHY — Above threshold.
HEALTHY code AAAAB8flXw…
contracts: CANZNTAW7DYMCZ6EAY5BP672H4AL2O2HVRBP4O4HRUEZRATHQRRLXL6L
⚠ sharing: code entries are shared by every contract built from the same Wasm.
This scan saw 1. Whether others depend on this entry cannot be
determined from a single-contract scan — pass them together.
remaining: 665,693 ledgers — live
ends at: ledger 5,290,829
approx: 2026-10-20T06:28:52.518Z (estimate — ledgers are the truth)
observed: ledger 4,625,136
health: HEALTHY — Above threshold.
! sharing-undetermined: Code entries are shared by every contract built from the same Wasm. This scan saw 1. Whether others depend on this entry cannot be determined from a single-contract scan — pass them together to see the real blast radius.
contracts: CANZNTAW7DYMCZ6EAY5BP672H4AL2O2HVRBP4O4HRUEZRATHQRRLXL6L
! coverage-limited: No data keys were supplied, so any further entries are unread. A clean result covers only what was asked for, never the whole contract.
contracts: CANZNTAW7DYMCZ6EAY5BP672H4AL2O2HVRBP4O4HRUEZRATHQRRLXL6L
Worst entry health: HEALTHY (threshold 17,280 ledgers)
Scan is PARTIAL — 2 issue(s). Absence is not health.
Captured on 2026-09-12 and committed at docs/evidence/2026-09-12-w2-review/scan-a-human.txt. Its ledger numbers are from that day; the dashboard reads the chain now.
How it works
Scan, watch, extend
Watch
A scheduled job re-reads the entries you configure and alerts before they cross the thresholds: seven days for a warning, one day to act.
Extend
Evergreen has no authority over your contract. Extending a TTL needs no permission from anyone — it is a property of the chain, not a promise from us. It can pay rent, and nothing else.