Public chain state.
Latest public block height.
Public data freshness against live RPC.
Retention and serving posture.
Witness and verification posture.
Receipt export posture.
BIGHT intake.
BIGHT-priced upload lane.
Extended status matrixChain, storage, handoff, invoice, and refusal labels for deeper checks.
Chain IDAwaiting live data
Observed network label.
App heightAwaiting live data
Latest ABCI app height.
SyncAwaiting live data
Catching-up label.
Live refreshAwaiting live data
Browser chain refresh cadence.
ObservationAwaiting live data
Public evidence feed.
Total storageAwaiting live data
Effective usable capacity.
Used storageAwaiting live data
Usage and replica reservations.
Query laneAwaiting live data
Public query posture.
ExportsAwaiting live data
Snapshot/export posture.
QUAD handoffAwaiting live data
Boundary lane status.
Fallback refusalAwaiting live data
Blocked fallback paths are receipted.
Fallback receiptsAwaiting live data
Public count of refusal evidence.
Service invoiceAwaiting live data
Lawful work claim lane.
Epoch stepAwaiting live data
Runs by epoch, not block.
Retry guardAwaiting live data
Quiet persistence cadence.
Tracked workAwaiting live data
Public count.
Invoice pendingAwaiting live data
Waiting for handoff or acknowledgement.
Invoice blockedAwaiting live data
Retry state is recorded.
Invoice ackedAwaiting live data
Payment receipts accepted.
Live and cached status
The page separates live RPC labels from the cached public snapshot so stale data does not masquerade as chain truth.
Live RPCAwaiting live data
Browser-side chain labels refresh from the public RPC path.
Cached snapshotAwaiting live data
The static JSON feed is compared against live chain height.
Last updatedAwaiting live data
Latest public generated timestamp.
GatewayAwaiting live data
Public intake payment and work-lane status.
Condition labelsOutcome labels, not private mechanics or production claims.
WitnessAwaiting live data
MemoryAwaiting live data
StorageAwaiting live data
Storage sourceAwaiting live data
Chain app hashAwaiting live data
Latest block timeAwaiting live data
Snapshot heightAwaiting live data
Snapshot lagAwaiting live data
ReceiptsAwaiting live data
Receipt entitlementAwaiting live data
Public metadataAwaiting live data
Payload boundaryAwaiting live data
QueriesAwaiting live data
ExportsAwaiting live data
Handoff epochAwaiting live data
Invoice movementAwaiting live data
Product surfaceAwaiting live data
IBC and ICAAwaiting live data
Provider policyAwaiting live data
Proof policyAwaiting live data
Hot/cold policyAwaiting live data
Authority splitAwaiting live data
OSMO ingressAwaiting live data
Receipt and authority postureReceipt metadata can be public; payloads and downstream meaning stay bounded.
Receipt policy
Awaiting live data
Authority boundary
Awaiting live data
How to read this page
Infra status is a product readiness surface: it tells you which action lanes are usable, stale, pending, or receipt-gated.
Good signal
Fresh public labels for memory, proof, storage, receipts, query, exports, and service handoff.
Pending signal
Staged or pending labels mean a lane is visible but not making a service claim yet.
Bad signal
Stale, unavailable, or failed labels should be read as a public observation issue until refreshed.
Separate gate
IBC, ICA, and Interop are not claimed live until relayer evidence and scoped packet handling are visible.
Receipt rule
The original receipt is included with the work. Later proof, reissue, reconstruction, retention, linkage, and challenge work are Infra memory services.
Payload rule
Receipt metadata can be queryable while private payload bodies stay redacted unless the source marks them public.
Independent checks
Readable cards come first. Machine-readable files remain available for indexers, reviewers, and independent snapshots.