height 23699 of 23699 on the network. 9 peer(s) connected, 77 in its peer directory; 995 block(s) followed and 825 pulled in by sync since this follower started. Caught up: this follower holds every block any peer has claimed, so every panel below is the whole chain. Genesis 1cf8655125cc1bbb…, producers genesis.
Following 7 seed(s) — their addresses are not published here, for the reason the peer table gives. Its store is held under its own Cerberus lease — no other node’s store is opened, touched or stopped.
Vanaheim: a chain of your own, started from the SourceLess software with its own genesis, its own validators and its own assembly. It runs the whole of SourceLess, from contracts and hostless storage to STR.talk, and shares nothing with Asgard but the code. Allied with Asgard and governed by nothing in it.
Four stages. The first takes a minute on one machine; the second is what separates a rehearsal from a chain anybody may trust.
Keys derived from the name and id
node scripts/fork.mjs up --name … --chain-id … --validators … builds a genesis, starts every seat on this machine and prints the genesis hash and the endpoints. The banner calls it a rehearsal: nothing on it is evidence of anything, and it is how you test an application against a chain of your own.
Made and held privately
The keys that seal a chain carrying value are made and held privately, never derived from its name. SourceLess does this with you before launch; it is the step that makes your keys yours.
Your seats, your keys
node scripts/fork.mjs up --genesis <file> --seat <dir> … starts the chain from the production genesis on its own seats. The banner says DELIVERED, the only path that produces a chain anybody may put value on.
Your validators, for the life of the chain
Every port the command opens is loopback. A published endpoint, a domain name, TLS and a seed list are separate work, and so is running the machines every day after: the stack says what each part of a running fork needs.
Nearly every part signs its records over the genesis hash, so it works on your fork as on Asgard, and nowhere else.
Built
Every SourceLess node is one of three classes, set by how much it keeps. Only the two that keep a chain may seal, and only when the genesis gives them a seat.
Partly built
Praeco is hostless peer discovery: nodes publish self-signed records (an ed25519 and ML-DSA pair), exchange them with the peers they meet, and drop a record that fails five dials in a row. Records expire after 30 minutes.
Built
Data with no server. A space (Oort) records on chain who may read it, its price and a manifest root; the content is never on chain. It is cut into encrypted 256 KiB chunks (Accretion) with Merkle proofs, so a peer holding chunks cannot read them. Records from a spreadsheet seal into a space (Stardust, from Kuiper's CSV import), and a reader can verify what it fetched against block headers without keeping the chain (Lagrange, --light).
Built
Every contract template deploys on a fork: the same compiler gives the same bytecode, the same VM charges the same gas, and the same deployer and salt give the same address.
Partly built
Threads between STR.domains, sealed end to end (Occultation). The chain records that a message was posted, who may read a thread, receipts and key epochs; the message itself is sealed to its readers.
Built
Thrymgjoll is the holder's door: an application a holder signs in to with their STR.domain. It holds no key. The wallet signs a challenge that carries the genesis hash, and the door checks it against the chain.
Not built
A phone's eSIM as a way in: the device carries, or unlocks, the key of an STR.domain, and the door admits it with the same challenge a wallet signs today.
Partly built
This explorer, pointed at your fork. It follows your chain as a node does and shows its blocks, names, spaces, threads and contracts.
3seats, three distinct producers
20blocks in 60 seconds
3,000 msslot, one block per slot
1head and one state root on every node
Measured on 2026-09-17, on Windows 11, from the command the builder opens on: height 7 at the first reading and 27 sixty seconds later, chainValid true on all three nodes. Every number is from one machine, so the seats shared a clock and a disk. A fork across several machines, and a production launch end to end, are not measured yet.
Stated before what it gets, because this is the assumption that ruins a fork.
Fixed when the genesis is
Changeable by your assembly, after a delay