Who does what on Infra.

Submit records, anchors, schemas, proof requests, retention contracts, or query-relevant state.

Store and serve retained data under value-indexed capacity, proof, repair, and settlement rules.

Maintain module state and expose the bounded keeper surfaces other modules are allowed to consume.

Make declared records searchable and reconstructable without inventing meaning.

Check proof, availability, schema consistency, and challenge outcomes, then emit verdict labels.

Watch liveness, repeated failure, drift, and challenge posture without becoming a private enforcement shortcut.

Serve metadata, lookup, reissue, reconstruction, retention proof, linkage proof, challenge, renewal, and bulk/API access as BIGHT-paid memory work.

Roles can prove or serve Infra work; they do not become Core, Bridge, Liquid, or RPC authority.

Published only when the public role feed names it.

Published only when the public role feed names it.

Published only when the public role feed names it.

Public addresses are labels, not credentials or private topology.

Provider capacity is value-indexed and bond-density bounded

Use status or data routes for current provider labels.

Use status or data routes for current counts.

Use status or data routes for current counts.

Provider admission is policy-gated, not a node-earning promise.

Use status or failure labels for current state.

Refusal is normal when proof, payment, capacity, or policy gates are not met.

Certified throughput cannot be split across thinly bonded identities just to lift rewards.

Retrieval, possession, repair, and settlement outcomes control service posture.

Geography or network diversity can inform placement after policy gates; it does not directly mint capacity, rewards, or stake discounts.

Published only through bounded public role feeds. No private topology or credentials are exposed here.

They reflect declared schema-bound meaning. They do not reinterpret claims.

They report validity or failure labels. Consequences belong to downstream rules.

They expose public metadata and proof posture. They do not expose private payloads or destination-chain consequences by default.

BIGHT is Infra work metering. It is not admitted reserve value or its own backing.

Public copy must not frame circular work, self-query loops, or unpaid activity as real yield.

Cross-chain handling cannot become hidden custody, pricing, storage policy, or treasury authority.

Provider payouts come from service work settlement, not from invented activity or reserve principal.