📅 Original date posted:2019-10-17 📝 Original message:As this is a P2P protocol ...

Eric Voskuil [ARCHIVE] /

npub1sgs…px3c

2023-06-07 18:21:13

in reply to nevent1q…n9e7

📅 Original date posted:2019-10-17
📝 Original message:As this is a P2P protocol change it should be exposed as a version increment (and a BIP), not just as a conditional service. If the intent is to retain this protocol indefinitely, exposing it conditionally, then a service bit would make sense, but it remains a protocol change.

BIP61 is explicit:

“All implementations of the P2P protocol version 70,002 and later should support the reject message.“

e

> On Oct 17, 2019, at 12:54, Andreas Schildbach via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>
> On 16/10/2019 18.43, John Newbery via bitcoin-dev wrote:
>
>> Following discussion on this mailing list, support for BIP 61 REJECT
>> messages was not removed from Bitcoin Core in V0.19. The behaviour in
>> that upcoming release is that REJECT messages are disabled by default
>> and can be enabled using the `-enablebip61` command line option.
>
> Is there a NODE_* bit we can use to pick peers that support this
> (useful!) feature?
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Author Public Key

npub1sgs97fe0n9wehe6zw7drcxdz4cy9yt9pfqjv8gasz5jlk4zezc0quppx3c

Seen on

wss://relay.nostr.band

Show more details

Published at

2023-06-07 18:21:13

Kind type

1 Short Text Note

Event JSON

{ "id": "5f02d8dcd5edaa34fa01b78041098dd9acf859accde63d4bc3156b185afc65b5", "pubkey": "82205f272f995d9be742779a3c19a2ae08522ca14824c3a3b01525fb5459161e", "created_at": 1686162073, "kind": 1, "tags": [ [ "e", "fc240d6737eec3e3732c71a02d6bd551346f2bcb2e039d48bf20d899e18045d3", "", "root" ], [ "e", "1c018e5304576ded9d0e68c3aa32fde355d0ce15cdcbc0dcdf8a299173aa472b", "", "reply" ], [ "p", "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc" ] ], "content": "📅 Original date posted:2019-10-17\n📝 Original message:As this is a P2P protocol change it should be exposed as a version increment (and a BIP), not just as a conditional service. If the intent is to retain this protocol indefinitely, exposing it conditionally, then a service bit would make sense, but it remains a protocol change.\n\nBIP61 is explicit:\n\n“All implementations of the P2P protocol version 70,002 and later should support the reject message.“\n\ne\n\n\u003e On Oct 17, 2019, at 12:54, Andreas Schildbach via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \n\u003e On 16/10/2019 18.43, John Newbery via bitcoin-dev wrote:\n\u003e \n\u003e\u003e Following discussion on this mailing list, support for BIP 61 REJECT\n\u003e\u003e messages was not removed from Bitcoin Core in V0.19. The behaviour in\n\u003e\u003e that upcoming release is that REJECT messages are disabled by default\n\u003e\u003e and can be enabled using the `-enablebip61` command line option.\n\u003e \n\u003e Is there a NODE_* bit we can use to pick peers that support this\n\u003e (useful!) feature?\n\u003e \n\u003e \n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev", "sig": "0813910275653f56a0ddcb6496a247cee9b21668514fffc4dd39ec2538d0ecf266efd31970c261feb66bed9811ad1fe706a34c2bb74c21569342c975de73eabc" }