From: praxeology_guy <praxeology_guy@protonmail.com>
To: Gregory Maxwell <greg@xiph.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] I do not support the BIP 148 UASF
Date: Fri, 14 Apr 2017 12:50:47 -0400 [thread overview]
Message-ID: <6Q-8gcti6Iml_nMKLlBIiS2WTVYxtRB30yRz0UqAe4-OmryaZCTYr0IrIl3RjFN3X6Yd_D_eWyXSN1ZNjq1l3dq5oXbYRmZfn1C1IvJ8FJc=@protonmail.com> (raw)
In-Reply-To: <CAAS2fgRdSOu8N6L3+fBpnye+rM+W6+F=cePy=9oL4tJuCj=Jsw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
Gregory Maxwell,
Criticizing 148 without suggesting a specific alternative leaves the community in disarray.
I know you are emphasizing patience. But at the same time, with your patience we are allowing ourselves to get dicked for longer than necessary.
I think that core could easily develop code that could create a solid/reliable date/height based activation to allow miners to create SegWit block candidates and having nodes fully verify them. Shaolinfry is the only person Ive seen actually make such a proposal: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/014049.html. His makes it so that SegWit default gets activated at the end of the BIP9 signalling timeframe instead of default leaving it non-activated.
I agree that 148 is is not ideal. Non-SegWit signaling blocks are not a Denial of Service, given that other activation methods are available. Someone just needs to code something up that is better that we can all use in a satisfying time frame. So far 148 is the most practical and reliable method I'm aware of.
If 148 causes orphaning and a fork, I don't think such really matters in the long term. The non-SegWit miners will probably just quickly give up their orphans once they realize that money users like being able to have non-mutable TX IDs. If they do create a long lasting branch... well that is good too, I'd be happy to no longer have them in our community. Good luck to them in creating a competitive money, so that we can all enjoy lower transaction fees.
SegWit has already undergone enough testing. It is time to activate it.
Cheers,
Praxeology Guy
[-- Attachment #2: Type: text/html, Size: 1988 bytes --]
next prev parent reply other threads:[~2017-04-14 16:50 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 [this message]
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
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='6Q-8gcti6Iml_nMKLlBIiS2WTVYxtRB30yRz0UqAe4-OmryaZCTYr0IrIl3RjFN3X6Yd_D_eWyXSN1ZNjq1l3dq5oXbYRmZfn1C1IvJ8FJc=@protonmail.com' \
--to=praxeology_guy@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=greg@xiph.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