public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Benjamin Lindner <ben@benlabs•net>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] 0.8.1 ideas
Date: Fri, 15 Mar 2013 13:06:20 -0400	[thread overview]
Message-ID: <D0FC8006-AF19-4E92-87B4-A4FE356D4577@benlabs.net> (raw)
In-Reply-To: <51411744.6010908@gmail.com>


On Mar 13, 2013, at 8:18 PM, Cameron Garnham <da2ce7@gmail•com> wrote:
> For me, everyone signed up to bitcoin thinking that there was a 1MB /
> block limit.  The lock limits were unexpected, and could be considered
> extremely uncontroversial to remove.

This. Software behavior which is not described by the source code should not be considered an integral part of the rule set.
Any influence of external libraries on the consensus mechanism is unacceptable.


  reply	other threads:[~2013-03-15 17:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 12:56 Luke-Jr
2013-03-13 13:14 ` Gregory Maxwell
2013-03-13 15:05 ` Peter Todd
2013-03-13 15:18   ` Gregory Maxwell
2013-03-13 15:26     ` Luke-Jr
2013-03-13 16:04       ` Peter Todd
2013-03-13 17:41 ` Mark Friedenbach
2013-03-13 17:58   ` Pieter Wuille
2013-03-13 18:27     ` Mark Friedenbach
2013-03-13 18:35       ` slush
2013-03-13 18:38       ` Pieter Wuille
2013-03-13 19:30       ` Gregory Maxwell
     [not found]         ` <16B6728E-4220-4DA6-B740-FA38A7C19CCB@thelibertyportal.com>
2013-03-13 20:24           ` Gregory Maxwell
2013-03-13 20:18       ` Luke-Jr
2013-03-13 18:04   ` Luke-Jr
2013-03-13 21:06 ` Andy Parkins
2013-03-13 21:14   ` Luke-Jr
2013-03-13 21:22     ` Roy Badami
2013-03-13 21:27       ` Gregory Maxwell
2013-03-13 21:36         ` Roy Badami
2013-03-14  0:18           ` Cameron Garnham
2013-03-15 17:06             ` Benjamin Lindner [this message]
2013-03-15 19:23               ` Luke-Jr
2013-03-15 19:52               ` Gregory Maxwell

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=D0FC8006-AF19-4E92-87B4-A4FE356D4577@benlabs.net \
    --to=ben@benlabs$(echo .)net \
    --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