From: shaolinfry <shaolinfry@protonmail•ch>
To: David Vorick <david.vorick@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Flag day activation of segwit
Date: Sun, 12 Mar 2017 17:04:11 -0400 [thread overview]
Message-ID: <5Rk8BbFuXS3TJ_fFvB8AmCLj41UZYEUz4CwxSJGc_sn52KwX20ri6MOEqq4sp7PImiaFdiFtWRGgUEHtoGuKEi3RIWI7j-wTXm0-ztTeH0k=@protonmail.ch> (raw)
In-Reply-To: <CAFVRnyqkJa1a9v-iC2GTyo+Qp5izwEVtUOHe6UENgfA0Fv0gfw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Before setting a flag day, I think we should get written cooperation agreements from the largest economic players in Bitcoin. This would include:
There isn't a flag day to set. If the major economic organs like exchanges run the BIP, non-signalling miners simply wont get paid (starting October 1st) and their blocks will be rejected. Miners will have the choice to signal, or find something else profitable to mine. In turn, this will trigger the existing segwit deployment for everyone who has already upgraded to segwit compatible node software (currently Bitcoin Core 0.13.1, 0.13.2, 0.14.0, Bitcoin Knots 0.13.1+, and bcoin) regardless of whether they run this BIP or not.
But yes, it goes without saying that this BIP would need to have buy-in from major economic organs, especially fiat egress points, before being deployed. Failing that, a second deployment of segwit with a flag day, or preferably using the bip-uaversionbits-strong BIP9/flagday hybrid would be required.
[-- Attachment #2: Type: text/html, Size: 1168 bytes --]
next prev parent reply other threads:[~2017-03-12 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 15:50 shaolinfry
2017-03-12 17:20 ` David Vorick
2017-03-12 21:04 ` shaolinfry [this message]
2017-03-13 3:01 ` Luke Dashjr
2017-03-13 10:36 ` shaolinfry
2017-03-13 22:18 ` Nick ODell
2017-03-26 11:08 ` praxeology_guy
2017-03-13 4:59 ` Nick ODell
2017-03-13 10:35 ` David Vorick
2017-03-13 10:54 ` shaolinfry
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='5Rk8BbFuXS3TJ_fFvB8AmCLj41UZYEUz4CwxSJGc_sn52KwX20ri6MOEqq4sp7PImiaFdiFtWRGgUEHtoGuKEi3RIWI7j-wTXm0-ztTeH0k=@protonmail.ch' \
--to=shaolinfry@protonmail$(echo .)ch \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=david.vorick@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