Nothing is addedto the brine.
The water leaves, and the salt stays. A proof-of-work chain with a fixed supply and no allocation to hand out.
A pan is a floor, a wall, a sluice, and time
A saltern is a field of shallow clay pans beside flat water. Seawater runs in a hand's depth deep and then nothing else is done: wind and sun take the water off the top, and whatever cannot evaporate is left lying on the floor. Nobody salts a pan. The pan is salted because the water was asked to leave.
Saltern is the same sequence turned into a chain. There is no premine, no sale, no reserved slice and no foundation allocation: a unit exists only because a block was found and the reward was left behind by the work. Addresses begin with S, the algorithm is unmodified RandomX on CPU, and the smallest unit is 0.00000001 SLT.
The schedule is arithmetic, not policy
Water leaves as vapour and the salt stays behind; that is the whole method, and it is slow on purpose. The emission is written the same way — nothing clever, everything checkable by hand.
86,400 ÷ 75 = 1,152 blocks a day · 1,152 × 20 = 23,040 SLT a day
720,000 ÷ 1,152 = 625 days an era · 625 × 24 = 15,000 hours
A halving series sums to twice its first term, so era one (14,400,000 SLT) is exactly half of everything there will ever be. When the last era runs out the reward is zero, and the supply stops where the arithmetic said it would.
Where the water stops is the only decision
Difficulty retargets every block from the last 120 timestamps, and one step cannot move it by more than a factor of four. Block times are median-filtered over 11 blocks; anything more than two hours ahead of the node's clock is rejected. There are no checkpoints and no remote configuration: a node follows the rules it was compiled with, or it forks away in public.
A pan does not make salt. It only decides where the water stops.
What exists today, unfinished rows included
| Consensus specification | published |
| Reference node | in progress |
| Testnet | not running |
| Windows wallet | released — v0.1.0, 213,225,918 bytes |
| Chain index | no data |
| Pools | none |
One line changed on 27 October 2026: there is an archive now, and an archive means a hash. It is printed in three places at once — the download page, the changelog and the release notes — and copied from one value rather than retyped. The node is still being built: a program that launches and a chain that exists are separate events, and only the first has happened.