BIGHT token markInfraVerifiable Storage

Verification

Check the receipt before the file.

Paste a receipt or object reference to inspect public evidence, payment posture, hash metadata, and retrieval state before download, reissue, reconstruction, or challenge work.

Verify ReceiptUpload DataRetrieve DataReceipt Activity
Choose the next Infra action.

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

WalletFund BIGHTUploadVerifyRetrieveContractsReceiptsProof

Verify a receipt

Receipt lookup pays the query rail and returns public record metadata. Blank browse is intentionally narrow and only returns PUBLIC_RENTED objects.

Receipt verification ready. Connect or fund an Infra BIGHT address, then paste a receipt ID or load the last upload receipt from this browser.

What verification checks

Infra makes storage auditable by attaching receipt evidence to retained records before bytes move.

IdentityReceipt ID and handle

The record can be found without exposing private browse by default.

IntegritySHA-256 and size

The returned metadata binds the object to its content hash and byte count.

RetentionStorage class

HOT_QUERY, COLD_RETENTION, PUBLIC_RENTED, or contract-bound policy intent.

AdmissionChain status

The lookup shows whether payment, admission, and lifecycle labels are present.

ProofProof lane

Public labels show the proof and retrieval posture without exposing private verifier procedure.

Next stepRetrieve or restore

Hot data can stream after payment; cold data may need a paid restore window.

Verification lane stateQuery, proof, receipt, and snapshot labels used by the receipt checker.
Receipt lane

checking

Query payment

checking

Query charge

checking

Proof policy

checking

Snapshot

checking

Live refresh

checking

Public boundaryReceipt lookup proves records without turning Infra into an accidental public data dump.
Public browse

Only PUBLIC_RENTED objects should appear without a receipt or handle.

Private records

Private records stay receipt or handle gated and may require security checks before retrieval.

Protocol records

Core exports, work receipts, custody records, and evidence packets should be queryable by proof path, not casually feed-browsed.

Receipt boundary

Verification labels prove recorded state only; they do not create rewards, ownership, or claims outside the receipt and chain evidence.