From: Alex Mizrahi <alex.mizrahi@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] death by halving
Date: Sat, 25 Oct 2014 23:49:54 +0300 [thread overview]
Message-ID: <CAE28kUT-Ywo=de94HVJCmLJhWnf_=v5Vo=M9pjed-YhEAu5Sjw@mail.gmail.com> (raw)
In-Reply-To: <2109053.EM3JWxoz5A@coldstorage>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
> For the sake of argument, lets assume that somehow (quite unlikely)
Why is it unlikely? Do you believe that the cost of electricity cannot be
higher than expected mining revenue?
Or do you expect miners to keep mining when it costs them money?
> half the mining equipment gets shut off.
> The amount of hashes/second is such that it is currently, lets just say,
> quite
> secure against any takeover.
>
The equipment won't be simply turned off, it will be up for grabs.
Please check this web sites:
https://nicehash.com/
https://www.multipool.us/
One can use them in the same way he uses normal mining pools, and they
switch between different chains.
Say, multipool.us can switch between BTC and PPC (Peercoin).
Mining BTC will be less profitable after a halving, so a miner who is
willing to maximize his profits might use multipool to auto-switch to
something more profitable.
Which might be attack-on-Bitcoin.
E.g. if 60% of bitcoin's total hashrate is available via "multipools", one
can try to pull of a double-spending attack.
> Your document makes a long series of assumptions about how this can turn
> out
> bad with each individually is implausible, together are just fiction.
>
It sounds like you failed to grasp even basics.
[-- Attachment #2: Type: text/html, Size: 2236 bytes --]
next prev parent reply other threads:[~2014-10-25 20:50 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
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 [this message]
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='CAE28kUT-Ywo=de94HVJCmLJhWnf_=v5Vo=M9pjed-YhEAu5Sjw@mail.gmail.com' \
--to=alex.mizrahi@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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