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
Currently, verify-checkpoints command always starts verification at genesis, and either stops at the most recent network ledger, or at a specified --history-ledger. The problem is verifying all the way back to genesis takes hours, and typically operators want to keep trusted hashes file up-to-date, so verifying the whole chain isn't efficient. We should design a solution to amortize the cost of trusted hash generation.
The text was updated successfully, but these errors were encountered:
Currently,
verify-checkpoints
command always starts verification at genesis, and either stops at the most recent network ledger, or at a specified--history-ledger
. The problem is verifying all the way back to genesis takes hours, and typically operators want to keep trusted hashes file up-to-date, so verifying the whole chain isn't efficient. We should design a solution to amortize the cost of trusted hash generation.The text was updated successfully, but these errors were encountered: