Jun 30, 2021

Dear Eric After spending some time lookin at the reorg listener interface in full_node*, I realize that the distinction of the process of the header sync (which is happening conceptually first: header-first sync, right) versus block sync, is not clear to me. Is LibBitcoin somehow integrating these two into one, so that there is only one reorg listener and event stream, and not two? How does that work out in practice. Is it that the reorg logics in LibBitcoin are trigged based on the headers only - and the reorg listener is trigged accordingly - and these logics *presume* that there will be data availability of the blocks in this chain, such that get/fetch/downloaded block listener events are presumed to follow for each block? Please explain