public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Ferdinando M. Ametrano" <ferdinando.ametrano@gmail•com>
To: Neil <kyuupichan@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: death by halving
Date: Tue, 28 Oct 2014 22:44:50 +0100	[thread overview]
Message-ID: <CADfmNEke=i+WWfJH0d5e7x5mbvGVuujK-LDke=6PRR_d_Vuhig@mail.gmail.com> (raw)
In-Reply-To: <CAPf5XX6aDGpNxNorbU_JddwpDhnCdX7z=8MskagorC9qUL+T=Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 760 bytes --]

On Tue, Oct 28, 2014 at 10:34 PM, Neil <kyuupichan@gmail•com> wrote:

> Economically a halving is almost the same as a halving in price (as fees
> take up more of the pie, less so).
>
> Coincidentally the price has halved since early July to mid-October, and
> we've not even seen difficulty fall yet.
>
because mining profits are many times operational costs. This might change
because of competition, in that case halving in price will become
problematic.

It amazes me that basic economic considerations seems completely lost here,
especially when it comes to mining. We should have learned the lesson of
how a small error in the incentive structure has lead from "one CPU, one
vote" to an oligopoly which might easily become a monopoly in the near
future.

[-- Attachment #2: Type: text/html, Size: 1100 bytes --]

  reply	other threads:[~2014-10-28 21:45 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
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 [this message]
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='CADfmNEke=i+WWfJH0d5e7x5mbvGVuujK-LDke=6PRR_d_Vuhig@mail.gmail.com' \
    --to=ferdinando.ametrano@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=kyuupichan@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