This fixes an oversight from the move of nChainTx from the user-supplied snapshot metadata into the hardcoded assumeutxo chainparams.
Since the nChainTx is now unused in the metadata, it should be removed in a future commit.
See: #19806 (review)
This fixes an oversight from the move of nChainTx from the user-supplied snapshot metadata into the hardcoded assumeutxo chainparams.
Since the nChainTx is now unused in the metadata, it should be removed in a future commit.
See: #19806 (review)
This fixes an oversight from the move of nChainTx from the user-supplied
snapshot metadata into the hardcoded assumeutxo chainparams.
Since the nChainTx is now unused in the metadata, it should be removed
in a future commit.
Code review ACK 931684b24a89aba884cb18c13fa67ccca339ee8c
It seems reasonable to just ignore the SnapshotMetadata::m_nchaintx value instead of checking it as long as it's going away. Will there be a followup PR to remove it?
23 | @@ -24,6 +24,8 @@ class SnapshotMetadata
24 |
25 | //! Necessary to "fake" the base nChainTx so that we can estimate progress during
Reference for myself #19806 (review)
utACK 931684b modulo AppVeyor test issue:
src\test\validation_chainstatemanager_tests.cpp(278,1): error C3493: 'bad_nchaintx' cannot be implicitly captured because no default capture mode has been specified
Thanks for the reviews @ryanofsky @Sjors. I've pushed a commit removing the nchaintx value from the snapshot metadata. This will of course render previously-generated snapshots unusable, but given that there's currently no way of actually making use of the snapshots I don't think that's an issue.
Other than breaking half the CI's: sounds good :-)
This value is no longer used and is instead specified statically
in chainparams. This change means that previously generated
snapshots will no longer be usable.
Other than breaking half the CI's: sounds good :-)
Oops! Fixed.
Code review ACK 91d93aac4e3fe6fff5ef492ed152c4d8fa6f2672. No change to previous commit, just new commit removing now unused utxo snapshot field and updating tests.
utACK 91d93aac4e3fe6fff5ef492ed152c4d8fa6f2672
I haven't reviewed this because I am still reviewing #19806, but the changes are likely ok to merge in the meantime.