CC3 testnet · block-anchored reads
Checking V3 deployment truth
Pinning core code, wiring, factory inventory, registry releases, and proof-job counts to one finalized CC3 block.
Current V3 core · deployment and activation
Checking the current core and capped testnet pilot.
These addresses belong to the current core recorded in deployments-v3-current.json. The capped testnet pilot activation is recorded in activation-v3-current.json. This terminal checks deployment and facility state at the displayed block; manifest records alone do not establish current state.
Finalized state anchor
Activation ledger
Five states, one honest boundary.
Deployed is not configured. Configured is not activated. Source-only is not live. External-gated is not complete.
Runtime code evidence
Current core addresses
Code presence and kernel-to-proof-jobs wiring are checked at the displayed block. They do not establish compatibility with the current artifacts or imply an audit.
| Contract | Address | Evidence |
|---|
Capped factory · complete inventory
Pilot lifecycle
| Facility | Status | Registered | Configured | Applied effects | Truth |
|---|
No activated pilot: the current capped factory contains no facilities at this anchored block.
Same finalized anchor · runtime code and wiring
Extension deployments
| Contract | Read | Value |
|---|
Repository capability
Extension addresses and local capabilities
Source-level contracts are labeled source-only until a verified deployment manifest and runtime code establish otherwise.
Off-chain dependencies
External-gated work
These gates cannot be completed by repository code or inferred from contract deployment.
Truth boundary
No market, reputation, or capital claim without evidence.
The activated facility is a fixed-supply demo-token testnet demonstration, not a live pilot with a counterparty. There is no independent audit. Items 5–6 are blocked on writability. Items 9–10 have deployed manifests: market — Deployed · empty · single project-operated attestor; pool — project-funded testnet allocation recorded in allocation-v3-portfolio-current.json, verified at block 5460383. The pool allocated 100,000 rUSD to its newly created facility 0x0C874e56AD2dC9789A63a9Bc63c08a5F6D3C82C8, backed by a 20,000 rUSD bond and issuer-attested policy deployment; the borrower then activated the facility. Investor and borrower used project-operated test tokens, not lender demand or external capital. The anchored extension section checks current state.
The superseded historical core remains a separate deployment record.
Operator quotes, agreements, settlements, and address history are shown only after enumerable on-chain records exist. No activity means no reputation score is invented.
A deployed mandate or pool does not establish deposited capital, allocations, or recoveries. Those claims require anchored state. No action adapter required by this mandate.