From: kjj <bitcoin-devel@jerviss•org>
To: Ryan Carboni <ryan.jc.pc@gmail•com>,
bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin-development Digest, Vol 31, Issue 25
Date: Tue, 10 Dec 2013 07:18:52 -0600 [thread overview]
Message-ID: <52A714BC.1010909@jerviss.org> (raw)
In-Reply-To: <CAO7N=i0=esXrwDJ-NNqXbhSNMPASk4mpjMmxOJsOmouWp84ZiA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
Ryan Carboni wrote:
> And the economic parameters of bitcoin are not fixed in stone. If
> there needs to be a change, it will be messy but it could happen.
Need is an awfully big word. One thing we are certain of is that some
guy telling us all that we are wrong is nowhere near the "need" level.
> Besides, using Austrian precepts of inflation blurs the fact that
> deflation will still be possible under my proposal. Although amusingly
> enough Austrian-defined inflation is still occurring within Bitcoin,
> in fact faster then desired since blocks are being processed every
> seven minutes now as opposed to ten, and it's quite likely when 28nm
> ASIC miners are released that blocks will be processed every five
> minutes before the difficulty is adjusted again.
Don't take this the wrong way, but things like this make it very hard
for us to take you seriously.
Please read up on how the system works, then read up on why we reject
the argument from authority, then if you still have something to say,
please do so in a proper venue. One option for this discussion is the
bitcointalk.org forums, where you will find literally dozens of threads
proposing the exact same thing you are proposing.
This mailing list is NOT for political discussion.
[-- Attachment #2: Type: text/html, Size: 2136 bytes --]
prev parent reply other threads:[~2013-12-10 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.365464.1386663560.21953.bitcoin-development@lists.sourceforge.net>
2013-12-10 9:55 ` Ryan Carboni
2013-12-10 13:18 ` kjj [this message]
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=52A714BC.1010909@jerviss.org \
--to=bitcoin-devel@jerviss$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=ryan.jc.pc@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