📅 Original date posted:2017-06-19 📝 Original message:It is essential that ...

Mark Friedenbach [ARCHIVE] /

npub1r3s…8d0u

2023-06-07 18:03:25

in reply to nevent1q…e2q7

📅 Original date posted:2017-06-19
📝 Original message:It is essential that BIP-148 nodes connect to at least two other BIP-148 nodes to prevent a network partition in August 1st. The temporary service but is how such nodes are able to detect each other.

> On Jun 19, 2017, at 12:46 PM, Tom Zander via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>
>> On Monday, 19 June 2017 21:26:22 CEST Luke Dashjr via bitcoin-dev wrote:
>> To ease the transition to BIP148 and to minimise risks in the event miners
>> choose to perform a chain split attack, at least Bitcoin Knots will be
>> using the temporary service bit (1 << 27) to indicate BIP148 support.
>>
>> Once the transition is complete, this will no longer be necessary, and the
>> bit will be (manually) returned for reuse.
>>
>> I encourage other software implementing BIP148 (both full and light nodes)
>> to set and use this service bit to avoid network partitioning risks.
>
> I'm curious what you action on the finding (or not) of a peer with this bit
> set (or not).
> Can you link to the github commit where you implemented this?
> --
> Tom Zander
> Blog: https://zander.github.io
> Vlog: https://vimeo.com/channels/tomscryptochannel
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Author Public Key

npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0u

Seen on

wss://relay.nostr.band

Show more details

Published at

2023-06-07 18:03:25

Kind type

1 Short Text Note

Event JSON

{ "id": "c8f61200b5501554a271451cf0c1e2f02a0a3f2ad4321cabd50cdaadf3919783", "pubkey": "1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069", "created_at": 1686161005, "kind": 1, "tags": [ [ "e", "ac53361ae82de7e96b054c0bfbfabef0c8bd3e552c4b50dc715d26b4d2e2114a", "", "root" ], [ "e", "9838f701a3a7b7cc82e27a1e739a43c21f8acf7a840b2863510381d85f44aeae", "", "reply" ], [ "p", "dcb947d818dbfd7cf0baf26c0d5eb606b5a32336c5483fb53e05146315833ca7" ] ], "content": "📅 Original date posted:2017-06-19\n📝 Original message:It is essential that BIP-148 nodes connect to at least two other BIP-148 nodes to prevent a network partition in August 1st. The temporary service but is how such nodes are able to detect each other.\n\n\u003e On Jun 19, 2017, at 12:46 PM, Tom Zander via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \n\u003e\u003e On Monday, 19 June 2017 21:26:22 CEST Luke Dashjr via bitcoin-dev wrote:\n\u003e\u003e To ease the transition to BIP148 and to minimise risks in the event miners\n\u003e\u003e choose to perform a chain split attack, at least Bitcoin Knots will be\n\u003e\u003e using the temporary service bit (1 \u003c\u003c 27) to indicate BIP148 support.\n\u003e\u003e \n\u003e\u003e Once the transition is complete, this will no longer be necessary, and the\n\u003e\u003e bit will be (manually) returned for reuse.\n\u003e\u003e \n\u003e\u003e I encourage other software implementing BIP148 (both full and light nodes)\n\u003e\u003e to set and use this service bit to avoid network partitioning risks.\n\u003e \n\u003e I'm curious what you action on the finding (or not) of a peer with this bit \n\u003e set (or not).\n\u003e Can you link to the github commit where you implemented this?\n\u003e -- \n\u003e Tom Zander\n\u003e Blog: https://zander.github.io\n\u003e Vlog: https://vimeo.com/channels/tomscryptochannel\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": "e77e7cd56839339a9ac41ae9ea5ad448d76141c38b99422f4bf2ddc75c83387df034e775a128af4feb66160d73c3bf2260e5621859ff22d50ec3798a94251d15" }