From: Mark Friedenbach <mark@friedenbach•org>
To: Tom Zander <tomz@freedommail•ch>, bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP148 temporary service bit (1 << 27)
Date: Mon, 19 Jun 2017 13:24:25 -0700 [thread overview]
Message-ID: <DAC56472-EF04-45FF-887B-2481B259E662@friedenbach.org> (raw)
In-Reply-To: <3654399.ZkJ0Jlgova@cherry>
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@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@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
prev parent reply other threads:[~2017-06-19 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 19:26 Luke Dashjr
2017-06-19 19:46 ` Tom Zander
2017-06-19 20:24 ` Mark Friedenbach [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DAC56472-EF04-45FF-887B-2481B259E662@friedenbach.org \
--to=mark@friedenbach$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=tomz@freedommail$(echo .)ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox