Describe validator rounds as spans of time The genesis gives roundMillis, at least a minute. The first block after a round's end closes it, an empty one if nothing else waits, and the changes voted in take over from the next height. The pages give the round, its end and the set votes are judged by in ledger info, and the vote command's refusal in the last seconds of a round.
Describe the ledger's dust rule, restarts, lock and wake rules The fee spork carries the least amount of a transfer that opens an account. A halted ledger starts again three times in six hours, the ledger folder is locked to one process, keys that are not Ed25519 points are refused, and a node signs while the validators hold its key. The consensus pages give the timer cap, how a resting height wakes, the re-offer of waiting transactions and the reserve for vouched peers.
Describe a spork proposal as having no effect and add a private network A proposal no longer holds the ledger back while it waits for its second signature, so the sporks page now says that the old rule stays in force until the change is co-signed, including for a blacklist entry. The genesis is made with util ledger-genesis, which the node page, the ledger page and the sporks page now say, and the options and the ledger folder join the page on running Hedgehog. A new page explains how to run nodes that trust board keys of their own and keep to themselves, and how to start a ledger on them.
Describe the ledger as part of master The ledger branch has been merged, so the ledger pages no longer carry a banner that calls them upcoming, and the home page and sidebar list the ledger beside the other features. Pages that placed the ledger sporks, endpoints or mint entries on a separate branch now say they are on master and not in release 0.0.8. The note that no genesis comes with the node stays in the text of the ledger pages.
Say that waiting transactions survive a promotion A node that replaces another in the same process, as a signing node replaces the observer it started as, takes over the transactions that waited for a block. Before, a promotion dropped what the node had taken in. A restart of the process still loses them, which the pages now say in those words.
Describe the send queue that puts votes ahead of bulk Each peer has a queue of two lanes. Ballots, heartbeats and statuses are written before proposals, decisions and transactions, so a big block that fills the stream no longer holds up the votes. Each lane is bounded in bytes. The old text said that a message the stream could not take was dropped quietly.
Describe the cap on what a spork mints to one address A node refuses a spork mint once the mints made to its address would pass the sum that the mint spork grants that address. This keeps a later version of the spork from paying an address twice by giving the same grant a new number. The total is derived from the blocks and a claimed legacy address keeps counting under its own address.
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 a page for the ledger command line Describe hedgehog cli ledger: info, balance and block for reading, and transfer, claim and vote for sending. The page has worked examples, the two-step claim with the legacy wallet's signmessage, the text that is signed, when --chain is needed and what the exit codes mean. It is linked from the sidebar, the home page and the ledger overview.
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.
Bring the ledger pages up to date with the node branch Describe claims, transfers and fees, the authority the node answers, the view-based consensus engine, the durable sign state, the driver and the transport in the application. List what is not wired yet. Follow the source-list convention of the other pages.
Document how the ledger is implemented Add a page on the ledger classes, byte layouts, checks and block log, linked from the ledger page and the sidebar.
Document the upcoming ledger Add a Ledger page that describes the ledger branch: what the chain records, how a block is made and certified, validator rounds, heartbeats and the block log. The page is marked as upcoming, and is listed under a new Upcoming group in the sidebar and on Home.