📅 Original date posted:2016-12-10
📝 Original message:> While disk space requirements might not be a big problem, block
propagation time is
Is block propagation time really still a problem? Compact blocks and FIBRE
should help here.
> Bitcoin, because its fundamental design, can scale by using offchain
solutions.
I agree.
However, I believe that on-chain scaling will be needed regardless of which
off-chain solution gains popularity.
2016-12-10 11:44 GMT+01:00 s7r via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org>:
> t. khan via bitcoin-dev wrote:
> > BIP Proposal - Managing Bitcoin’s block size the same way we do
> > difficulty (aka Block75)
> >
> > The every two-week adjustment of difficulty has proven to be a
> > reasonably effective and predictable way of managing how quickly blocks
> > are mined. Bitcoin needs a reasonably effective and predictable way of
> > managing the maximum block size.
> >
> > It’s clear at this point that human beings should not be involved in the
> > determination of max block size, just as they’re not involved in
> > deciding the difficulty.
> >
> > Instead of setting an arbitrary max block size (1MB, 2MB, 8MB, etc.) or
> > passing the decision to miners/pool operators, the max block size should
> > be adjusted every two weeks (2016 blocks) using a system similar to how
> > difficulty is calculated.
> >
> > Put another way: let’s stop thinking about what the max block size
> > should be and start thinking about how full we want the average block to
> > be regardless of size. Over the last year, we’ve had averages of 75% or
> > higher, so aiming for 75% full seems reasonable, hence naming this
> > concept ‘Block75’.
> >
> > The target capacity over 2016 blocks would be 75%. If the last 2016
> > blocks are more than 75% full, add the difference to the max block size.
> > Like this:
> >
> > MAX_BLOCK_BASE_SIZE = 1000000
> > TARGET_CAPACITY = 750000
> > AVERAGE_OVER_CAP = average block size of last 2016 blocks minus
> > TARGET_CAPACITY
> >
> > To check if a block is valid, ≤ (MAX_BLOCK_BASE_SIZE + AVERAGE_OVER_CAP)
> >
> > For example, if the last 2016 blocks are 85% full (average block is 850
> > KB), add 10% to the max block size. The new max block size would be
> > 1,100 KB until the next 2016 blocks are mined, then reset and
> > recalculate. The 1,000,000 byte limit that exists currently would
> > remain, but would effectively be the minimum max block size.
> >
> > Another two weeks goes by, the last 2016 blocks are again 85% full, but
> > now that means they average 935 KB out of the 1,100 KB max block size.
> > This is 93.5% of the 1,000,000 byte limit, so 18.5% would be added to
> > that to make the new max block size of 1,185 KB.
> >
> > Another two weeks passes. This time, the average block is 1,050 KB. The
> > new max block size is calculated to 1,300 KB (as blocks were 105% full,
> > minus the 75% capacity target, so 30% added to max block size).
> >
> > Repeat every 2016 blocks, forever.
> >
> > If Block75 had been applied at the difficulty adjustment on November
> > 18th, the max block size would have been 1,080KB, as the average block
> > during that period was 83% full, so 8% is added to the 1,000KB limit.
> > The current size, after the December 2nd adjustment would be 1,150K.
> >
> > Block75 would allow the max block size to grow (or shrink) in response
> > to transaction volume, and does so predictably, reasonably quickly, and
> > in a method that prevents wild swings in block size or transaction fees.
> > It attempts to keep blocks at 75% total capacity over each two week
> > period, the same way difficulty tries to keep blocks mined every ten
> > minutes. It also keeps blocks as small as possible.
> >
> > Thoughts?
> >
> > -t.k.
> >
>
> I like the idea. It is good wrt growing the max. block size
> automatically without human action, but the main problem (or question)
> is not how to grow this number, it is what number can the network
> handle, considering both miners and users. While disk space requirements
> might not be a big problem, block propagation time is. The time required
> for a block to propagate in the network (or at least to all the miners)
> is directly dependent of its size. If blocks take too much time to
> propagate in the network, the orphan rate will increase in unpredictable
> ways. For example if the internet speed in China is worse than in
> Europe, and miners in China have more than 50% of the hashing power,
> blocks mined by European miners might get orphaned.
>
> The system as described can also be gamed, by filling the network with
> transactions. Miners have the monetary interest to include as many
> transactions as possible in a block in order to collect the fees.
> Regardless how you think about it, there has to be a maximum block size
> that the network will allow as a consensus rule. Increasing it
> dynamically based on transaction volume will reach a point where the
> number got big enough that it broke things. Bitcoin, because its
> fundamental design, can scale by using offchain solutions.
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20161210/0eae6a60/attachment.html>;
Hampus Sjöberg [ARCHIVE] /
npub10u…hln8t
2023-06-07 17:54:46
in reply to nevent1q…ergv
Author Public Key
npub10uzud4rf4636awmfgvarmcfndcmdnv8rfd2y3rx2sqgckv9zur4qahln8tPublished at
2023-06-07 17:54:46Event JSON
{
"id": "dcb2f4c13f05efcfd5d422bfa99cbb61138555de7eae189f1ce5b0f071312ba0",
"pubkey": "7f05c6d469aea3aebb69433a3de1336e36d9b0e34b54488cca80118b30a2e0ea",
"created_at": 1686160486,
"kind": 1,
"tags": [
[
"e",
"93f229f84c7a0d580081719bdeab8a0791a31bea972b61b4a96af898141b5a6b",
"",
"root"
],
[
"e",
"f989de55e407e516f8da430baea8b927c63e0cc4f623e417babaacb47e9db16e",
"",
"reply"
],
[
"p",
"947955301a8805054c8d6a2c9ac2abf07a7a18f4a33b0a573a277868302953b1"
]
],
"content": "📅 Original date posted:2016-12-10\n📝 Original message:\u003e While disk space requirements might not be a big problem, block\npropagation time is\n\nIs block propagation time really still a problem? Compact blocks and FIBRE\nshould help here.\n\n\u003e Bitcoin, because its fundamental design, can scale by using offchain\nsolutions.\n\nI agree.\nHowever, I believe that on-chain scaling will be needed regardless of which\noff-chain solution gains popularity.\n\n2016-12-10 11:44 GMT+01:00 s7r via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e:\n\n\u003e t. khan via bitcoin-dev wrote:\n\u003e \u003e BIP Proposal - Managing Bitcoin’s block size the same way we do\n\u003e \u003e difficulty (aka Block75)\n\u003e \u003e\n\u003e \u003e The every two-week adjustment of difficulty has proven to be a\n\u003e \u003e reasonably effective and predictable way of managing how quickly blocks\n\u003e \u003e are mined. Bitcoin needs a reasonably effective and predictable way of\n\u003e \u003e managing the maximum block size.\n\u003e \u003e\n\u003e \u003e It’s clear at this point that human beings should not be involved in the\n\u003e \u003e determination of max block size, just as they’re not involved in\n\u003e \u003e deciding the difficulty.\n\u003e \u003e\n\u003e \u003e Instead of setting an arbitrary max block size (1MB, 2MB, 8MB, etc.) or\n\u003e \u003e passing the decision to miners/pool operators, the max block size should\n\u003e \u003e be adjusted every two weeks (2016 blocks) using a system similar to how\n\u003e \u003e difficulty is calculated.\n\u003e \u003e\n\u003e \u003e Put another way: let’s stop thinking about what the max block size\n\u003e \u003e should be and start thinking about how full we want the average block to\n\u003e \u003e be regardless of size. Over the last year, we’ve had averages of 75% or\n\u003e \u003e higher, so aiming for 75% full seems reasonable, hence naming this\n\u003e \u003e concept ‘Block75’.\n\u003e \u003e\n\u003e \u003e The target capacity over 2016 blocks would be 75%. If the last 2016\n\u003e \u003e blocks are more than 75% full, add the difference to the max block size.\n\u003e \u003e Like this:\n\u003e \u003e\n\u003e \u003e MAX_BLOCK_BASE_SIZE = 1000000\n\u003e \u003e TARGET_CAPACITY = 750000\n\u003e \u003e AVERAGE_OVER_CAP = average block size of last 2016 blocks minus\n\u003e \u003e TARGET_CAPACITY\n\u003e \u003e\n\u003e \u003e To check if a block is valid, ≤ (MAX_BLOCK_BASE_SIZE + AVERAGE_OVER_CAP)\n\u003e \u003e\n\u003e \u003e For example, if the last 2016 blocks are 85% full (average block is 850\n\u003e \u003e KB), add 10% to the max block size. The new max block size would be\n\u003e \u003e 1,100 KB until the next 2016 blocks are mined, then reset and\n\u003e \u003e recalculate. The 1,000,000 byte limit that exists currently would\n\u003e \u003e remain, but would effectively be the minimum max block size.\n\u003e \u003e\n\u003e \u003e Another two weeks goes by, the last 2016 blocks are again 85% full, but\n\u003e \u003e now that means they average 935 KB out of the 1,100 KB max block size.\n\u003e \u003e This is 93.5% of the 1,000,000 byte limit, so 18.5% would be added to\n\u003e \u003e that to make the new max block size of 1,185 KB.\n\u003e \u003e\n\u003e \u003e Another two weeks passes. This time, the average block is 1,050 KB. The\n\u003e \u003e new max block size is calculated to 1,300 KB (as blocks were 105% full,\n\u003e \u003e minus the 75% capacity target, so 30% added to max block size).\n\u003e \u003e\n\u003e \u003e Repeat every 2016 blocks, forever.\n\u003e \u003e\n\u003e \u003e If Block75 had been applied at the difficulty adjustment on November\n\u003e \u003e 18th, the max block size would have been 1,080KB, as the average block\n\u003e \u003e during that period was 83% full, so 8% is added to the 1,000KB limit.\n\u003e \u003e The current size, after the December 2nd adjustment would be 1,150K.\n\u003e \u003e\n\u003e \u003e Block75 would allow the max block size to grow (or shrink) in response\n\u003e \u003e to transaction volume, and does so predictably, reasonably quickly, and\n\u003e \u003e in a method that prevents wild swings in block size or transaction fees.\n\u003e \u003e It attempts to keep blocks at 75% total capacity over each two week\n\u003e \u003e period, the same way difficulty tries to keep blocks mined every ten\n\u003e \u003e minutes. It also keeps blocks as small as possible.\n\u003e \u003e\n\u003e \u003e Thoughts?\n\u003e \u003e\n\u003e \u003e -t.k.\n\u003e \u003e\n\u003e\n\u003e I like the idea. It is good wrt growing the max. block size\n\u003e automatically without human action, but the main problem (or question)\n\u003e is not how to grow this number, it is what number can the network\n\u003e handle, considering both miners and users. While disk space requirements\n\u003e might not be a big problem, block propagation time is. The time required\n\u003e for a block to propagate in the network (or at least to all the miners)\n\u003e is directly dependent of its size. If blocks take too much time to\n\u003e propagate in the network, the orphan rate will increase in unpredictable\n\u003e ways. For example if the internet speed in China is worse than in\n\u003e Europe, and miners in China have more than 50% of the hashing power,\n\u003e blocks mined by European miners might get orphaned.\n\u003e\n\u003e The system as described can also be gamed, by filling the network with\n\u003e transactions. Miners have the monetary interest to include as many\n\u003e transactions as possible in a block in order to collect the fees.\n\u003e Regardless how you think about it, there has to be a maximum block size\n\u003e that the network will allow as a consensus rule. Increasing it\n\u003e dynamically based on transaction volume will reach a point where the\n\u003e number got big enough that it broke things. Bitcoin, because its\n\u003e fundamental design, can scale by using offchain solutions.\n\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20161210/0eae6a60/attachment.html\u003e",
"sig": "ae22836530fc575e66ff003d8495ce86119c0c4d04c096befa950da6a1f7009ec5ba449f5a2abb7ccb60974dc58cfe1e51376a3d2a84a67d38eea8de2c90efcf"
}