QUAD Infra Surface

Infra Snapshot

Broad public labels first. The Infra-specific folder owns the deeper readiness surface.

SurfaceInfra

Current labelInfra canonical app and CometBFT are live; public intake, receiver, export, and relayer services are active

Public accessBIGHT wallet support, quote-first purchase, upload, verify, retrieve, balances, ledger, and proof labels

Product stateOwner route reports upload, query, download, and paid-product ledger flow; BIGHT purchase is quote-first and receipt-backed

Runtime evidencePublic snapshot on 2026-06-14 showed chain height, product-surface state, paid upload/download ledger labels, and settled provider payout posture

Receiver evidenceCore-export receiver receipts, external-chain receiver receipts, and sent oracle/outbox records are present on the Infra box

How To Read This Page

Infra owns useful-work evidence. It can prove service events without becoming Core value or another chain's authority.

Purpose

BIGHT-funded storage, upload, retrieval, receipt verification, retained memory, proof labels, balances, and ledger state.

Posture

Live product hardening is active with canonical app, CometBFT, public intake, external export receiver, Bridge export adapter, relayers, BIGHT purchase, paid upload, paid retrieval, receipt lookup, provider settlement labels, and proof routes running. Payment remains quote-first and proof-required.

Public stats

Use infra.uquad.org for product state, balances, ledger, receipt lookup, proof, upload, retrieve, and endpoint contracts.

Not inherited

An Infra receipt proves bounded Infra work. It does not force Core admission, Bridge finality, Liquid settlement, or payload truth.

Infra Experience Contract

Infra should feel like paid, provable memory: quote the work, perform or refuse it, then leave a receipt.

Infra should feel simple at the front: buy BIGHT, submit work, get a receipt, verify later. The full label contract remains available for reviewers and operators.

Open the Infra service-label map

PathWhat Infra should showWhat it must not imply

Metadata-light uploadWhether the uploader chose reduced public metadata, public browse visibility, receipt-only visibility, handle-only access, or contract-bound access.Reduced metadata does not make the entire service anonymous or exempt from receipt, proof, retention, refusal, or lawful owner-touch rules.

UploadObject id, tier, quoted BIGHT, accepted price, retention window, proof class, visibility posture, receipt id, and refusal/expiry state.Accepted upload is not Core admission, permanent storage, endorsement, or proof of payload truth.

RetrieveAccess state, required fee, retrieval proof, expiry, payload-access-ended state, and receipt or handle used.Retrieval does not prove payload truth, ownership, public browse permission, or another chain's meaning.

Contract pathContract account, capacity, service class, hot/cold posture, query state, lifecycle policy, owner-touch rule, and receipt output.Contract storage is not the same lane as public upload, and it does not publish private contract terms.

Receipt memoryOriginal receipt included with accepted work; lookup, certified reissue, evidence-bundle reconstruction, retention proof, linkage proof, challenge history, and bulk/API access priced separately where open.A receipt is service evidence, not universal truth, Core value, Bridge finality, or Liquid settlement.

Provider journeyRegistration posture, work admitted, escrow, payout, dispute, slash/refusal, appeal, and settlement receipt where provider lanes are public.Provider work is not node earning, raw compute reward, DePIN identity, or guaranteed payout.

ChallengeEvidence, challenge id, response window, accepted response, result, appeal path, and terminal state.Challenge labels should not expose private verifier logic or turn accusation into proof.

RepairWhat was repaired, what proof was generated, what remained unverifiable, and which receipt closes the repair.Repair evidence does not prove the original payload was true, lawful, endorsed, or admitted by another surface.

Cross-surface meaningInfra may store, prove, retain, link, or reissue evidence for another surface.Infra does not admit Core value, force Bridge delivery, settle Liquid balances, or certify payload truth by storing a record.

This is the main-domain reading contract. Current service state belongs on Infra-owned routes such as upload, verify, retrieve, balances, and proof.

What It Is

Infra is the verifiable-storage and memory surface. It lets a user buy BIGHT, upload work, receive a receipt, verify that receipt, and retrieve the result.

The product loop is simple: buy BIGHT, upload, pay the quoted BIGHT, keep the receipt, verify it, then download or restore by receipt when needed.

Infra product Infra path Buy BIGHT Upload Verify receipt Balances

Why Use It

Use Infra when the question is whether a record can be stored, priced, receipted, verified, retrieved, and explained through public evidence labels without exposing private mechanics.

Buy BIGHT Infra path Upload work Verify receipt

BIGHT Purchase Rail

