height 23715 of 23715 on the network. 9 peer(s) connected, 77 in its peer directory; 1011 block(s) followed and 840 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.
What other chain families give the people who launch a chain of their own, held against what a SourceLess fork has. 17 ideas: 11 part built, 6 not built yet. Each says where it comes from and what exists today. An idea is a proposal, not a promise.
Part built
From Avalanche CLI, Cosmos Spawn and Ignite
Answer a few questions (name, chain id, seats, allocations, owner domain) and get the genesis file and a sidecar describing it, ready for a production launch or a rehearsal.
Today: Rehearse a fork writes the command; the fork command writes the genesis. The wizard would write the genesis itself, every allocation included, and show its hash before anything starts.
Part built
From Cosmos Spawn (make testnet), Polkadot Pop CLI (pop up), Hedera Solo
Seats, a follower of each class, an explorer, a door and a funded faucet, from one command, torn down by one.
Today: The fork command starts the seats and funds four accounts with seed. Followers, the explorer and the door each start against a fork today, one command each: the stack lists them.
Idea
From Cosmos Interchain Security (spawn time)
A fork announces a launch time; it starts only if enough seats have committed by then, and is rescheduled if not, so no chain is born short of the validators it was planned with.
Today: Nothing waits today: the fork command starts every seat it is given at once.
Part built
From Canton (LocalNet, DevNet, TestNet, MainNet)
The same plan promoted from a rehearsal on one machine, to a testnet on production keys, to the chain that carries value, each step recorded.
Today: Two rungs exist: a rehearsal (derived keys) and a chain on its own production keys. The recorded promotion between them does not.
Idea
From Hyperledger Besu, Hedera Solo
Say what the fork must survive and serve, and get how many seats, archives and light nodes it needs, which host each goes on, and the command for each.
Today: The three classes and the command for each are on the stack. The planner that chooses the numbers is not built.
Idea
From AvaCloud's chain dashboard
Block production, seat liveness, finality and discovery for one fork, read from its own nodes.
Today: The fork command writes a manifest with every node's endpoints, and only fork.mjs status reads it. A dashboard pointed at a fork is not built.
Part built
From Kaleido, Caldera and other rollup services, which ship one per chain
Each fork gets this explorer, with its links pointing at that fork's own wallet and door.
Today: strblk explorer --genesis already follows a fork. Its links to the wallet and the books still point at SourceLess's own surfaces.
Part built
From Ignite's built-in faucet
Developers on a test fork take small amounts from a faucet instead of asking the treasury.
Today: The faucet contract is in the catalogue (draft it for your fork); starting one automatically with a test fork is not built.
Idea
From Kaleido's document store, rollup data-availability choices
A contract template that records a space's manifest root at a height, so a business can show which version of its data a payment or a vote referred to.
Today: Spaces work on a fork, and contracts work on a fork, but a contract cannot read a space. A template could store a manifest root a caller gives it; it would record the root, not verify it.
Part built
From Messaging relayers across chain families
Threads on a fork with a courier that carries each sealed message to its readers.
Today: Threads, receipts and key epochs are recorded on a fork today, and a courier now exists: Talaria, which a fork's operator turns on for a holder node that seals no blocks. It is off by default, never runs on a validator seat, and holds sealed parcels it cannot read for a week at most. Delivery is from the command line only; there is no wallet inbox yet.
Part built
From SourceLess's own design, finishing Praeco
Fork nodes find each other at rendezvous points derived for their chain alone, with no seed list to publish.
Today: The points are per chain now: every node announces points derived from its genesis hash and chain id, so a fork's and Asgard's never coincide, and a node's status counts the known peers that meet there. Nothing dials from them yet, and a node with no peer at all still needs a seat to dial: there is no shared lookup that a stranger can ask.
Idea
From SourceLess's own design
A phone's eSIM as the way in: the device's secure element holds, or unlocks, an STR.domain key, and the door admits the phone with the same signed challenge a wallet answers today.
Today: The door exists and works on a fork. Nothing in this build touches an eSIM: it would need the key kept in the device's secure element, a provisioning partner to issue the profile, and a way to recover the name if the phone is lost.
Part built
From ZKsync Prividium, Besu permissioning, AvaCloud private chains
A fork where only listed names may hold an asset, read a space or sign in, with a read endpoint that enforces it.
Today: The allowlist token, private spaces and the door each exist. A read endpoint that enforces who may ask is not built.
Part built
From Hyperledger Fabric's chaincode lifecycle
On a consortium fork, a contract goes live only when enough member organisations have approved it.
Today: The multisig, timelock and DAO treasury templates hold value under several signers. Approving the deployment itself is not built.
Part built
From The OP Stack's Superchain (coordinated hardforks)
A fork chooses to follow SourceLess's rule versions as they activate, or to pin its own schedule.
Today: A new fork's genesis can carry its own consensus schedule, committed into its identity. Following SourceLess's schedule automatically is not built.
Part built
From The OP Stack's Superchain Registry
A public directory of forks: each one's chain id and genesis hash, and a mark for a fork that runs stock SourceLess against one that changed it, with a diff of its genesis.
Today: Realms lists the register a fork is checked against. A directory of forks, and the genesis diff, are not built.
Idea
From Avalanche ICM, Polygon AggLayer, the Superchain's interop
A fork and Asgard, or two forks, pass messages through a relayer, with every crossing visible in the explorer.
Today: Every record is bound to one genesis, so none crosses today, by design: a fork has no bridge. Crossing would be a new component with its own trust, and it would be said so.