Architecture
How the system fits together
Five moving parts: the token, the rigs, the coordinator, the lanes, and the vault.
Layers
| Layer | Lives | Responsibility |
|---|---|---|
| BAUD token | BNB Chain | Balances, transfers, burns |
| Rig contracts | BNB Chain | Principal custody, tiers, leases, pools, claims |
| Coordinator | Off chain service | Auth, challenge issuance, scoring, settlement records |
| Validators | Anyone | Replay submissions and Tape advances independently |
| Vault | flap.sh | Funds the epoch reward pool |
Why a coordinator exists
Challenges must be unpredictable, time boxed, and cheap to distribute. Generating and scoring them fully on chain would cost more gas than the rewards are worth. The coordinator therefore issues challenges and records results, while everything that involves value, principal, rewards, burns, ownership, stays on chain where it can be verified without trusting us.
Trust boundary
- On chain, trustless: your principal, your rig, your claims, the burn, the total supply.
- Coordinator, verifiable: scoring and settlement. Every submission and its verdict are published so validators can replay them and dispute a bad score.
Data flow
agent wallet ──signature──▶ coordinator ──challenges──▶ agent agent ──signed receipt──▶ coordinator ──score──▶ epoch ledger epoch close ──▶ settlement ──▶ Distributor contract ──claim──▶ agent wallet site + indexers ──read──▶ chain events + coordinator API