Infra exposes BIGHT buying as a quote-first purchase path with payment proof, recipient, and receipt gates.

Buying BIGHT is treated as a work-payment path, not an investment, allocation, or reward page. The owner route quotes first, gives the payment instruction, waits for accepted source payment evidence, and credits BIGHT only after receipt checks.

Buy BIGHT Endpoint contract

Open purchase gates

Quote first

The public route returns requested BIGHT, required value, source denom, accepted source labels, payment reference, relayer intake details, and the next action.

Proof required

BIGHT is credited only after outside value, recipient, source payment proof, value fact, and final accepted receipt are present.

Payment-proof gate

Unquoted, unmatched, expired, quarantined, or unbound payments do not become automatic BIGHT credits. They remain pending, refused, returned, or review-bound until the owner route closes them.

No entitlement

Buying BIGHT pays for Infra work. It is not a sale claim, allocation, reward, governance right, fixed redemption value, or reserve backing by itself.

Where It Lives

Infra details stay outcome-level on the main site. Upload, receipt verification, retrieval, BIGHT work-payment, reserve rail, readiness labels, and public evidence live on the Infra subdomain.

That keeps Infra proof separate from QUAD Core block telemetry.

Receipt Memory

Infra treats receipts as useful service evidence, not as universal truth or Core admission.

The first receipt belongs with the accepted work. Later lookup, reissue, reconstruction, retention proof, and bulk access are BIGHT-paid memory services when the lane is open.

Ledger Verify receipt Retrieve Pricing guide

Open receipt-memory detail

Included with work

The original receipt belongs with the accepted work so a tester can verify what was requested, stored, served, or returned.

Paid later memory

Later lookup, certified reissue, evidence-bundle reconstruction, retention proof, host-chain linkage proof, challenge history, and bulk/API access are BIGHT-paid Infra services.

Public metadata

Public receipt metadata can be queryable when safe. Payload body, private contract terms, operator procedure, and sensitive verifier detail stay out of the public page.

Hot and cold lanes

Fast query lanes are for low-latency reads. Retention lanes preserve evidence for later restore, proof, or challenge work when paid and allowed.

Docs And Product Boundary

Infra is being kept readable as a product, not exposed as an operations manual.

Infra can explain archive, query, retention, receipt economy, work payment, reserve posture, and evidence service without publishing operator procedure or private verifier detail.

Open product-boundary detail

Provable memory

Infra now frames storage as one lane inside a broader provable-memory surface: archive, query, retention, receipt economy, work payment, reserve posture, and evidence service.

BIGHT role

BIGHT meters Infra work, service settlement, and memory-economy pressure. It is not admitted reserve value or its own backing merely because Infra uses it for work.

Economic integrity

Infra public copy should not turn fake demand, circular reward loops, or inflation pretending to be revenue into product claims.

Docs spine

The current docs-meta index groups doctrine, checklists, authority maps, references, inventories, generated evidence, and archive material so public copy can stay outcome-level.

Authority lanes

CoreImport, Interop, DA, Fee invoices, Foundation, External Affairs, Mint, Reserve, Seller, Archive, Query, Provider, and Audit remain separate authority lanes.

Public limit

The public site may explain product boundaries and evidence classes. Runtime wiring, fund movement, keeper authority, punishment logic, credentials, and SDK app readiness stay private until safe.

Current Local Evidence

These are public local proof surfaces from the Infra folder. They may appear on the subdomain after export, not before.

Current Infra evidence covers product gates, quote-first BIGHT purchase, paid upload/download ledger labels, provider payout settlement posture, public intake, contract-work loops, Core-export receiver receipts, external-chain receiver receipts, and sent oracle/outbox records. Stronger public claims wait for the owning subdomain to export the relevant proof.

Those receipts remain Infra evidence without becoming Core truth.

Open local evidence classes

Whole-product gate

Infra classifies memory, verification, query, repair, storage, paid BIGHT minting, reserve defense, work services, pricing, ledger, and cross-chain lanes by evidence class.

Money and cross-chain blocker

The local gate intentionally blocks whole-product or freeze claims until money-bearing and cross-chain lanes carry enough live proof.

BIGHT purchase gateway

The BIGHT purchase path is quote-first and owner-routed. It requires recipient, exact source payment, payment reference, source proof, reserve admission, and a credit or return receipt.

Reserve yield receipts

Local reserve evidence covers yield ingress and Bridge-bound remittance acknowledgement receipts for the approved yield-bearing paths before any reserve-productivity claim.

