BIGHT token markInfraVerifiable Storage

What is ready, what is gated.

Separate live observation from production claims, identify the evidence still needed, and keep public labels below the receipts actually captured.

Current statusProof categoriesPublic dataMain readiness
Choose the next Infra action.

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

WalletBuy BIGHTUploadVerifyRetrieveContractsReceiptsProof

Current public update

Infra has a separate public surface. Live chain status, production service readiness, and cross-chain evidence are labelled separately here.

Memory lane

Awaiting live data

Proof lane

Awaiting live data

Observation

Awaiting live data

Product surface

Awaiting live data

Tester next step

Awaiting live data

IBC and ICA state

Awaiting live data

Pricing authority

Awaiting live data

Receipt entitlement

Awaiting live data

Public metadata

Awaiting live data

Paid memory services

Awaiting live data

Hot/cold split

Awaiting live data

Authority split

Awaiting live data

OSMO ingress

Awaiting live data

Reserve intent

Awaiting live data

QUAD mint state

Awaiting live data

What is visible

Public labels for witness, memory, storage, receipts, queries, exports, role states, and generated aggregate counts.

What is pending

Production status, live Hermes proof, live QUAD invoice acknowledgement, provider onboarding, and any public value-bearing claims.

What to inspect

Open Upload for a priced BIGHT spend, Download for receipt query/retrieval, Balances for service rails, and Data for public data files.

Repo-matched gates

The site now mirrors the local repo's current boundary: product surfaces are mapped, public intake is testable, and IBC/ICA still need live relayer proof.

Runtime

Awaiting live data

Product surfaces

Awaiting live data

QUAD mint state

Awaiting live data

Evidence-class gate

Whole-product claims stay blocked until money-bearing and cross-chain lanes carry live receipt or acknowledgement proof.

Evidence class

Awaiting live data

Whole-product evidence

Awaiting live data

Evidence lanes

Awaiting live data

Current lane evidence

Awaiting live data

Interop fallback gate

Bridgechain remains the preferred movement route. Direct fallback and Osmosis ingress stay labelled as local proof until real packet acknowledgements exist.

Interop fallback

Awaiting live data

Live fallback packet

Awaiting live data

Fallback refusal

Awaiting live data

Osmosis live asset

Awaiting live data

Reserve intent

Awaiting live data

Awaiting live data

Cross-chain memory gate

Bridge and Liquid exports, feeder witness memory, CoreImport boundaries, and delayed NAV-low facts are shown as evidence-only memory unless live packet proof says otherwise.

Cross-chain memory

Awaiting live data

Memory dashboard

Awaiting live data

Awaiting live data

Work verification court

Paid work, verdicts, settlement, disputes, timeout recovery, quarantine closure, and bad-actor memory are shown as receipt-backed product facts, not private job output.

Work court

Awaiting live data

Awaiting live data

Governance and payments

Machine-first governance, Foundation budget funding, and External Affairs execution stay separated so invoices can be paid without giving any one rail reserve, mint, seller, or sink authority.

Governance and payments

Awaiting live data

Awaiting live data

Testing criteria

Infra readiness is about memory and proof behavior, not QUAD block production.

  • Public labels remain explicit. Staged, testing, live, stale, unavailable, and not-live states are named plainly.
  • Exporter path is bounded public. Generated data does not expose private thresholds, operator procedure, credentials, or exploit-sensitive timing.
  • Role boundaries stay readable. Writers, Keepers, Indexers, and Verifiers are explained without turning the page into a private manual.
  • Product receipt path is testable. A tester can upload, keep the returned receipt, query metadata, inspect BIGHT charges, and request retrieval without reading server logs.
  • Receipt metadata is bounded public. Receipt ID, source, class, height or epoch, root or hash, retention, proof, challenge, expiry, and disclosure posture can be public while payload bodies stay redacted by default.
  • Later proof is priced memory work. Lookup, detailed retrieval, certified reissue, evidence reconstruction, retention proof, host-chain linkage proof, challenge work, renewal, and bulk/API access are BIGHT-paid Infra services.
  • Pricing lanes stay separate. Hot-query reads and cold-retention storage can share worldview inputs without cross-authorizing claims.
  • Reserve boundaries stay explicit. Product BIGHT is work metering; reserve support is hard-collateral state and does not unwind principal by default.
  • Cross-chain meaning stays separate. Infra records and proves claims; it does not become Core truth, Bridge admission, or Liquid settlement.
  • No entitlement framing appears. Participation, uploads, proofs, and operator receipts do not create reward eligibility or future claims unless a named on-chain rule says so.

Host path

Public chain services, RPC, indexers, and Infra daemons require their own host class. Static website hosting stays separate.

Testing host

Awaiting live data

Public candidate

Awaiting live data

Website boundary

Awaiting live data

Yellow flags this surface rejects

Public-affairs guardrails for Infra testing.

  • No node setup to earn tokens.
  • No payment claims outside named product invoices and receipts.
  • No seed phrase, private key, or recovery phrase entry.
  • No DePIN, AI, raw compute reward, GPU reward, mining, airdrop, or allocation framing.
  • No audit, safety, reserve-yield, provider-payout, settlement, or cross-chain claim unless public evidence exists.
  • No claim that receipt metadata exposes private payloads or downstream chain meaning.
  • No claim that raw OSMO/uOSMO is spendable fallback collateral without accepted Infra ingress evidence.