- Add mention of BIP70 disabling by default at build time.
Any others?
E.g. does the burying of deployments of #16060 need to be mentioned? If so, where and how? For all of BIPs 34, 65 and 66?
Could also link to the buried deployments pull request?
See
ACK bcdab14673fd421fe3441980a0e50cce087420c2
Could also link to the buried deployments pull request?
Yes, but whether to put it under BIP9 or the affected deployment BIPs?
It could be appended to each deployment, similar to how ab0c35a did it.
I've decided to do both. Should be ready now.
0 | @@ -1,6 +1,6 @@ 1 | BIPs that are implemented by Bitcoin Core (up-to-date up to **v0.18.0**): 2 | 3 | -* [`BIP 9`](https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki): The changes allowing multiple soft-forks to be deployed in parallel have been implemented since **v0.12.1** ([PR #7575](https://github.com/bitcoin/bitcoin/pull/7575)) 4 | +* [`BIP 9`](https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki): The changes allowing multiple soft-forks to be deployed in parallel have been implemented since **v0.12.1** ([PR #7575](https://github.com/bitcoin/bitcoin/pull/7575)). The BIP 9 activation for BIPs 34, 65 and 66 was buried (hardcoded) in *v0.19.0* ([PR #16060](https://github.com/bitcoin/bitcoin/pull/16060)).
No strong opinion, but the fact that BIP 9 was responsible for their activation might be controversial. See e.g. https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2019-August/017267.html
OK, removing that then
10 | @@ -11,15 +11,15 @@ BIPs that are implemented by Bitcoin Core (up-to-date up to **v0.18.0**): 11 | * [`BIP 30`](https://github.com/bitcoin/bips/blob/master/bip-0030.mediawiki): The evaluation rules to forbid creating new transactions with the same txid as previous not-fully-spent transactions were implemented since **v0.6.0**, and the rule took effect on *March 15th 2012* ([PR #915](https://github.com/bitcoin/bitcoin/pull/915)). 12 | * [`BIP 31`](https://github.com/bitcoin/bips/blob/master/bip-0031.mediawiki): The 'pong' protocol message (and the protocol version bump to 60001) has been implemented since **v0.6.1** ([PR #1081](https://github.com/bitcoin/bitcoin/pull/1081)). 13 | * [`BIP 32`](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki): Hierarchical Deterministic Wallets has been implemented since **v0.13.0** ([PR #8035](https://github.com/bitcoin/bitcoin/pull/8035)). 14 | -* [`BIP 34`](https://github.com/bitcoin/bips/blob/master/bip-0034.mediawiki): The rule that requires blocks to contain their height (number) in the coinbase input, and the introduction of version 2 blocks has been implemented since **v0.7.0**. The rule took effect for version 2 blocks as of *block 224413* (March 5th 2013), and version 1 blocks are no longer allowed since *block 227931* (March 25th 2013) ([PR #1526](https://github.com/bitcoin/bitcoin/pull/1526)). 15 | +* [`BIP 34`](https://github.com/bitcoin/bips/blob/master/bip-0034.mediawiki): The rule that requires blocks to contain their height (number) in the coinbase input, and the introduction of version 2 blocks has been implemented since **v0.7.0**. The rule took effect for version 2 blocks as of *block 224413* (March 5th 2013), and version 1 blocks are no longer allowed since *block 227931* (March 25th 2013) ([PR #1526](https://github.com/bitcoin/bitcoin/pull/1526)). The BIP 9 activation for this softfork was buried (hardcoded) in *v0.19.0* ([PR #16060](https://github.com/bitcoin/bitcoin/pull/16060)).
bip 34 was buried in bip 90 (a different pull request). See e.g #9879
OK, will revert that change.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
ACK 82c11773dc7493e1863b3b8277958f744a321eb9
Concept ACK.
In the first line
BIPs that are implemented by Bitcoin Core (up-to-date up to **v0.18.0**):
s/18/19/
s/18/19/
Might want to mention the version bump in the release process? https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md#before-every-major-and-minor-release
ACK 60e855f5c50c4578bbab93282226f236853491dc
Milestone
0.19.0