Q token markInfraTestnet Surface

Writers / Keepers / Indexers / Verifiers

Public Roles

Infra roles explain who does what at a public level. This is not a provider console, node setup guide, earning path, allocation route, or private operations manual.

Role map

Simple public explanation. The implementation keeps authority narrower than the page needs to describe.

Writers

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

Keepers

Store data and prove retention or availability under declared public labels.

Indexers

Make declared records searchable and reconstructable without inventing meaning.

Verifiers

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

Observed role labels

Generated public states from the current snapshot.

Boundaries

Role clarity is how Infra avoids becoming a generic data platform or another chain's hidden authority.

Indexers mirror

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

Verifiers verdict

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

BIGHT meters work

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

No fake demand

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