Name the folder of each chain in the ledger pages The block log and the sign state of a chain sit in a folder of their own below ledger, named by the start of the chain id, and the node logs that folder at start. A node given another genesis opens another folder and leaves the old ones. The pages said the folder was the same for every genesis and had to be moved away by hand.
Say that the ledger can be read and used from outside The ledger pages said that no REST endpoint or command existed and that nothing read the status of the service. Remove those statements and point to the endpoints and the command line. List the new classes, the reads the ledger gives the outside, the report fields for unset and lagging sporks, and the tests of the resource and the commands.
Add figures and diagrams to the ledger pages Draw how blocks link, where coins come from and go, a height decided in its second view, the bytes of a block, the leaves of the state root, the recovery of the block log, when a mint entry is due and what a node does from start to its first vote. Diagrams show the steps of a view, the checks of a block, the intake of the driver, sync, the start of the service and how a mint is authorised.
Split the ledger pages and document the ledger in the daemon The implementation page is now a hub with six pages under it, and two new pages explain how to run a ledger node and which sporks the ledger reads. They cover the genesis file, the validator key, the snapshot check, the spork authority, the blacklist and fee sporks, and the service that runs the ledger in the daemon. The sidebar nests the ledger pages under the Ledger page.