public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail•com>
To: Zooko Wilcox-OHearn <zooko@leastauthority•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] (no subject)
Date: Sat, 25 May 2013 10:09:11 +0200	[thread overview]
Message-ID: <CA+s+GJD0xoudWUiko4epSXYz+ytU0SvrdAKR-sAnh89rUhKLkw@mail.gmail.com> (raw)
In-Reply-To: <CAM_a8Jwo_7NJJoaKYUYo6T7U8AsDfT5=MZSXjmdYU4330OHNmw@mail.gmail.com>

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

On Sat, May 25, 2013 at 7:46 AM, Zooko Wilcox-OHearn <
zooko@leastauthority•com> wrote:

> jgarzik wrote:
>  > 1) Rule changes.  We don't want these.
>
> In general? What constitutes a rule change?
>

I'm sure he means rule changes with economical impact, such as miner block
reward, total number of bitcoins, block speed. Mostly non-interesting from
a technical view point, but the only changes most altcoins seem to be
making... In any case, these are set in stone and cannot ever be changed
for bitcoin or all hell will break loose.

See also https://en.bitcoin.it/wiki/Hardfork_Wishlist.

Wladimir

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

  reply	other threads:[~2013-05-25  8:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25  5:46 Zooko Wilcox-OHearn
2013-05-25  8:09 ` Wladimir [this message]
2013-05-27  2:43   ` [Bitcoin-development] Handling alerts & communication on bitcoin.org Saïvann
2013-05-25  8:25 ` [Bitcoin-development] (no subject) Melvin Carvalho
2013-05-25  8:53   ` Luke-Jr
2013-05-25  9:23     ` Melvin Carvalho
2014-05-04  1:47 losewife

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=CA+s+GJD0xoudWUiko4epSXYz+ytU0SvrdAKR-sAnh89rUhKLkw@mail.gmail.com \
    --to=laanwj@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=zooko@leastauthority$(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