Yoalto runs on three private single‑node development clusters. There is no mainnet, no public testnet, no faucet and no block explorer — so rather than showing you a dashboard of numbers we made up, this page says what exists and what has to happen before it does.
This is a diagram of the address space, not a load display. Cell shading is uniform on purpose: there is no network to measure, and varying it would imply per-partition traffic nobody can observe.
Three single‑node Talos Kubernetes clusters, provisioned with OpenTofu and reconciled by Flux. They exist so the team can run the node against real infrastructure rather than a laptop. They are not reachable from the internet and they carry nothing of value.
The repository ships a devnet bootstrap generator that produces the material for a local network, and the e2e suite brings up multi‑validator clusters in‑process against a FoundationDB container. That is currently the realistic way to see Yoalto finalize a block.
| Item | Status | Why it blocks a public network |
|---|---|---|
| Validator registration | Designed | with proof-of-possession, so an address cannot be squatted |
| Rewards and payouts | Designed | fees are burned today; issuance is unset |
| Slash evidence | Designed | the penalty works; nothing raises the evidence |
| Mempool gossip | Designed | validators do not propagate transactions to each other |
| Partition sync coordinator | In progress | late-joiner catch-up across 256 partitions |
| Public RPC and explorer | Designed | nothing is exposed publicly |
No dates are given because none have been set. When a testnet exists it will be announced with the genesis material and the instructions to join it, not with a countdown.