Skip to content

Conversation

@jnewbery
Copy link
Contributor

This PR reverts #14054 following discussion on the bitcoin-dev mailing list.

It also adds release notes to clearly document that the enablebip61 option will be disabled by default in a future release before being removed entirely.

@jnewbery jnewbery force-pushed the reject_message_by_default branch from 2188763 to a756363 Compare March 14, 2019 19:46
@jnewbery
Copy link
Contributor Author

Oops. Accidentally changed some unrelated formatting in the release-notes docs. Force pushed to fix.

@maflcko maflcko changed the title [p2] Enable reject messages by default 0.18: [p2p] Enable reject messages by default Mar 14, 2019
@maflcko
Copy link
Member

maflcko commented Mar 14, 2019

utACK a756363, but the release notes change should (also) be done upstream in the wiki. Otherwise you risk it getting overwritten.

@maflcko maflcko added the P2P label Mar 14, 2019
@maflcko maflcko added this to the 0.18.0 milestone Mar 14, 2019
@gmaxwell
Copy link
Contributor

utACK

@Sjors
Copy link
Member

Sjors commented Mar 14, 2019

utACK a756363

@maflcko maflcko merged commit a756363 into bitcoin:0.18 Mar 14, 2019
maflcko pushed a commit that referenced this pull request Mar 14, 2019
a756363 [docs] document BIP 61 deprecation (John Newbery)
da14d90 [p2p] Enable BIP 61 REJECT messages by default (John Newbery)

Pull request description:

  This PR reverts #14054 following discussion on the bitcoin-dev mailing list.

  It also adds release notes to clearly document that the `enablebip61` option will be disabled by default in a future release before being removed entirely.

Tree-SHA512: 0c9162045a4fb95689a0cb2de19f98a83636c9a6fb7ffa6809773b593c6c00b14e0480683e4d1c48e9b7f90e89cf7c2dca18bff42f5d2da2a43c522039e9f1ee
@jnewbery
Copy link
Contributor Author

Changed release notes upstream

Thanks Marco

@jnewbery jnewbery deleted the reject_message_by_default branch March 14, 2019 21:16
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Dec 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants