From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UFlEd-0002TO-8Q for bitcoin-development@lists.sourceforge.net; Wed, 13 Mar 2013 12:56:47 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1UFlEa-0005SJ-7r for bitcoin-development@lists.sourceforge.net; Wed, 13 Mar 2013 12:56:46 +0000 Received: from ishibashi.localnet (unknown [173.170.142.26]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id A1D6527A2968 for ; Wed, 13 Mar 2013 12:56:36 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Wed, 13 Mar 2013 12:56:29 +0000 User-Agent: KMail/1.13.7 (Linux/3.7.3-gentoo; KDE/4.9.5; x86_64; ; ) X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201303131256.30144.luke@dashjr.org> X-Spam-Score: -2.4 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -2.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1UFlEa-0005SJ-7r Subject: [Bitcoin-development] 0.8.1 ideas X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 12:56:47 -0000 Here's a simple proposal to start discussion from... BEFORE block 262144: - Never make a block that, combined with the previous 4 blocks, results in over 4500 transaction modifications. - Reject any block that includes more than 4500 transaction modifications on its own (slight soft-fork) - (these rules should make older clients safe under most circumstances) FROM block 262144 to block 393216 (hard fork #1): - Never make, and reject any block that includes more than 24391 transaction modifications on its own (this *should* be equivalent to 1 MB) - (this rules can make older client backports safe unless a reorg is more than 6 blocks deep) FROM block 393216 onward (hard fork #2): - Never make, and reject any block that includes more than 48781 transaction modifications on its own (this *should* be equivalent to 2 MB) - Accept blocks up to 2 MB in data size - Discontinue support for clients prior to 0.8.1 I intentionally set the block numbers conservatively to try to account for the yet-unseen ASIC upgrade. Thoughts?