Overview
What a Pareton validator does on subnet 10, and the two ways to run one.
A Pareton validator sets weights on Bittensor subnet 10. Emission follows the seated leader of each open campaign and decays while that leader holds the crown. Everything not paid to a leader is burned. For how the split is defined, see Validators and emissions.
There are two ways to run.
1. Use our API
Download auditor.py and sign what GET /v1/weights publishes. No database,
no GPUs, no pipeline. One process, one wallet.
You are trusting Pareton's arithmetic. Every input behind it is public, so you can spot-check it whenever you want.
Go to Set weights from our API.
2. Run your own stack
Rent a VPS, point it at your own Postgres, and run three services. Your host watches the chain for miner submissions, benches them on GPUs it rents per job, crowns leaders from its own results, and computes and signs the vector from that. Nothing about your vector depends on us.
This costs money to run: GPU rental per submission and a VPS that stays up.
Go to Run your own validator.
What both paths need
- A Bittensor wallet whose hotkey is registered on subnet 10 (finney).
- A validator permit on that hotkey. Permits go to the top stake holders, so
you need enough stake to hold one. Without a permit,
set_weightsfails as an opaque substrate error. - Python 3.10 or later and
bittensor11.x. version_keyset to2032. Validators trust-weight each other only while their keys agree, so this is a coordinated value, never one you pick. Read the current key fromGET /v1/weights.
Cadence
Set every 360 blocks, about 72 minutes. Blocks are the clock, not wall time: the decay curve is measured in blocks, and blocks are the only clock every validator shares.
