📅 Original date posted:2015-08-16 📝 Original message:Levin, it is a complicated ...

Mark Friedenbach [ARCHIVE] /

npub1r3s…8d0u

2023-06-07 15:47:41

in reply to nevent1q…hvfl

📅 Original date posted:2015-08-16
📝 Original message:Levin, it is a complicated issue for which there isn't an easy answer. Part
of the issue is that "block size" doesn't actually measure resource usage
very reliably. It is possible to support a much higher volume of typical
usage transactions than transactions specifically constructed to cause DoS
issues. But if "block size" is the knob being tweaked, then you must design
for the DoS worst case, not the average/expected use case.

Additionally, there is an issue of time horizons and what presumed
improvements are made to the client. Bitcoin Core today can barely handle
1MB blocks, but that's an engineering limitation. So are we assuming fixes
that aren't actually deployed yet? Should we raise the block size before
that work is tested and its performance characteristics validated?

It's a complicated issue without easy answers, and that's why you're not
seeing straightforward statements of "2MB", "8MB", or "20MB" from most of
the developers.

But that's not to say that people aren't doing anything. There is a
workshop being organized for September 12-13th that will cover much of
these "it's complicated" issues. There will be a follow-on workshop in the
Nov/Dec timeframe in which specific proposals will be discussed. I
encourage you to participate:

http://scalingbitcoin.org/

On Sun, Aug 16, 2015 at 9:41 AM, Levin Keller via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:

> Hey everyone,
>
> as with the current "max block size" debate I was wondering: Is anyone
> here in favor of a minimum block size (say 2 MB or so)? If so I would be
> interested in an exchange (maybe off-list) of ideas. I am in favor of a
> lower limit and am giving it quite a bit of thought at the moment.
>
> Cheers
>
> Levin
>
> _______________________________________________
> 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/20150816/a20a3511/attachment.html>;

Author Public Key

npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0u

Show more details

Published at

2023-06-07 15:47:41

Kind type

1 Short Text Note

Event JSON

{ "id": "51ccf16f0545394cbf05ae0469201ef079328f7397aea47045f743a454ee126c", "pubkey": "1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069", "created_at": 1686152861, "kind": 1, "tags": [ [ "e", "c6028343af20add1d3ffeb3f35fc60d5874a0688ad01ee7a6b7c0966cb0b2273", "", "root" ], [ "e", "bfe47a89d48b7db0522e11e0d428a4063769c218e7cd4f0d9f9e42f59e39189a", "", "reply" ], [ "p", "a45b2071acb27d4e292ae549d3ac8f24f003e25f0c5145990646328e2236f5b9" ] ], "content": "📅 Original date posted:2015-08-16\n📝 Original message:Levin, it is a complicated issue for which there isn't an easy answer. Part\nof the issue is that \"block size\" doesn't actually measure resource usage\nvery reliably. It is possible to support a much higher volume of typical\nusage transactions than transactions specifically constructed to cause DoS\nissues. But if \"block size\" is the knob being tweaked, then you must design\nfor the DoS worst case, not the average/expected use case.\n\nAdditionally, there is an issue of time horizons and what presumed\nimprovements are made to the client. Bitcoin Core today can barely handle\n1MB blocks, but that's an engineering limitation. So are we assuming fixes\nthat aren't actually deployed yet? Should we raise the block size before\nthat work is tested and its performance characteristics validated?\n\nIt's a complicated issue without easy answers, and that's why you're not\nseeing straightforward statements of \"2MB\", \"8MB\", or \"20MB\" from most of\nthe developers.\n\nBut that's not to say that people aren't doing anything. There is a\nworkshop being organized for September 12-13th that will cover much of\nthese \"it's complicated\" issues. There will be a follow-on workshop in the\nNov/Dec timeframe in which specific proposals will be discussed. I\nencourage you to participate:\n\nhttp://scalingbitcoin.org/\n\nOn Sun, Aug 16, 2015 at 9:41 AM, Levin Keller via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Hey everyone,\n\u003e\n\u003e as with the current \"max block size\" debate I was wondering: Is anyone\n\u003e here in favor of a minimum block size (say 2 MB or so)? If so I would be\n\u003e interested in an exchange (maybe off-list) of ideas. I am in favor of a\n\u003e lower limit and am giving it quite a bit of thought at the moment.\n\u003e\n\u003e Cheers\n\u003e\n\u003e Levin\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/20150816/a20a3511/attachment.html\u003e", "sig": "a1cf44c72cf483ceac7c170041450c3cf87d2cad94f600dbfeb2ede05ab98c637f65fae769ad1549193d91125526e775d3d0a115fa78317b5f7a66a0cfb2b55d" }