BIGHT token markInfraVerifiable Storage

Onboarding

Start with the role you actually need.

Infra has different entry paths for people storing data, validators joining consensus, and providers serving query or retrieval work. Each path keeps wallet use, receipts, proof, node operation, and private payloads separated.

Start with walletStore dataProvider guideChain metadata
Pick one path first.

Storage users need BIGHT and receipts. Validators need a node packet. Query providers need role admission, endpoint proof, and settlement receipts.

WalletBuy BIGHTUploadRetrieveProvidersSnapshotsData

Choose a path

The same chain can serve different people, but the evidence needed for each role is not the same.

Storage userUse your storage on Infra.

Fund a BIGHT wallet, upload, keep the receipt, verify, query, retrieve, or open a cold restore window.

Product path ValidatorPrepare a consensus node.

Use public chain metadata now. Independent join requires a posted genesis, binary checksum, peer list, and validator transaction path.

Node path Query providerServe query or retrieval work.

Declare a public role, prove response ability, serve paid requests, and settle only with provider receipts.

Service path

Use storage

This is the normal product path for someone who wants Infra to hold or retrieve data.

1Get BIGHT

Add Infra to Keplr, copy your public address, buy BIGHT through the paid purchase lane, and wait for the credit receipt.

2Upload

Choose retention and service class. Public rented is cold retention. The quote is priced before bytes move.

3Keep receipt

Save the receipt or handle. That is what lets the system verify, query, reissue, retrieve, or restore later.

4Retrieve

Public rented can be downloaded by anyone after payment. Private records need receipt or handle checks before bytes move.

WalletConnect Keplr and copy the public Infra address. Buy BIGHTUse the paid BIGHT purchase lane before product work. VerifyCheck receipt state, hash metadata, proof labels, and access posture. Cold restoreOpen a paid temporary window when cold retention needs to be downloaded.

Run a validator

Public chain metadata is available now. The missing piece for open validator onboarding is the startup packet, not a secret operator tunnel.

Chain

Awaiting live data

RPC

https://infra.uquad.org/rpc

REST

https://infra.uquad.org/rest

gRPC

infra.uquad.org:443

Stake and gas

BIGHT, minimal denom ubight, 6 decimals.

Address prefixes

infra, infravaloper, infravalcons.

Needed before join

Posted genesis file, genesis checksum, binary or build tag, minimum gas guidance, P2P peers or seeds, and validator creation command.

Node steps

Build or install infrad, init a home for chain infra, place the public genesis, configure peers, start sync, then submit validator creation only after the node is caught up.

Security rule

Never paste validator mnemonic, private validator key, node key, or sentry topology into a website or public support channel.

# command shape once the public startup packet is posted
infrad init <moniker> --chain-id infra --home ~/.infra
curl -fsS <posted genesis url> -o ~/.infra/config/genesis.json
sha256sum ~/.infra/config/genesis.json
# configure public peers or seeds from the startup packet
infrad start --home ~/.infra

Serve query or retrieval

Query providers help people inspect or retrieve retained records. They are not allowed to turn private payloads into public data by accident.

Query role

Declare whether you serve metadata query, hot retrieval, cold restore assistance, receipt reissue, or proof-history lookup.

Public endpoint

Publish only the endpoint and role metadata needed to route paid work. Keep private host layout and keys private.

Proof check

Be ready to prove response time, served bytes, receipt binding, and failure handling for the work class you accept.

Payment

Query, retrieval, restore, and receipt reissue work is BIGHT-priced. Provider payout waits for service and settlement receipts.

Privacy

Blank public browse returns public rented only. Private receipt or handle queries return metadata and access state, not payload bodies by default.

Failure

Timeouts, stale endpoints, missing receipts, wrong signer, or proof mismatch should become explicit refusal, dispute, repair, or withholding labels.

Provider journey

Awaiting public provider labels

What this page will not do

Onboarding should reduce friction without pretending away missing evidence.

No seed phrase

The site never needs a seed phrase or private key for wallet, validator, storage, or provider onboarding.

No free product work

Upload, query, retrieval, restore, and receipt services require quoted BIGHT payment or a named accepted service receipt.

No private admission claim

Provider, query, and validator pages explain the route. They do not silently admit providers, create validators, or promise rewards.