public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Erik Aronesty <erik@q32.com>
To: Luke Dashjr <luke@dashjr.org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] I do not support the BIP 148 UASF
Date: Tue, 2 May 2017 12:54:35 -0400	[thread overview]
Message-ID: <CAJowKg+zdXgeBAmY4WhW-P3WWfqze7G+B3AAwxxVtKeTsoB81g@mail.gmail.com> (raw)
In-Reply-To: <201704251846.10793.luke@dashjr.org>

[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]

If the flag day for a wtxid commitment is timed before the current segwit
period end, I suspect segwit would activate within the current period.

On Tue, Apr 25, 2017 at 2:46 PM, Luke Dashjr via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> On Tuesday 25 April 2017 6:28:14 PM Gregory Maxwell via bitcoin-dev wrote:
> > > https://github.com/bitcoin/bitcoin/compare/master...
> shaolinfry:uasegwit-f
> > > lagday
> > >
> > > I believe this approach would satisfy the more measured approach
> expected
> > > for Bitcoin and does not have the issues you brought up about BIP148.
> >
> > I have not reviewed it carefully yet, but I agree that it addresses my
> > main concern!  I think this is a much better approach. Thanks.
>
> FWIW, I disagree in this case. I think given the circumstances, if we are
> going to do a UASF for segwit at all, we need a clearly decisive outcome,
> which is given by BIP 148. Using the approach in BIP 8 makes sense in many
> cases, but in this case, it is liable to simply create a prolonged
> uncertainty
> where nobody knows the outcome when segwit's rules are challenged by a
> malicious miner.
>
> If BIP 148 fails to achieve widespread support, we could do a BIP 8-based
> UASF
> with Segwit v2 (along with some other changes I suggested in the other
> thread), but I think the tradeoffs right now favour BIP 148 as the best
> UASF
> deployment.
>
> Luke
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 2444 bytes --]

  reply	other threads:[~2017-05-02 16:54 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14  7:56 [bitcoin-dev] I do not support the BIP 148 UASF Gregory Maxwell
2017-04-14 16:50 ` praxeology_guy
2017-04-14 17:36   ` Chris Stewart
2017-04-14 18:33     ` praxeology_guy
2017-04-14 19:12   ` Tom Zander
2017-04-14 19:20 ` Tom Zander
2017-04-14 19:33   ` James Hilliard
2017-04-14 20:34     ` Tom Zander
2017-04-14 20:51       ` James Hilliard
2017-04-14 20:58         ` Tom Zander
2017-04-14 21:10           ` James Hilliard
2017-04-14 21:12             ` Gregory Maxwell
2017-04-14 20:59       ` Gregory Maxwell
2017-04-15  2:01 ` Steven Pine
2017-04-15  3:05   ` Chris Stewart
2017-04-15  3:29   ` Gregory Maxwell
2017-04-15  4:10     ` Steven Pine
2017-04-15  4:47       ` Gregory Maxwell
2017-04-15  6:28 ` Cameron Garnham
2017-04-15  7:04   ` Gregory Maxwell
2017-04-15  7:46     ` Chris Acheson
2017-04-15 13:23       ` Natanael
2017-04-15 13:54         ` Greg Sanders
2017-04-15  8:05     ` Cameron Garnham
2017-04-20 18:39 ` shaolinfry
2017-04-25 18:28   ` Gregory Maxwell
2017-04-25 18:46     ` Luke Dashjr
2017-05-02 16:54       ` Erik Aronesty [this message]
2017-05-22 19:23 ` Suhas Daftuar
2017-05-23  4:03   ` Steven Pine
2017-05-23  6:30     ` Karl Johan Alm
2017-05-23 12:55       ` Luke Dashjr
2017-05-23 13:20         ` Jorge Timón
2017-05-23  9:47     ` Hampus Sjöberg
2017-04-14 10:52 Chris Acheson
2017-04-15 13:42 Mark Friedenbach
2017-04-15 14:54 ` Ryan Grant
2017-04-15 18:50 ` Gregory Maxwell
2017-04-19 16:17   ` Erik Aronesty
2017-04-20 14:23     ` Alphonse Pace
2017-04-20 15:48       ` Erik Aronesty

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=CAJowKg+zdXgeBAmY4WhW-P3WWfqze7G+B3AAwxxVtKeTsoB81g@mail.gmail.com \
    --to=erik@q32.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=luke@dashjr.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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