Write a rule. See what the testnet would say.
The checks below are the ones the Tau Testnet Alpha runs before it lets a personal rule in. Nothing you do here is sent to the chain.
Not checked yet.
Your rule never enters the chain as you wrote it. The node wraps it in a guard on your address, so it can only ever decide your own transfers. Everyone else falls through to “allow”.
| From | Amount | To | Time | Result |
|---|
Results come from an in-browser preview of the rule. When the Tau engine on the community node is reachable, “Check rule” also runs every transfer through it and its answer replaces the preview.
Rules that bind everyone, like the base fee, change only when enough validators agree. Here you hold one of four seats. Pick a change or write your own, then vote.
a1fe40…7d2b, most likely run by IDNI), so the quorum is 1. The network also runs with open governance admission: a proposal or a vote from any key counts, so a single yes vote schedules a change. Here the seat is simulated and only validators vote, which is the code’s default. Counting, quorum and the delay before a change takes effect work as on the real node.How the real node does it: governance.py ↗ · quorum ⌈2N/3⌉ of the current validator set, one vote per validator, activation at a later height.
Checks ported from IDNI/tau-testnet @ 539d1e2: rule_offers.py, admission.py, approvals.py. Unofficial community page, not affiliated with IDNI. ·