From: "Rebroad (sourceforge)" <rebroad+sourceforge.net@gmail•com>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] block difficulty - inherently stable or inherently unstable?
Date: Tue, 8 May 2012 15:02:58 +0100 [thread overview]
Message-ID: <CAFBxzABj90QLxsO6aywzPvFmV=Pk91hiDCXc5-xk-3B9ePEVAQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
I was just thinking about the way block difficulty is calculated, and how
people may (in future) decide whether to mine or not.
Is it possible that when the difficulty is low, many will decide to mine,
producing blocks every 3 or 5 minutes, and then in 1 week, bitcoin will
increase the difficulty, and many will decide it is no longer cost
effective, stop mining, and find blocks are being produced every 30 minutes
for the next 6 weeks, before the returning to a previous difficulty where
people decide to mine again, etc, etc.
Seems reasonably possible in my mind, and I'm wondering if the stability so
far has been purely due to people mining without thinking too much about
the immediate cost-effectiveness (or mining by zombie-farms).
Thoughts, anyone?
Ed
[-- Attachment #2: Type: text/html, Size: 871 bytes --]
reply other threads:[~2012-05-08 14:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAFBxzABj90QLxsO6aywzPvFmV=Pk91hiDCXc5-xk-3B9ePEVAQ@mail.gmail.com' \
--to=rebroad+sourceforge.net@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