From: Gregory Maxwell <gmaxwell@gmail•com>
To: "Jérémie Dubois-Lacoste" <jeremie.dl@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: death by halving
Date: Tue, 28 Oct 2014 21:43:42 +0000 [thread overview]
Message-ID: <CAAS2fgR4-V10i2D=v5-ZR9rWYcBjPKyRgGvgnG3JAmPKr4x19Q@mail.gmail.com> (raw)
In-Reply-To: <CAJqsvLCG2Cv=7wzDLotunEUTnAvdxVLSGrMEtkAnmdoBgONBsg@mail.gmail.com>
On Tue, Oct 28, 2014 at 9:19 PM, Jérémie Dubois-Lacoste
<jeremie.dl@gmail•com> wrote:
> The fact that a topic was brought up many times since a long time,
> does not mean it is not relevant.
I am not saying that it is "not relevant", I'm saying the discussion
is pointless:
No new information has arrived since the very first times that this
has been discussed except
that the first halving passed without incident.
If people were not sufficiently convinced that this was a serious
concern before there was concrete evidence (however small) that it was
okay, then discussion is not likely going to turn out differently the
50th or 100th time it is repeated...
except, perhaps, by wearing out all the most experienced and
knowledgeable among us as we become tired of rehashing the same
discussions over and over again.
On Tue, Oct 28, 2014 at 9:23 PM, Ferdinando M. Ametrano
<ferdinando.ametrano@gmail•com> wrote:
[snip]
> As of now the cost per block is probably already about 100USD, probably in
> the 50-150USD.
This is wildly at odds with reality. I don't mean to insult, but
please understand that every post you make here consumes the time of
dozens (or, hopefully, hundreds) of people. Every minute you spend
refining your post has a potential return of many minutes for the rest
of the users of the list.
At current difficulty, with a SP30 (one of the
leading-in-power-efficiency) marginal break-even is ~1144.8852 * $/kwh
== $/btc.
At $0.10/kwh each block has an expected cost right now, discounting
all one time hardware costs, close to $3000.
next prev parent reply other threads:[~2014-10-28 21:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 18:06 [Bitcoin-development] " 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 [this message]
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='CAAS2fgR4-V10i2D=v5-ZR9rWYcBjPKyRgGvgnG3JAmPKr4x19Q@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jeremie.dl@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