[Bitcoin-segwit2x] SegWit2x Hard Fork Testing Update

Jeff Garzik jeff at bloq.com
Wed Jul 12 15:26:10 UTC 2017


For tracking and discussion purposes, this was filed by James H at
https://github.com/btc1/bitcoin/pull/46

tl;dr   It appears to introduce compatibility risk with deployed,
in-the-field wallets.



On Wed, Jul 12, 2017 at 11:23 AM, Peter Todd via Bitcoin-segwit2x <
bitcoin-segwit2x at lists.linuxfoundation.org> wrote:

> On Wed, Jul 12, 2017 at 10:43:35AM -0400, Charlie Shrem via
> Bitcoin-segwit2x wrote:
> > The first block after the hard fork occurs is required (by design) to be
> > larger than 1MB.  Because there aren’t very many transactions on testnet,
> > this stalled out block creation until 1MB of transactions could
> accumulate.
>
> I'd appreciate an official explanation of why the nVersion hard-fork bit
> wasn't
> used for this functionality. That's a far simpler mechanism, more
> reliable, and
> it serves the important purpose of allowin lite clients to detect what
> chain
> they're on.
>
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
>
> _______________________________________________
> Bitcoin-segwit2x mailing list
> Bitcoin-segwit2x at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x
>
>


-- 
Jeff Garzik
CEO and Co Founder
Bloq, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/attachments/20170712/021b5e14/attachment.html>


More information about the Bitcoin-segwit2x mailing list