Satoshi Forum Archive
Thread #0233

[PATCH] increase block size limit

jgarzik2010-10-03T20:13:42Z

We should be able to at least match Paypal's average transaction rate...

Code:

diff --git a/main.h b/main.h
index c5a0127..c92592a 100644
--- a/main.h
+++ b/main.h
@@ -14,7 +14,10 @@ class CBlockIndex;
class CWalletTx;
class CKeyItem;

-static const unsigned int MAX_BLOCK_SIZE = 1000000;
+static const unsigned int TX_PER_MINUTE = 1400;
+static const unsigned int TX_AVG_SIZE_GUESS = 256;
+static const unsigned int MAX_BLOCK_SIZE =
+ TX_PER_MINUTE * TX_AVG_SIZE_GUESS * 10 * 2;
static const unsigned int MAX_BLOCK_SIZE_GEN = MAX_BLOCK_SIZE/2;
static const int MAX_BLOCK_SIGOPS = MAX_BLOCK_SIZE/50;
static const int64 COIN = 100000000;

URL: http://yyz.us/bitcoin/patch.bitcoin-block-sz-limit

Original message

theymos2010-10-03T20:28:39Z

Applying this patch will make you incompatible with other Bitcoin clients.

Original message

satoshi2010-10-03T21:07:28Z

Quote from: theymos on October 03, 2010, 08:28:39 PM (https://bitcointalk.org/index.php?topic=1347.msg15126#msg15126)

Applying this patch will make you incompatible with other Bitcoin clients.

+1 theymos. Don't use this patch, it'll make you incompatible with the network, to your own detriment.
We can phase in a change later if we get closer to needing it.

Original message

jgarzik2010-10-03T21:38:46Z

Quote from: satoshi on October 03, 2010, 09:07:28 PM (https://bitcointalk.org/index.php?topic=1347.msg15139#msg15139)

We can phase in a change later if we get closer to needing it.

IMO it's a marketing thing. It's tough to get people to buy into a system, if the network is technically incapable of supporting high transaction rates.

Original message

FreeMoney2010-10-04T07:39:35Z

Quote from: jgarzik on October 03, 2010, 09:38:46 PM (https://bitcointalk.org/index.php?topic=1347.msg15145#msg15145)

Quote from: satoshi on October 03, 2010, 09:07:28 PM (https://bitcointalk.org/index.php?topic=1347.msg15139#msg15139)

We can phase in a change later if we get closer to needing it.

IMO it's a marketing thing. It's tough to get people to buy into a system, if the network is technically incapable of supporting high transaction rates.

Satoshi just said it can be changed, so technically the network is capable.

Original message

jgarzik2010-10-04T08:10:01Z

Quote from: FreeMoney on October 04, 2010, 07:39:35 AM (https://bitcointalk.org/index.php?topic=1347.msg15207#msg15207)

Quote from: jgarzik on October 03, 2010, 09:38:46 PM (https://bitcointalk.org/index.php?topic=1347.msg15145#msg15145)

Quote from: satoshi on October 03, 2010, 09:07:28 PM (https://bitcointalk.org/index.php?topic=1347.msg15139#msg15139)

We can phase in a change later if we get closer to needing it.

IMO it's a marketing thing. It's tough to get people to buy into a system, if the network is technically incapable of supporting high transaction rates.

Satoshi just said it can be changed, so technically the network is capable.

It is also an incompatible change, as you see.....

Original message

martin2010-10-04T11:50:35Z

No, it's incompatible if just a few people change their behaviour. To roll out a change to the network you need to get most of the clients understanding both the old and the new protocol, and then when you have a majority you turn on the new protocol.

Original message

jgarzik2010-10-04T18:33:55Z

Quote from: martin on October 04, 2010, 11:50:35 AM (https://bitcointalk.org/index.php?topic=1347.msg15268#msg15268)

No, it's incompatible if just a few people change their behaviour. To roll out a change to the network you need to get most of the clients understanding both the old and the new protocol, and then when you have a majority you turn on the new protocol.

You just described a whole-network upgrade. I'd call that an incompatible change ![Smiley](https://bitcointalk.org/static/img/emoticons/smiley.gif)
The effort to raise the transaction rate limit is the same as the effort to change the fundamental nature of bitcoins: convince the vast majority to upgrade.

Original message

satoshi2010-10-04T19:48:40Z

It can be phased in, like:
if (blocknumber > 115000)
maxblocksize = largerlimit
It can start being in versions way ahead, so by the time it reaches that block number and goes into effect, the older versions that don't have it are already obsolete.
When we're near the cutoff block number, I can put an alert to old versions to make sure they know they have to upgrade.

Original message