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
If I only want to monitor the blocks from a starting point, is there a way I can tell nakamoto not to go sync headers all the way to genesis on boot up? I don't need history, and I would trust a checkpoint or multiple peers telling me the same block 100 confirmations back is valid.
If it's not already built, where would you recommend I look in the code to try to add this feature?
The text was updated successfully, but these errors were encountered:
looking at the BIP https://en.bitcoin.it/wiki/BIP_0157 looks like there is no problem it say "I start monitoring from block X" where block X is somehow one of the recent one.
If it's not already built, where would you recommend I look in the code to try to add this feature?
I think that needs to be built, and we should pass a --stat-height in the https://github.com/cloudhead/nakamoto/blob/master/node/src/main.rs#L11 and state modifying it you will go down to the core and see where the node is starting to fetch headers from the block 0 (I think you need to search by block hash not for block height)
If I only want to monitor the blocks from a starting point, is there a way I can tell nakamoto not to go sync headers all the way to genesis on boot up? I don't need history, and I would trust a checkpoint or multiple peers telling me the same block 100 confirmations back is valid.
If it's not already built, where would you recommend I look in the code to try to add this feature?
The text was updated successfully, but these errors were encountered: