getblockchaininfo.verificationprogress never reaching 1.0 #26433

issue sander2 openend this issue on November 1, 2022
  1. sander2 commented at 11:49 am on November 1, 2022: none

    Expected behavior

    getblockchaininfo.verificationprogress is 1.0 when it is done syncing

    Actual behavior

    The highest value that getblockchaininfo.verificationprogress gets to is something like 0.9999976273867589. As a result, we can not rely on this value to determine if syncing is complete. We can not rely on getblockchaininfo.initialblockdownload either due to #26432

    To reproduce

    Call getblockchaininfo on a synced node and observe that verificationprogress is < 1.0.

    System information

    Version 22 of the bitcoin core binary, downloaded from the website

  2. sander2 added the label Bug on Nov 1, 2022
  3. maflcko removed the label Bug on Nov 1, 2022
  4. maflcko added the label RPC/REST/ZMQ on Nov 1, 2022
  5. maflcko added the label Questions and Help on Nov 1, 2022
  6. maflcko commented at 11:58 am on November 1, 2022: member

    As per the documentation, the field is only an estimate. The guess will take into account the duration since the timepoint of your tip block and the estimate of the rate of transactions.

    Maybe you are better off crafting your own estimate, based on your needs?

  7. sander2 commented at 12:12 pm on November 1, 2022: none

    As per the documentation, the field is only an estimate. The guess will take into account the duration since the timepoint of your tip block and the estimate of the rate of transactions.

    Maybe you are better off crafting your own estimate, based on your needs?

    Hmm that’s not very useful then for our needs. After some googling, I found https://bitcoin.stackexchange.com/questions/96452/how-to-detect-that-full-node-is-in-sync-using-jsonrpc . Can you confirm that if getblockchaininfo.headers is equal to getblockchaininfo.blocks, the sync is complete?

  8. maflcko commented at 12:44 pm on November 1, 2022: member

    Again, it might be better if you stated your problem/use-case and designed a estimate function for your problem/use-case. It is not possible to design a “sync” function without knowing what it should do.

    Note, usually the issue tracker is used to track technical issues related to the Bitcoin Core code base. General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange or the #bitcoin IRC channel on Libera Chat.

  9. maflcko commented at 7:12 am on November 2, 2022: member
    Closing for now. Let us know if you have any other questions.
  10. maflcko closed this on Nov 2, 2022

  11. bitcoin locked this on Nov 2, 2023

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2024-07-01 10:13 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me