diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2020-11-02 10:12:00 +0100 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2020-11-02 10:12:06 +0100 |
| commit | c5ec0367d718544caa3a1578d6c730fc92ee4e94 (patch) | |
| tree | 04509a4643f08cca98bdc10c35ccd209d2e19109 /depends | |
| parent | 867dbeba5f91be15ca0d4a7303a71957ff9a37ad (diff) | |
| parent | 3d0556d41087f945ed0a47a5d770076ad42ce432 (diff) | |
| download | bitcoin-c5ec0367d718544caa3a1578d6c730fc92ee4e94.tar.xz | |
Merge #20165: Only relay Taproot spends if next block has it active
3d0556d41087f945ed0a47a5d770076ad42ce432 Increase feature_taproot inactive test coverage (Pieter Wuille)
525cbd425e2f6a1dbd0febc53d7ada22cec4661f Only relay Taproot spends if next block has it active (Pieter Wuille)
Pull request description:
There should be no change to mempool transaction behavior for witness v1 transactions as long as no activation is defined. Until that point, we should treat the consensus rules as under debate, and for soft-fork safety, that means spends should be treated as non-standard.
It's possible to go further: don't relay them unless the consensus rules are actually active for the next block. This extends non-relay to the period where a deployment is defined, started, locked in, or failed. I see no downsides to this, and the code change is very simple.
ACKs for top commit:
Sjors:
utACK 3d0556d41087f945ed0a47a5d770076ad42ce432
MarcoFalke:
review ACK 3d0556d41087f945ed0a47a5d770076ad42ce432 🏓
jnewbery:
utACK 3d0556d41087f945ed0a47a5d770076ad42ce432
Tree-SHA512: ca625a2981716b4b44e8f3722718fd25fd04e25bf3ca1684924b8974fca49f7c1d438fdd9dcdfbc091a442002e20d441d42c41a0e2096e74a61068da6c60267a
Diffstat (limited to 'depends')
0 files changed, 0 insertions, 0 deletions