Yoalto executes native payments across 255 parallel partitions, each with its own accounts and its own block stream, coordinated by a single validator set. Payments need no cross‑partition coordination at all — and a validator is a pod cluster over shared FoundationDB, so throughput grows by adding pods rather than by buying a bigger machine.
Every account has a deterministic home partition, derived by hashing its identity — computable by any client, assigned by no sequencer. Native payments execute there and nowhere else, so 255 partitions advance without coordinating.
A validator is not one machine. It is a pod cluster sharing a FoundationDB cluster, with the partitions distributed across pods. More capacity means more pods, and FoundationDB handles replication and tiered storage underneath.
Validator-set changes travel as signed EpochCerts — BLS quorum certificates that aggregate to one 48‑byte signature no matter how many signers. A late-joining node rebuilds the entire validator-set history from certs already in each partition's block stream.
An account's identity is a claim hash, frozen when the account opens and kept separate from the key that signs for it. Rotating to a different signature scheme is one transaction, and it disturbs neither sends nor receives.
There is no published throughput figure for Yoalto, because none has been measured on a network. When there is one, it will arrive with the harness and the hardware beside it.
The toolchain is Go. Bring up a devnet, record a file's hash on chain, and check the inclusion proof — the SDK verifies proofs client‑side, so nothing in this loop asks you to trust the node you queried.
| Capability | Status | Notes |
|---|---|---|
| Native coin (YOA) | Shipped | send, receive, change |
| Fungible tokens | Shipped | deploy, mint, burn, send, receive |
| NFTs | Shipped | collection deploy, mint, transfer, receive, burn |
| Attestations | Shipped | single and batched, hash-chain accumulator |
| NFT marketplace | Shipped | fixed-price listings, offers, royalty enforcement |
| Proof of stake | Shipped | epoch rotation, DKG group key committed on chain |
| Multi-node consensus | Shipped | HotStuff, end-to-end across partitions |
| Validator registration | Designed | genesis validators only; needs proof-of-possession |
| Slashing | Designed | two reasons defined; fault detection not built |
| Validator rewards | Designed | fees are burned today |
| Order-book DEX | Designed | schema only, engine deferred |
| EVM on chain 0 | Designed | smart contracts and governance |
| Public testnet | Designed | private dev clusters today |
Yoalto has no mainnet and no public testnet. There is no token sale, no market, and no published tokenomics — the native token exists in the protocol as gas and stake, and nothing beyond that has been decided.