📅 Original date posted:2017-03-28
📝 Original message:Juan,
I suggest you take a look at this paper:
http://fc16.ifca.ai/bitcoin/papers/CDE+16.pdf It may help you form
opinions based in science rather than what appears to be nothing more than
a hunch. It shows that even 4MB is unsafe. SegWit provides up to this
limit.
8MB is most definitely not safe today.
Whether it is unsafe or impossible is the topic, since Wang Chun proposed
making the block size limit 32MiB.
Wang Chun,
Can you specify what meeting you are talking about? You seem to have not
replied on that point. Who were the participants and what was the purpose
of this meeting?
-Alphonse
On Tue, Mar 28, 2017 at 12:33 PM, Juan Garavaglia <jg at 112bit.com> wrote:
> Alphonse,
>
>
>
> In my opinion if 1MB limit was ok in 2010, 8MB limit is ok on 2016 and
> 32MB limit valid in next halving, from network, storage and CPU perspective
> or 1MB was too high in 2010 what is possible or 1MB is to low today.
>
>
>
> If is unsafe or impossible to raise the blocksize is a different topic.
>
>
> Regards
>
>
>
> Juan
>
>
>
>
>
> *From:* bitcoin-dev-bounces at lists.linuxfoundation.org [mailto:
> bitcoin-dev-bounces at lists.linuxfoundation.org] *On Behalf Of *Alphonse
> Pace via bitcoin-dev
> *Sent:* Tuesday, March 28, 2017 2:24 PM
> *To:* Wang Chun <1240902 at gmail.com>; Bitcoin Protocol Discussion <
> bitcoin-dev at lists.linuxfoundation.org>
> *Subject:* Re: [bitcoin-dev] Hard fork proposal from last week's meeting
>
>
>
> What meeting are you referring to? Who were the participants?
>
>
>
> Removing the limit but relying on the p2p protocol is not really a true
> 32MiB limit, but a limit of whatever transport methods provide. This can
> lead to differing consensus if alternative layers for relaying are used.
> What you seem to be asking for is an unbound block size (or at least
> determined by whatever miners produce). This has the possibility (and even
> likelihood) of removing many participants from the network, including many
> small miners.
>
>
>
> 32MB in less than 3 years also appears to be far beyond limits of safety
> which are known to exist far sooner, and we cannot expect hardware and
> networking layers to improve by those amounts in that time.
>
>
>
> It also seems like it would be much better to wait until SegWit activates
> in order to truly measure the effects on the network from this increased
> capacity before committing to any additional increases.
>
>
>
> -Alphonse
>
>
>
>
>
>
>
> On Tue, Mar 28, 2017 at 11:59 AM, Wang Chun via bitcoin-dev <
> bitcoin-dev at lists.linuxfoundation.org> wrote:
>
> I've proposed this hard fork approach last year in Hong Kong Consensus
> but immediately rejected by coredevs at that meeting, after more than
> one year it seems that lots of people haven't heard of it. So I would
> post this here again for comment.
>
> The basic idea is, as many of us agree, hard fork is risky and should
> be well prepared. We need a long time to deploy it.
>
> Despite spam tx on the network, the block capacity is approaching its
> limit, and we must think ahead. Shall we code a patch right now, to
> remove the block size limit of 1MB, but not activate it until far in
> the future. I would propose to remove the 1MB limit at the next block
> halving in spring 2020, only limit the block size to 32MiB which is
> the maximum size the current p2p protocol allows. This patch must be
> in the immediate next release of Bitcoin Core.
>
> With this patch in core's next release, Bitcoin works just as before,
> no fork will ever occur, until spring 2020. But everyone knows there
> will be a fork scheduled. Third party services, libraries, wallets and
> exchanges will have enough time to prepare for it over the next three
> years.
>
> We don't yet have an agreement on how to increase the block size
> limit. There have been many proposals over the past years, like
> BIP100, 101, 102, 103, 104, 105, 106, 107, 109, 148, 248, BU, and so
> on. These hard fork proposals, with this patch already in Core's
> release, they all become soft fork. We'll have enough time to discuss
> all these proposals and decide which one to go. Take an example, if we
> choose to fork to only 2MB, since 32MiB already scheduled, reduce it
> from 32MiB to 2MB will be a soft fork.
>
> Anyway, we must code something right now, before it becomes too late.
> _______________________________________________
> 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/20170328/70199439/attachment.html>;
Alphonse Pace [ARCHIVE] /
npub1xd…lkyw0
2023-06-07 17:58:08
in reply to nevent1q…gfea
Author Public Key
npub1xddusuj8cyeqaqalq0zklafvdgr26pt32t0tvquw5mmwwwm3dehsqlkyw0Published at
2023-06-07 17:58:08Event JSON
{
"id": "185708fa8043a482190f8ef9cd688fa8bbdb215067c46f4b487ba5c66203b309",
"pubkey": "335bc87247c1320e83bf03c56ff52c6a06ad057152deb6038ea6f6e73b716e6f",
"created_at": 1686160688,
"kind": 1,
"tags": [
[
"e",
"f66fb8ea0b053d3b896ce377aea38775ffc7975376c3ee96291861cf920b456b",
"",
"root"
],
[
"e",
"12614a56851516472e7b523645641e8bc08ed70b5de0d16191c97362b8bea793",
"",
"reply"
],
[
"p",
"b8acca17a6f74c77cd8a4899846d99012d1b52082a01a2d2753fcb0c6669a60b"
]
],
"content": "📅 Original date posted:2017-03-28\n📝 Original message:Juan,\n\nI suggest you take a look at this paper:\nhttp://fc16.ifca.ai/bitcoin/papers/CDE+16.pdf It may help you form\nopinions based in science rather than what appears to be nothing more than\na hunch. It shows that even 4MB is unsafe. SegWit provides up to this\nlimit.\n\n8MB is most definitely not safe today.\n\nWhether it is unsafe or impossible is the topic, since Wang Chun proposed\nmaking the block size limit 32MiB.\n\n\nWang Chun,\n\nCan you specify what meeting you are talking about? You seem to have not\nreplied on that point. Who were the participants and what was the purpose\nof this meeting?\n\n-Alphonse\n\nOn Tue, Mar 28, 2017 at 12:33 PM, Juan Garavaglia \u003cjg at 112bit.com\u003e wrote:\n\n\u003e Alphonse,\n\u003e\n\u003e\n\u003e\n\u003e In my opinion if 1MB limit was ok in 2010, 8MB limit is ok on 2016 and\n\u003e 32MB limit valid in next halving, from network, storage and CPU perspective\n\u003e or 1MB was too high in 2010 what is possible or 1MB is to low today.\n\u003e\n\u003e\n\u003e\n\u003e If is unsafe or impossible to raise the blocksize is a different topic.\n\u003e\n\n\u003e\n\u003e Regards\n\u003e\n\u003e\n\u003e\n\u003e Juan\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e *From:* bitcoin-dev-bounces at lists.linuxfoundation.org [mailto:\n\u003e bitcoin-dev-bounces at lists.linuxfoundation.org] *On Behalf Of *Alphonse\n\u003e Pace via bitcoin-dev\n\u003e *Sent:* Tuesday, March 28, 2017 2:24 PM\n\u003e *To:* Wang Chun \u003c1240902 at gmail.com\u003e; Bitcoin Protocol Discussion \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e\n\u003e *Subject:* Re: [bitcoin-dev] Hard fork proposal from last week's meeting\n\u003e\n\u003e\n\u003e\n\u003e What meeting are you referring to? Who were the participants?\n\u003e\n\u003e\n\u003e\n\u003e Removing the limit but relying on the p2p protocol is not really a true\n\u003e 32MiB limit, but a limit of whatever transport methods provide. This can\n\u003e lead to differing consensus if alternative layers for relaying are used.\n\u003e What you seem to be asking for is an unbound block size (or at least\n\u003e determined by whatever miners produce). This has the possibility (and even\n\u003e likelihood) of removing many participants from the network, including many\n\u003e small miners.\n\u003e\n\u003e\n\u003e\n\u003e 32MB in less than 3 years also appears to be far beyond limits of safety\n\u003e which are known to exist far sooner, and we cannot expect hardware and\n\u003e networking layers to improve by those amounts in that time.\n\u003e\n\u003e\n\u003e\n\u003e It also seems like it would be much better to wait until SegWit activates\n\u003e in order to truly measure the effects on the network from this increased\n\u003e capacity before committing to any additional increases.\n\u003e\n\u003e\n\u003e\n\u003e -Alphonse\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e On Tue, Mar 28, 2017 at 11:59 AM, Wang Chun via bitcoin-dev \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e I've proposed this hard fork approach last year in Hong Kong Consensus\n\u003e but immediately rejected by coredevs at that meeting, after more than\n\u003e one year it seems that lots of people haven't heard of it. So I would\n\u003e post this here again for comment.\n\u003e\n\u003e The basic idea is, as many of us agree, hard fork is risky and should\n\u003e be well prepared. We need a long time to deploy it.\n\u003e\n\u003e Despite spam tx on the network, the block capacity is approaching its\n\u003e limit, and we must think ahead. Shall we code a patch right now, to\n\u003e remove the block size limit of 1MB, but not activate it until far in\n\u003e the future. I would propose to remove the 1MB limit at the next block\n\u003e halving in spring 2020, only limit the block size to 32MiB which is\n\u003e the maximum size the current p2p protocol allows. This patch must be\n\u003e in the immediate next release of Bitcoin Core.\n\u003e\n\u003e With this patch in core's next release, Bitcoin works just as before,\n\u003e no fork will ever occur, until spring 2020. But everyone knows there\n\u003e will be a fork scheduled. Third party services, libraries, wallets and\n\u003e exchanges will have enough time to prepare for it over the next three\n\u003e years.\n\u003e\n\u003e We don't yet have an agreement on how to increase the block size\n\u003e limit. There have been many proposals over the past years, like\n\u003e BIP100, 101, 102, 103, 104, 105, 106, 107, 109, 148, 248, BU, and so\n\u003e on. These hard fork proposals, with this patch already in Core's\n\u003e release, they all become soft fork. We'll have enough time to discuss\n\u003e all these proposals and decide which one to go. Take an example, if we\n\u003e choose to fork to only 2MB, since 32MiB already scheduled, reduce it\n\u003e from 32MiB to 2MB will be a soft fork.\n\u003e\n\u003e Anyway, we must code something right now, before it becomes too late.\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\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170328/70199439/attachment.html\u003e",
"sig": "63da44fa584a2ad2d05a5c8f30bca53c3b2a9215d1b5851799a52c50b6d3cf2b6f2c285b47a5ec66ebf34aa04f94171b81670bb9178a5503ba82d3edcd346a8b"
}