BIGHT token markInfraVerifiable Storage

Cold restore

Open a restore window.

Cold retained data stays dormant until a paid restore path opens a temporary retrieval window backed by receipt state, payment state, and a visible timer.

Start from retrievalVerify receiptReceipts
Choose the next Infra action.

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

WalletFund BIGHTUploadVerifyRetrieveContractsReceiptsProof

Restore window

Loading cold restore state...

Receipt

checking

Handle

checking

Status

checking

Timer

checking

Payment

checking

Charges before action

Cold restore uses the retrieval quote, then waits on the load-aware restore timer before the download window opens.

Charges

checking

Cold restore path

Cold data is not treated as instantly hot. A receipt opens the restore window; the timer, payment state, and lifecycle label decide when download becomes available.

1Start from retrieval.

Bring a receipt or handle to the retrieve page so Infra can decide whether the record is hot, cold, public, or unavailable.

Access path 2Check the receipt.

Verify hash, retention class, payment posture, and proof labels before treating the object as retrievable.

Proof path 3Keep the evidence trail.

Restore and download activity should stay tied to the receipt instead of becoming a silent file link.

Receipt path 4Name failed states.

Expired windows, missing payment, stale records, and unavailable payloads should end in visible labels.

Failure path