Q token mark QUADPublic Accountability

Infra product path

Store, Prove, Retrieve, Remember

Infra is the work-and-memory surface. BIGHT pays for bounded work; receipts prove what Infra accepted, refused, stored, served, reconstructed, or closed.

The Fast Answer

Infra turns useful work into receipted memory.

The public loop is simple: get a quote, pay in BIGHT where the lane is open, submit the work, keep the receipt, verify the receipt, then retrieve, restore, reissue, or challenge by evidence when needed.

Current Product Path

Use the Infra-owned route for current state. The main domain explains how to read it.

1. Open InfraStart at the product surface for wallet, funding, upload, verify, retrieve, proof, ledger, balances, and public data routes. 2. Fund BIGHTUse quote-first funding where open. Deposit instructions stay unpublished until the Infra-owned custody lane is configured. 3. Upload workSubmit a bounded object, choose visibility, receive a quote, and keep the resulting receipt. 4. Verify receiptCheck object id, hash, class, admission, proof, payment, retrieval, and refusal labels. 5. Retrieve or restoreUse receipt, handle, or public browse rules to retrieve hot data or request a cold restore window. 6. Read pricingUnderstand USD-equivalent target values, quote-time BIGHT conversion, tiers, and what a quote controls.

What BIGHT Does

BIGHT is the work-payment unit for Infra service lanes. It is not a reserve story.

Work payment

BIGHT pays for upload, query, retrieval, proof, reissue, reconstruction, retention proof, contract work, and related service lanes where open.

Quote-time conversion

Infra can quote the target work value first, then settle the accepted work in BIGHT at the quote-time value.

Receipt closure

A BIGHT-paid service should end in a receipt, refusal, expiry, restore window, proof record, settlement record, or other terminal label.

No reserve collateral

BIGHT is not hard reserve backing, admitted reserve collateral, a fixed redemption claim, or a price-support promise.

Core Product Lanes

Storage is one lane. Infra is broader: memory, proof, query, repair, contracts, and settlement evidence all matter.

LaneWhat the reader can expectWhat it cannot prove
UploadQuote, object id, storage class, visibility posture, payment label, proof class, and receipt.Payload truth, permanent storage guarantee, Core admission, endorsement, or public ownership.
VerifyReceipt lookup by receipt or handle with hash, class, admission, proof, payment, and retrieval labels.Universal truth, legal endorsement, or another chain's settlement.
RetrieveHot retrieval, public-rented browse, private handle checks, cold restore request, restore timer, and temporary access window.Public access to private payloads or ownership transfer.
Contract storageContract account, invoice recipient, service tier, prepaid period, query labels, and receipt output.Private contract terms, host identity, or custody outside the contract lane.
Contract workOpt-in packet envelopes for accepted review work with commitments and source proof metadata.Automatic enforcement, punishment, or host-chain authority.
Provider evidenceCapacity, admitted work, escrow, settlement, dispute, withholding, repair reimbursement, and payout receipts where public.Node earning, raw compute rewards, guaranteed payout, or DePIN identity.
Receipt memoryOriginal receipt with work; later lookup, certified reissue, reconstruction, retention proof, linkage proof, challenge history, and bulk/API access where open.Receipt-as-truth, Core value, Bridge finality, Liquid settlement, or payload truth.

Public And Private Payload Boundary

Infra can publish proof metadata without dumping private content into public pages.

Public metadata

Receipt id, object id, hash, tier, proof class, visibility posture, payment state, retrieval state, and refusal state can be public when safe.

Private payload

Payload body, private contract terms, handles, access material, payment data, operator procedure, and sensitive verifier detail stay out of public pages.

Public-rented lane

Records explicitly marked for public browse can be listed or retrieved under the route rules and payment labels for that lane.

Handle-bound lane

Private records require receipt, handle, contract, or owner-bound checks. A public receipt does not make the payload public.

Evidence Classes

Infra uses evidence class labels so product claims do not outrun proof.

Static surface

A page or endpoint contract exists, but current work still needs route evidence.

Local proof

A repo or local chain path proves shape, but the public subdomain may not yet own the current state.

Live chain

The Infra chain or public route can show current state for the named lane.

Public intake

The public product service can quote, accept, refuse, or return visible receipt labels.

Cross-chain acknowledgement

External movement or memory needs real packet, receipt, acknowledgement, ingress, and route proof before stronger claims.

Terminal receipt

A lane is closed by a receipt, refusal, expiry, settlement, restore completion, dispute result, or other end state.

Infra Is Not

These labels keep the product readable without pitching the wrong thing.

Not raw compute rewardsBIGHT pays for accepted Infra work; it is not a GPU/CPU-cycle reward campaign.
Not node earningProvider settlement evidence is not an invitation to run nodes for guaranteed tokens.
Not a storage guaranteeReceipts, proof, restore windows, and refusal labels describe service state; they do not promise permanent availability.
Not payload truthStoring or proving a hash does not make the content true, lawful, endorsed, or admitted by another surface.
Not Core valueInfra receipts do not force QUAD Core admission, Bridge finality, or Liquid settlement.
Not reserve backingBIGHT product payments are separate from hard-collateral reserve rails.