diff options
| author | fanquake <fanquake@gmail.com> | 2023-03-19 12:09:20 +0000 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2023-03-19 12:11:47 +0000 |
| commit | 0973018067eb9445bfdc33a67d06ad5583e7d579 (patch) | |
| tree | d524521df6a8330eaec81b412d2a5c6220abd64f /src | |
| parent | 053b2d33772189468e9bef76840f59b8d44e6ab1 (diff) | |
| parent | 6d24d1ef2be7a86ddd798c4966d705e72013b6af (diff) | |
Merge bitcoin/bitcoin#27265: test: check that sigop limit also affects ancestor/descendant size (27171 follow-up)
6d24d1ef2be7a86ddd798c4966d705e72013b6af test: check that sigop limit also affects ancestor/descendant size (Sebastian Falbesoner)
Pull request description:
This is a follow-up to #27171, adding a check that the sigop-limit vsize logic is also respected for {ancestor,descendant}size calculation (as suggested in https://github.com/bitcoin/bitcoin/pull/27171#pullrequestreview-1331143909). For simplicity, we use a one-parent-one-child cluster here and only check for the case that the sigop-limit equivalent size is larger than the serialized vsize.
ACKs for top commit:
glozow:
code review ACK 6d24d1ef2be7a86ddd798c4966d705e72013b6af, thanks for taking!
Tree-SHA512: dc65e455d06cfef1f1d6a53b959f99ec1ca3fe51c98dc1ed5826614b5619773d34aff0171c43a0ede4fd45605b2eb7a9278e027196128bb7ad8586b859f1cf70
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions