InfraVerifiable Storage
Capacity, proof, retrieval, repair, and payout claims stay separate until the relevant receipt exists.
Public provider labels are metadata. They do not publish keys, private topology, or hidden thresholds.
Awaiting live data
Awaiting live data
Awaiting live data
Awaiting live data
Awaiting live data
Awaiting live data
A provider should be able to prove more than disk space. Infra cares about retrieval, proof response, repair participation, and clean settlement records.
Prepare a public Infra provider address, payout address, optional handle, and an operator identity that can survive key rotation without hiding prior failures.
Declare usable storage, reserved repair headroom, storage class, retrieval posture, and supported proof classes without overclaiming sellable capacity.
Be ready for retrieval challenge, Merkle possession checks, proof-of-storage posture, and dispute or appeal receipts.
Be able to serve random chunks, handle hot-query work, support cold-retention restore windows, and participate in repair around failed replicas.
Understand that accepted work, withheld work, disputed work, slashed work, and paid work are separate provider receipt states.
Do not publish seed phrases, private keys, hidden network topology, private thresholds, or operator-only procedures in an onboarding request.
The public shape is deliberately slower than a simple registration form. Good acting should be cheap and legible; bad acting should get more expensive as it touches proof, repair, and settlement.
Submit public provider identity, capacity, storage class, proof support, and payout metadata.
Enter shadow observation before high-value work or payout eligibility is treated as live.
Pass retrieval and possession checks, then receive only the work class your proof posture supports.
Earn only from admitted work that produces settlement receipts or explicit withheld/dispute labels.
These maps are generated public labels. They are useful for orientation, not private admission policy.
Awaiting public provider labels
Awaiting public settlement labels
Awaiting public payout labels
Payment follows service receipts. It does not follow marketing language, raw capacity claims, or circular demand.
Accepted storage work after quote, payment, admission, and provider assignment labels exist.
Hot reads, public-rented downloads, private receipt downloads, and cold restore work after BIGHT payment and access checks.
Valid proof or challenge response where the receipt names what was checked without exposing private chunks.
Repair or handoff participation after failed, dirty, or unavailable replicas are routed through the repair path.
Disputed, stale, missing-proof, or failed-retrieval work stays withheld until the terminal receipt decides it.
A running node, raw zone label, or idle disk promise does not create BIGHT entitlement by itself.
Machine-run role addresses may be public. Credentials and private operator procedure are not.
Awaiting public machine role labels