From: Anthony Towns <aj@erisian•com.au>
To: Peter Todd <pete@petertodd•org>, bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Segwit Upgrade Procedures & Block Extension Data
Date: Sun, 31 Jan 2016 01:48:57 +1000 [thread overview]
Message-ID: <20160130154857.GA13217@sapphire.erisian.com.au> (raw)
In-Reply-To: <20160130153226.GA9757@sapphire.erisian.com.au>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
On Sun, Jan 31, 2016 at 01:32:26AM +1000, Anthony Towns via bitcoin-dev wrote:
> On Thu, Jan 28, 2016 at 01:51:24PM -0500, Peter Todd via bitcoin-dev wrote:
> > While Pieter Wuille's segwit branch(1) doesn't yet implement a fix for
> > the above problem, the obvious thing to do is to add a new service bit
> > such as NODE_SEGWIT, and/or bump the protocol version, and for outgoing
> > peers only connect to peers with segwit support.
> If I'm following the code right, the segwit branch has a fHaveWitness
> flag for each connection, which is set when a HAVEWITNESS message comes
> from the peer, and HAVEWITNESS is sent as part of handshaking. BIP144
> suggests maybe this should be changed to a service bit though:
Oh, there's a PR to change this to a NODE_WITNESS service bit:
https://github.com/sipa/bitcoin/pull/55
Cheers,
aj
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-01-30 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 18:51 Peter Todd
2016-01-30 15:32 ` Anthony Towns
2016-01-30 15:48 ` Anthony Towns [this message]
2016-02-01 16:55 ` Pieter Wuille
2016-02-01 19:29 ` Tier Nolan
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=20160130154857.GA13217@sapphire.erisian.com.au \
--to=aj@erisian$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=pete@petertodd$(echo .)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