From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] BIP148 temporary service bit (1 << 27)
Date: Mon, 19 Jun 2017 19:26:22 +0000 [thread overview]
Message-ID: <201706191926.25006.luke@dashjr.org> (raw)
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.
Luke
next reply other threads:[~2017-06-19 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 19:26 Luke Dashjr [this message]
2017-06-19 19:46 ` Tom Zander
2017-06-19 20:24 ` Mark Friedenbach
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=201706191926.25006.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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