A decentralized relic proof network

Forge permanencefrom alpha.

Forge a numbered relic from one finalized alpha burn today. The protocol is being engineered to become a Bittensor subnet where miners serve the index and validators independently prove every result.

Execution
Native SS58
Settlement
Finalized blocks
Contracts
No EVM
Founding RelicFinalized proof
ShizzySN1 / #0001
TAO committed1 test TAO
Alpha relinquished1,035.580333 α

Finalized at block 7,698,721 · extrinsic 6.

Verify the evidence

The Forge

See exactly what the mint will burn.

The Forge re-quotes at the current block, checks the subnet generation and balance, then shows every limit before the wallet can sign.

01Connect TAOStats Wallet

Your wallet signs. The site never sees your private key.

02Use test TAO

Live testnet TAO is available by request; never send mainnet funds.

Network details →
03Create the artifact

Your image is compressed locally, then its exact bytes enter the finalized transaction.

01Select a subnet
Alpha economy
Reading alpha economies…Search by subnet name or number
Subnet generation--
Canonical identity--
02Choose a burn amount
03Write the relic
On-chain imageStored inside the finalized transaction
04Connect the signer

One signature, three facts

The chain proves the sacrifice.

Bittensor Relics never pretends metadata lives inside a fungible alpha token. The artifact is derived from public, reproducible chain evidence.

01 / Buy

TAO enters the selected pool.

The native runtime swaps the committed TAO for that subnet's alpha.

02 / Burn

The acquired alpha is relinquished.

A finalized AlphaBurned event records the exact amount, subnet, and signer. The present runtime operation is supply-neutral.

03 / Inscribe

The Relic is permanently identified.

The matching remark and burn share one atomic transaction and one canonical number.

Native call pathbatchAll[ addStakeBurn, remarkWithEvent ]No EVM. No custody. Finalized testnet only.
Relics proof network

Proof-serving, not database trust.

Relics can work before its own subnet. The current research network demonstrates deterministic three-miner challenges where the dapp requires matching checkpoint proofs.

Open the proof network ->

  1. MinersIndex burns, images, numbering, transfers, and ownership.
  2. ValidatorsChallenge random chain positions and score exact correctness.
  3. DappAccepts threshold agreement instead of trusting one server.