From: Tom Zander <tomz@freedommail•ch>
To: bitcoin-dev@lists•linuxfoundation.org,
Jacob Eliosoff <jacob.eliosoff@gmail•com>
Subject: Re: [bitcoin-dev] Barry Silbert segwit agreement
Date: Fri, 26 May 2017 20:48:32 +0200 [thread overview]
Message-ID: <2134289.AMSES3raTP@strawberry> (raw)
In-Reply-To: <CAAUaCyiHUOQ-rhN5XiGyMc6ocfsNBuH_tzK_QWu7sg1=Qd-o=Q@mail.gmail.com>
On Friday, 26 May 2017 19:47:11 CEST Jacob Eliosoff via bitcoin-dev wrote:
> Forgive me if this is a dumb question.
Sorry for picking your email.
I understand people want something different for the agreement, I know I do
too.
We have a specific agreement on the table, signed by a huge subsection of the
industry.
Maybe the time for changing things is not to be *after* the signatures are
set. I know I’d change some detials. But do we really want to go through
another conference where all the important people are present to agree on a
compromise? Or can we use the one we have?
The compromise is pretty simple;
https://medium.com/@DCGco/bitcoin-scaling-agreement-at-consensus-2017-133521fe9a77
* Activate Segregated Witness at an 80% threshold, signaling at bit 4
* Activate a 2 MB hard fork within six months
--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel
next prev parent reply other threads:[~2017-05-26 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 17:47 Jacob Eliosoff
2017-05-26 18:48 ` Tom Zander [this message]
2017-05-26 20:02 ` Matt Corallo
2017-05-26 20:10 ` Jacob Eliosoff
2017-05-26 21:30 ` James Hilliard
2017-05-26 22:12 ` Tom Zander
[not found] ` <CADvTj4qdr2yGYFEWA7oVmL-KkrchYb5aQBRY9w0OK4ZVopSTSA@mail.gmail.com>
2017-05-28 20:51 ` Tom Zander
2017-05-28 23:28 ` James Hilliard
2017-05-26 22:44 ` Matt Corallo
-- strict thread matches above, loose matches on Subject: below --
2017-05-22 12:29 Daniele Pinna
2017-05-22 6:12 shaolinfry
2017-05-22 6:27 ` Peter Todd
2017-05-22 9:23 ` Hampus Sjöberg
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=2134289.AMSES3raTP@strawberry \
--to=tomz@freedommail$(echo .)ch \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jacob.eliosoff@gmail$(echo .)com \
/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