InfraVerifiable Storage
Wallet, purchase, storage, proof, retrieval, contracts, and status are kept as separate product lanes.
Search by receipt or handle. With neither, browse returns only intentionally public rented objects.
Public rented browse returns public receipts and can be downloaded by anyone after BIGHT payment. Private records require receipt or handle security checks.
Retrieval search ready. Query and download both require quoted BIGHT from the funded Infra payer attached to the request.
Download is not one flat path. Infra shows which gate applies before a user spends BIGHT or waits on restore.
Public payloads can be downloaded by anyone after the required service conditions and BIGHT payment are met.
A handle can pay for access, then waits for the security checks attached to that handle path.
Private retained objects require the upload receipt before metadata or bytes should move.
Expired payload access stops byte serving while receipt metadata and evidence can remain queryable.
Deleted or tombstoned payloads keep terminal evidence without pretending the bytes are still active.
The query rail returns labelled metadata and state. Payload bytes stay on the separate paid download or restore path.
Receipt, object ID, CID, size, class, hash, created time, and public/private labels.
Payment, admission, settlement, provider payout, and receipt references.
Storage proof policy, proof verdict, repair, retrieval, and restore labels.
Active, expired, deleted, tombstoned, payload state, and terminal evidence labels.
Returned as access state only. The query path does not stream payload bytes.
Download is deliberately separate from upload. A retained object can be present while retrieval still has to price, pay, respect admission state, and follow its hot or cold retrieval path.
The request pays the query rail before object metadata is returned.
The returned receipt shows class, size, hash, payment, proof, and admission labels.
The download quote prices read and proof work into BIGHT.
The gateway spends the download charge before serving bytes.
Cold retention opens a restore page with a timer; hot query can serve directly.
Infra serves the retained object only while the product restore window is active.
Loaded from the public intake service. Verification/query payment is separate from byte retrieval.
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
Awaiting live data
Awaiting live data
Awaiting live data
Awaiting live data
Every product click has a visible charge posture before it spends BIGHT.
Awaiting live data
Public rented data is intentionally visible to public browse. Private records need a receipt or handle path, and retrieval still pays the BIGHT download rail.
Awaiting live data
Awaiting live data
Awaiting live data
Awaiting live data
Expiry, deletion, tombstone, evidence retention, and repair suppression stay separated.
Awaiting live data
Stored data moves through explicit service states. Query can show evidence after payload access ends.
Upload quoted or admitted before the runtime makes it active.
Hot query or public rented payload can serve after BIGHT payment and admission.
Cold retention is dormant until a paid restore opens a temporary download window.
Payload access closes while receipt metadata and evidence remain queryable.
Payload bytes end; terminal evidence remains and tombstone suppresses repair/retrieval.
Bad or disputed evidence is recorded without becoming active service.
Each transition names the owner, actor, and receipt boundary instead of relying on operator memory.
Public intake admits work, storage runtime serves it, proof/challenge lanes judge it, lifecycle closes it.
Uploader, gateway, provider, proof worker, challenge actor, retention policy, or operator.
Admission, retrieval, proof verdict, provider payout, expiry, deletion, tombstone, refusal, or challenge.
Old receipts reconstruct metadata and evidence after payload access ends; query never revives deleted bytes.
Expired, deleted, and tombstoned records move to terminal evidence counts, not active stored payload.