From: Tier Nolan <tier.nolan@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin is an experiment. Why don't we have an experimental hardfork?
Date: Wed, 19 Aug 2015 16:48:23 +0100 [thread overview]
Message-ID: <CAE-z3OUwm2823NN9qxC3vEqosPStuqka-bxf4JXUPgykMJO-QA@mail.gmail.com> (raw)
In-Reply-To: <46e6bf2dbd8e08745f1c0dbd9f62bc7d@xbt.hk>
[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]
On Wed, Aug 19, 2015 at 4:22 PM, jl2012 via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Will the adoption of BitcoinXT lead by miners? No, it won't. Actually,
> Chinese miners who control 60% of the network has already said that they
> would not adopt XT. So they must not be the leader in this revolution.
> Again, miners need to make sure they could sell their bitcoin in a good
> price, and that's not possible without support of exchanges and investors.
>
So, the exchanges get together to "encourage" the miners to start running
bitcoin-XT. What would they do?
One scheme would be to create a taint system. All non-XT coinbases outputs
are marked as tainted. All outputs are tainted if any of the inputs into a
transaction are tainted. Tainted coins can only be un-tainted by sending
0.5% of their value to the public address of one of the participating
exchanges (or to OP_RETURN). They could slowly ratchet up the surcharge.
Exchanges in the cartel agree not to exchange tainted coins. Even if some
still do, the tainted coins are still inherently less valuable, since fewer
exchanges accept them.
Schemes like that are the main way for non-miners to flex their muscles,
even if they seem unsavory.
Taint tracking would allow merchants to participate. They could give less
credit for tainted bitcoins, even if the exchanges are trying to remain
neutral. If that happens, the exchanges could run 2 prices, BTC and
BTC-tainted.
On the other hand, implementing taint machinery is a bad thing for
fungibility.
It can also be accomplished with checkpointing. They need to create 1 big
block and then agree to checkpoint it.
A less strict rule rule could be that blocks after the first big block
count as double POW. That means that the big block chain only needs 34% of
the hashing power to win.
[-- Attachment #2: Type: text/html, Size: 2330 bytes --]
next prev parent reply other threads:[~2015-08-19 15:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 9:54 jl2012
2015-08-18 11:57 ` Micha Bailey
2015-08-18 18:52 ` Eric Lombrozo
2015-08-18 20:48 ` Danny Thorpe
2015-08-18 20:51 ` Eric Lombrozo
2015-08-18 21:06 ` Danny Thorpe
2015-08-18 21:17 ` Eric Lombrozo
2015-08-18 21:39 ` Danny Thorpe
2015-08-19 9:29 ` Jorge Timón
2015-08-19 10:14 ` odinn
2015-08-19 11:06 ` Jorge Timón
2015-08-19 11:25 ` odinn
2015-08-19 15:22 ` jl2012
2015-08-19 15:48 ` Tier Nolan [this message]
2015-08-19 15:25 ` Jorge Timón
2015-08-19 17:30 ` Danny Thorpe
2015-08-19 18:33 ` Jorge Timón
2015-08-18 22:51 ` Ahmed Zsales
2015-08-19 2:53 ` Eric Lombrozo
2015-08-19 9:24 ` Jorge Timón
2015-08-19 10:34 ` jl2012
2015-08-19 10:53 ` Jorge Timón
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=CAE-z3OUwm2823NN9qxC3vEqosPStuqka-bxf4JXUPgykMJO-QA@mail.gmail.com \
--to=tier.nolan@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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