Invoice persistence
Invoice state stays visible until payment, refusal, expiry, or a terminal receipt closes it.
Awaiting live data
InfraVerifiable Storage
Wallet, purchase, storage, proof, retrieval, contracts, and status are kept as separate product lanes.
Invoice state stays visible until payment, refusal, expiry, or a terminal receipt closes it.
Awaiting live data
Receipt activity is public evidence first. Payload bodies and downstream chain meaning stay bounded.
Awaiting live data
Public CometBFT and ABCI labels behind the receipt page.
Top-level labels from the public data feed.
Awaiting live data
Service handoff and epoch labels.
Awaiting live data
Reserve, escrow, quarantine, payable, receivable, deferred service, repair reserve, relayer/host gas float, and restricted balances stay separate.
Awaiting live data
Governance, Foundation, External Affairs, Reserve, Mint, service, provider, invoice, and bridge labels stay separate.
Awaiting live data
Public accounting shows what money is doing without implying that product BIGHT is reserve backing.
Awaiting live data
Public evidence categories without private thresholds.
Awaiting live data
Awaiting live data
Awaiting live data
Effective capacity is visible as public posture, not as private provider procedure.
Service payments stay on product rails and do not become reserve backing by implication.
Awaiting live data
Outside value rails are separate from product BIGHT work payments and require recorded evidence before reserve claims move.
Awaiting live data
Awaiting live data
Awaiting live data
Awaiting live data
Awaiting live data
Awaiting live data
Awaiting live data
Awaiting live data
Awaiting live data
Service-work payables, reserve yield support, and rail refunds are separate receipt families.
Awaiting live data
Awaiting live data
Generated public events from the latest snapshot. These are status and receipt labels, not private operator logs.