You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently call block-fetch directly in the chain-sync client RollForward handler. Instead, we should generate an event, and the ledger can decide when/if to fetch the block content. We'll need to provide a way for the ledger to ask for a range of blocks, such as a callback function that the consumer can define. This may need to include a connection ID(s) to ensure we ask a node that has already sent us the block headers
The text was updated successfully, but these errors were encountered:
We currently call block-fetch directly in the chain-sync client RollForward handler. Instead, we should generate an event, and the ledger can decide when/if to fetch the block content. We'll need to provide a way for the ledger to ask for a range of blocks, such as a callback function that the consumer can define. This may need to include a connection ID(s) to ensure we ask a node that has already sent us the block headers
The text was updated successfully, but these errors were encountered: