📅 Original date posted:2015-07-17
📝 Original message:What are you trying to do? Break the ice with a hard fork so that later it
becomes easier to do so, with people more complacent towards it? There are
many solutions to the scaling problem that do not require a hard fork and
are quite simple to implement actually, and don't come with the
complications involved with a hard fork. I'm not a reputable developer on
this list, so my opinion probably doesn't matter much, but I watched and
analyzed this situation closely and I don't like this idea.
On Fri, Jul 17, 2015 at 3:55 PM, Jeff Garzik via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> Opening a mailing list thread on this BIP:
>
> BIP PR: https://github.com/bitcoin/bips/pull/173
> Code PR: https://github.com/bitcoin/bitcoin/pull/6451
>
> The general intent of this BIP is as a minimum viable alternative plan to
> my preferred proposal (BIP 100).
>
> If agreement is not reached on a more comprehensive solution, then this
> solution is at least available and a known quantity. A good backup plan.
>
> Benefits: conservative increase. proves network can upgrade. permits
> some added growth, while the community & market gathers data on how an
> increased block size impacts privacy, security, centralization, transaction
> throughput and other metrics. 2MB seems to be a Least Common Denominator
> on an increase.
>
> Costs: requires a hard fork. requires another hard fork down the road.
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--
PGP: B6AC 822C 451D 6304 6A28 49E9 7DB7 011C D53B 5647
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150717/540d1554/attachment-0001.html>;
Andrew [ARCHIVE] /
npub1l8…hm88x
2023-06-07 15:42:28
in reply to nevent1q…ug5n
Author Public Key
npub1l899vmy2zhg9zr96jvnxt85ayddd26qu36m02k22759e9djqldnqrhm88xPublished at
2023-06-07 15:42:28Event JSON
{
"id": "f03ebbe3ca090a85939fcb4e189fec37a2269f0e6856e8821cfe3b07576f778b",
"pubkey": "f9ca566c8a15d0510cba9326659e9d235ad5681c8eb6f5594af50b92b640fb66",
"created_at": 1686152548,
"kind": 1,
"tags": [
[
"e",
"2e544b01cfe0620e95990efdfb39d6c5828a4b2f5866e5b209d567b2efd50207",
"",
"root"
],
[
"e",
"138534280172cea863cf29dd9ed7018e6b71deb31ddd2fec44e63e5beb3d2ab8",
"",
"reply"
],
[
"p",
"b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11"
]
],
"content": "📅 Original date posted:2015-07-17\n📝 Original message:What are you trying to do? Break the ice with a hard fork so that later it\nbecomes easier to do so, with people more complacent towards it? There are\nmany solutions to the scaling problem that do not require a hard fork and\nare quite simple to implement actually, and don't come with the\ncomplications involved with a hard fork. I'm not a reputable developer on\nthis list, so my opinion probably doesn't matter much, but I watched and\nanalyzed this situation closely and I don't like this idea.\n\nOn Fri, Jul 17, 2015 at 3:55 PM, Jeff Garzik via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Opening a mailing list thread on this BIP:\n\u003e\n\u003e BIP PR: https://github.com/bitcoin/bips/pull/173\n\u003e Code PR: https://github.com/bitcoin/bitcoin/pull/6451\n\u003e\n\u003e The general intent of this BIP is as a minimum viable alternative plan to\n\u003e my preferred proposal (BIP 100).\n\u003e\n\u003e If agreement is not reached on a more comprehensive solution, then this\n\u003e solution is at least available and a known quantity. A good backup plan.\n\u003e\n\u003e Benefits: conservative increase. proves network can upgrade. permits\n\u003e some added growth, while the community \u0026 market gathers data on how an\n\u003e increased block size impacts privacy, security, centralization, transaction\n\u003e throughput and other metrics. 2MB seems to be a Least Common Denominator\n\u003e on an increase.\n\u003e\n\u003e Costs: requires a hard fork. requires another hard fork down the road.\n\u003e\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\n\n-- \nPGP: B6AC 822C 451D 6304 6A28 49E9 7DB7 011C D53B 5647\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150717/540d1554/attachment-0001.html\u003e",
"sig": "6e791ea3a600650d77bb85f3b3e21b2623937c5880062f92bf92e547d54b7681a9931fc75619e435f9817f8a88e744659480da56fc8e9a60e5d49cc181920b8f"
}