From: David Vorick <david.vorick@gmail•com>
To: shaolinfry@protonmail•ch,
Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Flag day activation of segwit
Date: Sun, 12 Mar 2017 13:20:15 -0400 [thread overview]
Message-ID: <CAFVRnyqkJa1a9v-iC2GTyo+Qp5izwEVtUOHe6UENgfA0Fv0gfw@mail.gmail.com> (raw)
In-Reply-To: <OUzy7vvSKdJW7OCcCNCbaVDT-hJcf7Fy3fxEi_z6AmBC3VY0dGZpSBOGxRs-fVE-CfOVToCjjwB-meqejkb4VXYAGu0HHPTzNFhomEhgVpk=@protonmail.ch>
[-- Attachment #1: Type: text/plain, Size: 2226 bytes --]
It has taken almost 6 months for SegWit adoption to get to where it is
today. I don't think it will take that long to reach similar adoption for
UASF SegWit, but conservatively we want to give it at least that much time.
It's really important to stress here that a UASF will split and become the
minority chain if a majority of the transaction accepting nodes on the
network do not agree to strictly follow the UASF and outright reject blocks
that do not signal for SegWit at the designated date.
Before setting a flag day, I think we should get written cooperation
agreements from the largest economic players in Bitcoin. This would include:
Bitfinex
Bitflyer
BitGo
BitPay
Bitstamp
Blockchain.info
Blockcypher
Coinbase
Huobi
Kraken
Gemeni
OkCoin
Poloniex
(feel free to discuss this list)
100% cooperation is not necessary, but close to 100% cooperation is
strongly desired. It should be noted that their cooperation is only
required because they are sufficiently powerful to threaten the success of
a UASF, particularly because many of these entities hold users bitcoins.
Once a convincing majority is on-board, I suggest we release a UASF patch
that activates a full year after release. This is because a UASF is a big
gamble that requires a large majority of the economy has upgraded.
Though that is a very long time, SegWit can always be activated early with
miner cooperation.
------
As an extra note, if the UASF triggers with majority economy support and
the miners resist, a minority block reward chain may be the longest chain
for a while. However, when the majority block reward chain does catch up,
the minority reward chain will be entirely obliterated, eliminating all
block rewards, all transaction history, and making a ton of money vanish
all at once.
This makes it very dangerous for an exchange, payment processor, online
wallet, or miner to oppose the UASF if there is significant momentum behind
it. This gives the UASF a powerful snowball effect once a few major parties
(or the majority of tiny full nodes) have decided to commit to the UASF.
On the other hand, failure means a permanent coin split, so it is still
necessary to exercise caution that exceeds the caution of a normal soft
fork.
[-- Attachment #2: Type: text/html, Size: 3737 bytes --]
next prev parent reply other threads:[~2017-03-12 17:20 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 [this message]
2017-03-12 21:04 ` shaolinfry
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=CAFVRnyqkJa1a9v-iC2GTyo+Qp5izwEVtUOHe6UENgfA0Fv0gfw@mail.gmail.com \
--to=david.vorick@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=shaolinfry@protonmail$(echo .)ch \
/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