BIGHT token markInfraVerifiable Storage

Storage

Upload data. Keep the receipt.

Price the bytes, choose the retention class, spend quoted BIGHT, then keep the receipt that proves the object, charge, class, and later verification path.

Upload DataVerify ReceiptBuy BIGHTStorage Contracts
Choose the next Infra action.

Wallet, purchase, storage, proof, retrieval, contracts, and status are kept as separate product lanes.

WalletBuy BIGHTUploadVerifyRetrieveContractsReceiptsProof

Quote and upload

Uploads are quoted in BIGHT from file size, retention class, and tier. Public browse only shows objects intentionally placed in PUBLIC_RENTED.

Live upload quote

Choose a file to price the BIGHT charge before upload.

Before action chargechoose file
Retentionchoose file
Service tierchoose file
Proof classchoose file
Billable sizechoose file
Value basischoose file
Receipt will proveobject hash, size, charge, class, admission, and proof policy
Privacy posturereceipt-bound by default

The receipt is the product handle: keep it, verify it, and use it before retrieval. Infra never asks for a seed phrase.

Upload lane ready. Buy BIGHT through the purchase gateway, then spend quoted BIGHT here.

Receipt cardProof handle appears here after upload
Quoted before uploadnone
Paid after uploadnone
Upload speednot measured
Receipt IDnone
Object IDnone
CIDnone
Retentionnone
Proof classnone
Receipt provesnone
Privacy posturenone
Payment routepaying wallet required
Admissionnone
Settlementpending
Next actionverify receipt

Retention classes at a glance

These are product labels for choosing the path before the live quote. Actual upload pricing is still returned by the intake service.

HOT_QUERYFast active retrieval

Use for records you expect to query or retrieve often.

Quoted live by size and tier
COLD_RETENTIONLonger-term retained data

Use for records that should persist but may require a paid restore window before bytes stream.

Quoted live by size and tier
PUBLIC_RENTEDIntentional public browse

Use only when the object is meant to be publicly discoverable. Public rented payloads can be downloaded by anyone after required service conditions are met.

Quoted live by size and tier
CONTRACTAccount-bound work

Use a contract ID when storage belongs to an invoice-recipient-backed account.

One-month prepay on contract tests

Live storage classes

Classes loaded from the public intake feed. These are live service labels; receipts remain the authority.

Storage classes

Awaiting live data

Storage path

This is the friendly front door. The chain still decides payment acceptance, admission, retention behavior, proofs, repair, provider settlement, and public evidence labels.

Drop

The browser sends the file to public intake.

Hash

Infra records size and SHA-256 in the manifest.

Quote

Fee math prices bytes and class into BIGHT.

Pay

The gateway spends quoted BIGHT on the product service rail.

Receipt

The receipt records the proof handle, class, payment, hash, and admission trail.

Prove

Later proof lanes can challenge retention and retrieval.

What the upload receipt is for

An upload receipt is the thing to keep. It lets later pages verify, reissue, reconstruct evidence, prove retention, challenge, renew, or retrieve under the service class that was actually accepted.

Public by default

Receipt metadata can show receipt ID, class, hash, size, retention state, proof state, challenge state, expiry posture, and disclosure label.

Private by default

Payload bytes, private terms, sensitive payer metadata, operational detail, and service-private fields stay out unless the source service explicitly marks them public.

Later services

Lookup, detailed retrieval, certified reissue, reconstruction, retention proof, linkage proof, challenge history, renewal, and bulk/API access are BIGHT-paid memory services.

Upload service labelsLive class and pricing authority labels used by the intake surface.
Quote source

Awaiting live data

Proof path

Awaiting live data

Payment rail

Awaiting live data

Contract state

Awaiting live data