Vote on Tau

On the real testnet IDNI’s tau-testnet command line

Run your own node about 1.5 h · about €6 a month

Votes enter the testnet through a node; no public node takes them (ours only reads). The Tau HUD kit runs one with the network’s settings, open admission included.
Open the command line on the server · 10 s

tau becomes short for IDNI’s tau-testnet command line inside your node. Keys are kept in the node’s data volume.
```
cd /opt/tau-node-kit/kit
alias tau='docker compose exec -T -e HOME=/data tau-node python -m tau_testnet_cli'
tau status
```
Make your key your address and your voice

It prints your public key, your address and the name your vote carries. Back up the private key: tau keys show me --private.
```
tau keys save --name me
```

Vote yes one command per proposal

Each open rule change with its command ready. There is no “no”: a change nobody agrees to expires.
Propose a change advanced · public for good

A ready proposal, then your vote on it. With one validator, one yes agrees it for everyone.

Same rules (no change) Base fee AGRS
```
Waiting for the rules in force…
```

Your public key (from step 3)

Paste it and this page shows when your vote waits in the queue, when a block counts it and what it changed.

Any account may vote. The testnet runs with open admission: a yes from any key counts, not only from validators.
Two thirds decide. A change needs yes votes from two thirds of the number of validators, rounded up.
Free, and once. Proposals and votes pay no fee. The node refuses a second yes from the same key, and any vote for a change that is no longer open.
Never at once. A change takes effect at its activation height, at least as many blocks ahead as there are validators.
Think before you propose. IDNI warns that a bad rule change can halt the testnet until it is corrected. Test rule text in the Playground first.
Prefer a browser? IDNI’s web wallet has a Gov: Vote tab.