From: Alex Mizrahi <alex.mizrahi@gmail•com>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] death by halving
Date: Sat, 25 Oct 2014 22:53:57 +0300 [thread overview]
Message-ID: <CAE28kUS5otH3q6BPETANw6PaDCrrs1+Sm+LMNnv_TK-viGRFLQ@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T1RPkif1+DEsOLrFfr-sE=FCs_B5C5aZzKr6HZCHw15ag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
> We had a halving, and it was a non-event.
> Is there some reason to believe next time will be different?
>
Yes.
When the market is rapidly growing, margins can be relatively high because
of limited amounts of capital being invested, or introduction of more
efficient technologies.
However, we should expect market to become more mature with time, and a
mature market will result in lower margins.
The halving can do much more damage when margins are relatively small.
Besides that, there is a difference in ecosystem maturity:
1. Back in 2012, miners weren't so focused on profits, as Bitcoin was
highly experimental: some were mining for the hell of it (it was a novelty
thing back then), others wanted to secure the network, others did it
because it was hard to obtain bitcoins by other means. But now miners are
mostly profit-motivated: they buy expensive dedicated mining equipment and
want to maximize profits. As you might know, at one point ghash.io reached
50% hashrate, and miners didn't care about it enough to switch to a
different pool.
2. Back in 2012, we didn't have multipools. Multipools automatically
switches between mining different alt-chains to maximize miners' profits.
Miners who use multipools do not care how their hashrate is used as long as
they profit off it.
Particularly, check https://nicehash.com/ -- you can easily buy hashrate to
attack a smaller alt-coin, for example.
If the halving will result in a significant hashrate drop (and we did
observe hashrate drop in 2012, although it wasn't that big), it might be
possible to buy enough hashpower to attack Bitcoin.
[-- Attachment #2: Type: text/html, Size: 2187 bytes --]
next prev parent reply other threads:[~2014-10-25 19:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 18:06 Alex Mizrahi
2014-10-25 18:12 ` Jeff Garzik
2014-10-25 18:22 ` Alex Mizrahi
2014-10-25 18:31 ` Jeff Garzik
2014-10-25 19:08 ` Alex Mizrahi
2014-10-25 19:16 ` Gavin Andresen
2014-10-25 19:53 ` Alex Mizrahi [this message]
2014-10-25 21:50 ` Melvin Carvalho
2014-10-28 20:17 ` Ferdinando M. Ametrano
[not found] ` <CAAS2fgSiz-XRVQ4V+KbrTUWG4=g=WGf8c-pF4b4fFnfyU9HOqQ@mail.gmail.com>
2014-10-28 20:36 ` [Bitcoin-development] Fwd: " Gregory Maxwell
2014-10-28 20:57 ` Alex Mizrahi
2014-10-28 21:19 ` Jérémie Dubois-Lacoste
2014-10-28 21:43 ` Gregory Maxwell
2014-10-28 22:43 ` Ferdinando M. Ametrano
2014-10-29 14:34 ` [Bitcoin-development] Death by halving (pro-active proposals) Sergio Lerner
2014-10-29 17:25 ` Jeff Garzik
2014-10-28 21:23 ` [Bitcoin-development] Fwd: death by halving Ferdinando M. Ametrano
2014-10-28 21:34 ` Neil
2014-10-28 21:44 ` Ferdinando M. Ametrano
2014-10-28 22:00 ` Thomas Zander
2014-10-28 22:38 ` Ferdinando M. Ametrano
2014-10-28 21:57 ` Christophe Biocca
2014-10-25 20:27 ` [Bitcoin-development] " Adam Back
2014-10-25 20:43 ` Thomas Zander
2014-10-25 20:28 ` Thomas Zander
2014-10-25 20:49 ` Alex Mizrahi
2014-10-25 21:51 ` Alexander Leishman
2014-10-25 22:10 ` Ross Nicoll
2014-10-25 22:42 ` Melvin Carvalho
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=CAE28kUS5otH3q6BPETANw6PaDCrrs1+Sm+LMNnv_TK-viGRFLQ@mail.gmail.com \
--to=alex.mizrahi@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@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