Infra Testnet - Readiness

Current public update

Infra Testnet has a separate public surface. Mainnet and production status are not claimed here.

What is visible

Public labels for witness, memory, storage, receipts, queries, exports, role states, and generated aggregate counts.

What is pending

Public exporter wiring, production status, provider onboarding, and any public value-bearing claims.

What to inspect

Open Status for aggregate state, Proof for evidence categories, Roles for public role boundaries, and Data for raw public JSON.

Infra readiness is about memory and proof behavior, not QUAD block production.

Public labels remain explicit. Staged, testing, live, stale, unavailable, and not-live states are named plainly.
Exporter path is public-safe. Generated data does not expose private thresholds, operator procedure, credentials, or exploit-sensitive timing.
Role boundaries stay readable. Writers, Keepers, Indexers, and Verifiers are explained without turning the page into a private manual.
Cross-chain meaning stays separate. Infra records and proves claims; it does not become Core truth, Bridge admission, or Liquid settlement.
No entitlement framing appears. Testnet participation is technical testing and does not create reward eligibility or future claim.

Public chain services, RPC, indexers, and Infra daemons require their own host class. Static website hosting stays separate.

Testing host

checking

Public candidate

checking

Website boundary

checking

Public-affairs guardrails for Infra testing.

No node setup to earn tokens.
No real-money payment for testnet access.
No seed phrase, private key, or recovery phrase entry.
No DePIN, AI, raw compute reward, GPU reward, mining, airdrop, or allocation framing.
No production, audit, safety, or mainnet claim unless public evidence exists.