Module forest_filecoin::chain_sync::tipset_syncer

Structs

• TipsetGroup 🔒
• TipsetProcessor 🔒
  The TipsetProcessor receives and prioritizes a stream of Tipsets for syncing from the ChainMuxer and the SyncSubmitBlock API before syncing. Each unique Tipset, by epoch and parents, is mapped into a Tipset range which will be synced into the Chain Store.
• TipsetRangeSyncer 🔒

Enums

• InvalidBlockStrategy 🔒
• TipsetProcessorError
• TipsetProcessorState 🔒
• TipsetRangeSyncerError

Constants

• MAX_TIPSETS_TO_REQUEST 🔒

Functions

• block_sanity_checks 🔒
  Checks optional values in header.
• block_timestamp_checks 🔒
  Check the clock drift.
• check_block_messages 🔒
  Validate messages in a full block, relative to the parent tipset.
• fetch_batch 🔒
  Ask peers for the Messages that these Tipsets should contain. Requests covering too many tipsets may be rejected. As of 2023-07-13, requesting for 8 tipsets works fine but requesting for 64 is flaky.
• fetch_batch_inner 🔒
• for_each_tipset_until_epoch_overreached 🔒
• sync_headers_in_reverse 🔒
  Download headers between the proposed head and the current one available locally. If they turn out to be on different forks, download more headers up to a certain limit to try to find a common ancestor.
• sync_messages_check_state 🔒
  Going forward along the tipsets, try to load the messages in them from the BlockStore, or download them from the network, then validate the full tipset on each epoch.
• sync_tipset 🔒
• sync_tipset_range 🔒
  Sync headers backwards from the proposed head to the current one, requesting missing tipsets from the network. Once headers are available, download messages going forward on the chain and validate each extension. Finally set the proposed head as the heaviest tipset.
• validate_block 🔒
  Validate the block according to the rules specific to the consensus being used, and the common rules that pertain to the assumptions of the ChainSync protocol.
• validate_tipset 🔒
  Validates full blocks in the tipset in parallel (since the messages are not executed), adding the successful ones to the tipset tracker, and the failed ones to the bad block cache, depending on strategy. Any bad block fails validation.
• validate_tipset_against_cache 🔒
  Check if any CID in tipset is a known bad block. If so, add all their descendants to the bad block cache and return an error.