Yoalto/About

A payment chain,
mid-construction.

Yoalto is a Layer 1 built around one idea: that most payments never need to touch each other, so they should not have to queue behind each other. It is written in Go, licensed Apache‑2.0, and it is not finished.

Principles

Four commitments we can be held to.

01

Ship the hard part first

Parallel execution and deterministic account residence were built before any of the conveniences that sit on top of them. Deferred fundamentals become migrations, and migrations are where chains break.

02

Specify, then implement

The sync design, the cert protocol and the transaction roadmap were written before the code that implements them, and they are still the thing new work is scoped against rather than rediscovered from.

03

Publish the unflattering numbers

Every page on this site lists what is not built alongside what is. The status tables are generated from the same document the team plans against, not from a marketing summary of it.

04

No figure without a method

There is no throughput number anywhere on this site, because none has been measured on a network. When there is one it will arrive with the harness, the hardware and the failure cases attached.

In brief

The short version.

What it isA Layer 1 for parallel native payments
LanguageGo — a workspace monorepo
LicenseApache-2.0
Partitions256 — chain 0 plus 255 payment lanes
ConsensusHotStuff, per partition, one validator set
StorageFoundationDB with a sparse Merkle tree
Native tokenYOA — gas and stake
StagePre-mainnet; private development clusters
History

It used to be called Flink.

Yoalto grew out of Flink, a feeless block‑lattice payment network. The name changed and so did the architecture: the block‑lattice gave way to 256 HotStuff‑finalized partitions over a shared FoundationDB cluster, and the Nano‑style SEND/RECEIVE pattern is the part that survived the rewrite.

Artefacts from that era are still around — the whitepaper in the repository describes the old design, and its performance figures belong to it rather than to Yoalto. They are not reproduced on this site.

There is no foundation, no funding announcement, no token sale and no published tokenomics. If you read any of those about Yoalto somewhere, it did not come from here.

Source and licence.

Yoalto is Apache‑2.0. The repository is private for now, which means the licence is a statement of intent rather than something you can act on yet — worth saying outright rather than leaving "open source" to do the work.

Repository
github.com/yoalto-rnd/yoalto — private
Go monorepo · Apache-2.0