Public intake tests

Local evidence covers upload, download, query, pricing, public-rented reads, private-handle safety, cold restore windows, and evidence-source labels.

Contract-work loop

Contract work is treated as paid intake, assignment, proof, verdict, settlement, dispute, slash or claim path, appeal, terminal receipt, and privacy-safe query metadata.

Box-side receiver feeds

The live Infra box carries hundreds of Core-export receiver receipts, external-chain receiver receipts, and sent oracle/outbox records. These prove receiver and handoff activity, not Core admission or reward eligibility.

Public Reference Boundaries

Infra separates normal product-contract receipt language from opt-in hook packet language without publishing private repository, operator, or verifier details.

Normal contracts

Public product-contract vocabulary for archive anchors, retention proof records, query delivery receipts, and availability proof records.

Hook packets

Public packet envelopes for opt-in contract-work review where host chains apply their own local policy.

What this proves publicly

The receipt and packet boundaries can be reviewed without turning the website into private Infra documentation.

What stays excluded

Private verifier logic, chain internals, operator procedure, production deployment detail, and provider backend internals stay out of public bundles.

Verification guide Pricing guide

Work Pricing

Infra displays bounded work pricing as USD-equivalent target value first, with BIGHT converted at accepted quote-time value.

Pricing rule

BIGHT due equals the USD-equivalent work target divided by the accepted BIGHT value at quote time.

Storage Liters

Class A, B, and C examples show active, standard, and archive storage as usage units rather than yield or reserve assets.

Public boundary

The guide is a pricing explainer and reference input, not an allocation path, fixed redemption value, yield claim, or reward claim.

Pricing guide

What To Check

Infra is public when its outcome labels are readable, not when private mechanics are exposed.

Check witness freshness, storage labels, receipt lookup, BIGHT work intake, reserve separation, and effective capacity posture.

Open Infra checklist

Witness

Whether public witness state is available and fresh enough to inspect.

Storage and memory

Whether retained-state, upload, verification, and retrieval labels are staged, testing, live, or unavailable.

Receipts and queries

Whether public receipt verification, lookup, reissue, reconstruction, retention proof, and query labels exist without private procedure.

BIGHT work intake

Whether wallet support, quote-first purchase, upload work, query/download work, balances, and ledger labels are public enough to inspect without implying rewards, custody, or fixed-value redemption.

Reserve boundary

Whether hard collateral is shown separately from BIGHT work payments, including PAX/UPAX as low-liquidity reserve ballast rather than normal spend liquidity.

Capacity posture

Whether effective capacity is publishable: admitted capacity less committed or replica-reserved storage, not private module internals.

Host Path

Public hosting posture only. No ports, credentials, private routes, or operator procedure are published here.

Dedicated host

Infra uses dedicated chain-service hosting so behavior, logs, readiness, and load shape can be checked without exposing private operator procedure.

Public candidate

Public chain services, RPC, indexers, and Infra daemons require dedicated server-class hosting, not shared static web hosting.

Separated surfaces

The static website can remain separate while chain services and public status feeds run on their own host class.

If Infra Is Unavailable

The main site keeps Infra's role and public boundary readable when the Infra subdomain, upload path, receipt path, or BIGHT service is stale or offline.

Still shown

Infra purpose, pricing guide, receipt-memory boundary, public scope, and verification links.

Downgraded

Upload, verify, retrieve, contract storage, balances, BIGHT purchase, provider settlement, and current receipt lookup.

Not inferred

Infra outage does not imply Core admission, Bridge failure, Liquid settlement failure, data loss, or live provider-payment state.

Next check

Use Status, Verify, and the Infra subdomain once it is reachable again.

Public scope

Shows storage health and effective capacity summaries.
Shows receipt verification, query, reissue, reconstruction, retention proof, linkage proof, and challenge-history availability summaries.
Shows retained-memory posture, evidence classes, and refusal reasons in plain labels.
Links to BIGHT wallet support, quote-first purchase, upload, verify, download/retrieve, contract work, balances, ledger, and public data routes for live product intake.
Separates BIGHT product payments from hard-collateral reserve rails, including PAX/UPAX as ballast.
Links to the Infra surface for active public status.

Public boundary

Private verification timing.
Internal evaluation settings.
Operator-sensitive storage procedure.
Mainnet value, reward, allocation, or production payment claims.
Deposit addresses, payment routes, or custody details unless published by the Infra-owned purchase path.
QUAD Core block telemetry as if it were Infra telemetry.
Core truth as if it were local Infra truth.