Mar 29, 2023

The aspect that this leaves out presently is the "chaser" object that manages and validates data fed from multiple concurrent peers into a single tree, determining the greatest work, and organizing that into the store. Presently it's just a single peer connection that validates and organizes into the store. The block download is also functional, but as was the case with headers, is not yet validating. Now that headers are storing their context (from chain state), blocks can be validated upon arrival. A couple days ago I did the work to size and verify the validation and confirmation metadata tables. So next step is to validate the full chain as it arrives from a single peer. I'll work on that next. Once that is done I'll implement transaction_in in a similar manner. Its chaser manages the tx pool. Then I'll add in the header/block/tx out protocols, which are even simpler than the incoming protocols. Then will move on to the chasers (header tree, concurrent block downloader/validator/confirmer, tx graph).