height 23725 of 23725 on the network. 9 peer(s) connected, 77 in its peer directory; 1021 block(s) followed and 850 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.
What this follower is, locally
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.
Binance fork
A business fork for Binance: a chain of its own, started from the SourceLess software with its own genesis, its own validators and its own assembly. In progress.
In progress
- Fork for
- Binance
- Slot
3of 799- Chain id held
1313003- Registered
- 2026-10-29
- Genesis hash
- none yet
- Seats, treasury, chain name
- decided with the partner
What in progress means
In progress: a partner is registered and the fork is on its way to a genesis. Until its genesis is made there is no chain to read yet.
Once deployed, the fork is identified by its genesis hash, which the realms page explains.
The partner and the contract
The partner
Binance. A cryptocurrency exchange.
- Website
binance.com- Registered
- 2026-10-29
Smart contract
Deployment pending
- Contract
- SourceLess Business Fork Licences (SLFORK)
- Standard
- ZK13 NFT, one token per slot
- Planned address
zk13str_c21bc264ad5c403d50ec9b139c2408f18f0d39c7_6380no contract is at it until the collection is deployed- Token
3of 799- Token metadata
sourceless-fork-licence:slot=3;chain-id=1313003- Ownership
- It passes to the partner once the fork is paid for, and from then on only the partner can move it.
Where it stands
The agreement, then the four stages every fork walks from a rehearsal to a chain that carries value.
Done
Agreed and registered
The agreement is recorded and a slot, with its chain id, is held for the fork.
Next
Rehearse
A rehearsal on the partner’s own machines, against the applications they will run.
Not started
Make the genesis
The chain name, the id, the seats and the treasury are fixed, for ever.
Not started
Launch
The fork’s seats start and the chain runs.
Not started
Publish and operate
The genesis hash is published here, and the fork is deployed.
Rehearse it with the held chain id
node scripts/fork.mjs up --name "Binance" --chain-id 1313003 --validators 3 \
--allocate treasury:STR:1000000:STR.binanceThe held chain id with three seats and a treasury of 1,000,000 STR, which are placeholders: the seats, the treasury and the final chain name are decided with the partner. A rehearsal is a throwaway on one machine; the builder writes any other.