From: Mark Friedenbach <mark@friedenbach•org>
To: Ilan Oh <ilansky.sharkson@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Blockchain Voluntary Fork (Split) Proposal (Chaofan Li)
Date: Mon, 22 Jan 2018 11:59:39 -0800 [thread overview]
Message-ID: <091F89E0-FBA0-42F9-9166-CF121A84319F@friedenbach.org> (raw)
In-Reply-To: <CALTsm7irVCPE0_JE28NviEUdvVoE1bVcQ37w13VX2bKKb_RnVg@mail.gmail.com>
> On Jan 22, 2018, at 11:01 AM, Ilan Oh via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> The chain with the most mining power will tend to have more value.
I believe you have the causality on that backwards. The tokens which are worth more value will attract more mining hash rate. Miners respond to cash-out value, they don’t set it.
next prev parent reply other threads:[~2018-01-22 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALTsm7iyJjQa5rkddZj2jL_BTdGxH+6Xz78Rt0wOqW1OveecHw@mail.gmail.com>
[not found] ` <CALTsm7gQC8RejAhmobzejEoU4T7xLf77Ykk2m0p=Z2=oM2p0Uw@mail.gmail.com>
2018-01-22 19:01 ` Ilan Oh
2018-01-22 19:59 ` Mark Friedenbach [this message]
2018-01-22 22:52 ` Eric Voskuil
2018-01-23 0:38 Chaofan Li
2018-01-23 4:57 ` Eric Voskuil
2018-01-23 5:47 ` Chaofan Li
2018-01-30 5:32 ` ZmnSCPxj
2018-01-30 6:20 ` Chaofan Li
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=091F89E0-FBA0-42F9-9166-CF121A84319F@friedenbach.org \
--to=mark@friedenbach$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=ilansky.sharkson@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