height 23719 of 23719 on the network. 9 peer(s) connected, 77 in its peer directory; 1015 block(s) followed and 844 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.
Rehearse a fork
The command that starts a rehearsal of your chain on your own machine, and what its genesis would carry. A rehearsal is for testing an application against a chain of your own; nothing on it is evidence of anything. The four stages say what comes after.
Build the command
Written in this tab and sent nowhere. The chain ids it refuses are the realms in this build’s register.
Your rehearsal
The command is written here, in this tab, and goes nowhere: you copy it and run it on your own machine. The taken chain ids are the realms in this build's register.
The command
node scripts/fork.mjs up --name "Lindworm Freight" --chain-id 606060 --validators 3 \
--allocate treasury:STR:1000000:STR.lindworm-freight- Owner and treasury domain
STR.lindworm-freight- Data root
.sourceless/forks/lindworm-freight-606060- Althing bar (51%, rounded up)
- 77 of 150 voting power
- What that means
- 2 of 3 seats decide every chain parameter
Anyone who knows the name Lindworm Freight and the id 606060 can derive these keys.
A rehearsal's keys are not custody, and the script says so on every run. A chain that will carry value starts from private production keys: stage 2.
Once it is running
node scripts/fork.mjs statusreads what every node holds right now.node scripts/fork.mjs seedgives the chain work, so it advances. An idle chain that does not advance is not a fault: a producer with an empty queue seals nothing.node scripts/fork.mjs downstops it and keeps the chain;upagain resumes it from the log.- Every port is ephemeral and loopback. The ports of your run are in the banner and in
<data root>/fork.json. - Then add the rest. Followers of every class, an explorer, the door, spaces and threads each start against the rehearsal: the stack has the command for each.