Start here
Use the product lanes first. Reserve and cross-chain signals remain visible, but they should not be the first thing someone has to decode.
Open reserve and cross-chain signals
Awaiting live data
Awaiting live data
Quote, Pay, Receipt, Retrieve
The browser can feel simple because the chain keeps quote, payment, proof, retrieval, and provider settlement as separate facts.
Price bytes, class, service tier, and policy into BIGHT before action.
Spend quoted BIGHT from the purchase path or contract account.
Keep the proof handle for later verification, retrieval, or reissue.
Use hot read, public-rented browse, private receipt checks, or cold restore.
What the receipt means
Infra receipts are product evidence. They make work inspectable without turning private payloads, reserve support, or another chain's policy into public claims.
Accepted work metadata such as quote, payment label, object hash, receipt class, admission state, proof posture, and the next service path.
Private payload contents, permanent availability outside declared terms, provider payout, reserve backing, downstream execution, or ownership rights.
The public label should downgrade to pending, stale, unavailable, refused, queued, or terminal instead of pretending the service is complete.
Use Infra
The main actions are product lanes. Status and raw data stay available, but they are not the first thing a visitor has to decode.
Use the quote-first purchase path to credit BIGHT to an Infra wallet after accepted payment proof.
Awaiting live data 02UploadChoose a file, storage class, service tier, and optional contract ID, then pay the BIGHT quote.
Awaiting live data 03VerifyPaste a receipt or handle to inspect hash, class, admission, proof, and payment labels.
Awaiting live data 04RetrieveQuery retained records and pay for hot download or cold restore when bytes need to move.
Awaiting live data 05ContractsCreate invoice-recipient-backed storage accounts for repeated or account-bound work.
Awaiting live data 06WorkStage receipt-backed work packets for opted-in Core, Bridge, and Liquid review paths.
Awaiting live dataWhy Use Infra
Infra is useful when a future reader needs more than a file link. It gives work a receipt, separates public metadata from private payloads, and makes later proof work a priced service instead of a vague support request.
Uploads return a receipt path that can be verified later instead of disappearing into a private support thread.
Hot, public-rented, private receipt, handle-mediated, and cold restore paths are labelled before bytes move.
Account-bound storage can track invoice recipient, storage class, pricing posture, and prepay state.
Boundary Ledger
- Purchase
- Awaiting live data
- Spend
- Awaiting live data
- Reserve
- Product BIGHT is excluded from reserve backing totals.
- Payload
- Awaiting live data
Proof Without Overclaiming
Infra can show live product progress while still refusing to overstate cross-chain, provider, reserve, or retention claims.
RPC and ABCI fields only count when public height and app-height checks agree.
Upload, purchase, contract, and work pages count only after the public endpoint returns the product receipt or payment label.
Useful engineering evidence, but not a live product claim until runtime receipts exist.
Awaiting public data
Where To Go Next
Each page owns a narrower job. Use product pages first, then inspect receipts, reserve labels, proof categories, or raw JSON when needed.
What This Page Does Not Do
It does not ask for seed phrases, sell a reward path, imply allocation, expose private payloads, publish operator routes, or make Infra the authority for another chain's economic meaning.