diff options
| author | Andrew Chow <github@achow101.com> | 2023-10-11 14:19:22 -0400 |
|---|---|---|
| committer | Andrew Chow <github@achow101.com> | 2023-10-11 14:25:23 -0400 |
| commit | e3eb3aae30269b0c9478afe946e7a0871cab5b69 (patch) | |
| tree | 2b0e9f32d7a6d27f2f99c6785d6318d7dcfb1956 /test/functional/feature_proxy.py | |
| parent | d98d88c779bc28794e5936d5ad08fd2df3d992a4 (diff) | |
| parent | 2e31250027ac580a7a72221fe2ff505b30836175 (diff) | |
Merge bitcoin/bitcoin#28625: test: check that loading snapshot not matching AssumeUTXO parameters fails
2e31250027ac580a7a72221fe2ff505b30836175 test: check that loading snapshot not matching AssumeUTXO parameters fails (Sebastian Falbesoner)
Pull request description:
This PR adds test coverage for the failed loading of an AssumeUTXO snapshot in case the referenced block hash doesn't match the parameters in the chainparams. Right now, I expect this would be the most common error-case for `loadtxoutset` out in the wild, as for mainnet the `m_assumeutxo_data` map is empty and this error condition would obviously always be triggered for any (otherwise valid, correctly encoded) snapshot. Note that this test-case is the simplest scenario and doesn't cover any of the TODO ideas mentioned at the top of the functional test yet.
ACKs for top commit:
jamesob:
ACK https://github.com/bitcoin/bitcoin/pull/28625/commits/2e31250027ac580a7a72221fe2ff505b30836175
Sjors:
utACK 2e31250027ac580a7a72221fe2ff505b30836175
achow101:
ACK 2e31250027ac580a7a72221fe2ff505b30836175
Tree-SHA512: 8bcb2d525c95fbc95f87d3e978ad717d95bddb1ff67cbe7d3b06e4783f0f1ffba32b17ef451468c39c23bc1b3ef1150baa71148c145275c386f2d4822d790d39
Diffstat (limited to 'test/functional/feature_proxy.py')
0 files changed, 0 insertions, 0 deletions