📅 Original date posted:2017-02-08
📝 Original message:You're never going to reach 100% agreement, and stifling the network
literally forever to please a tiny minority is daft.
On Feb 8, 2017 8:52 AM, "alp alp via bitcoin-dev" <
bitcoin-dev at lists.linuxfoundation.org> wrote:
10% say literally never. That seems like a significant disenfranchisement
and lack of consensus.
On Mon, Feb 6, 2017 at 2:25 PM, t. khan via bitcoin-dev <bitcoin-dev at lists.
linuxfoundation.org> wrote:
> On Mon, Feb 6, 2017 at 2:53 PM, Luke Dashjr <luke at dashjr.org> wrote:
>
>> On Monday, February 06, 2017 6:19:43 PM you wrote:
>> > >My BIP draft didn't make progress because the community opposes any
>> block
>> > >size increase hardfork ever.
>> >
>> > Luke, how do you know the community opposes that? Specifically, how did
>> you
>> > come to this conclusion?
>>
>> http://www.strawpoll.me/12228388/r
>
>
> That poll shows 63% of votes want a larger than 1 MB block by this summer.
> How do you go from that to "the community opposes any block increase ever"?
> It shows the exact opposite of that.
>
>
>> > >Your version doesn't address the current block size
>> > >issues (ie, the blocks being too large).
>> >
>> > Why do you think blocks are "too large"? Please cite some evidence. I've
>> > asked this before and you ignored it, but an answer would be helpful to
>> the
>> > discussion.
>>
>> Full node count is far below the safe minimum of 85% of economic activity.
>>
>
> Is this causing a problem now? If so, what?
>
>
>> Typically reasons given for people not using full nodes themselves come
>> down
>> to the high resource requirements caused by the block size.
>
>
> The reason people stop running nodes is because there's no incentive to
> counteract the resource costs. Attempting to solve this by making blocks
> *smaller* is like curing a disease by killing the patient. (Incentivizing
> full node operation would fix that problem.)
>
> - t.k.
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
_______________________________________________
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/20170208/fab8e0e5/attachment-0001.html>;
Andrew Johnson [ARCHIVE] /
npub1lf…zuul6
2023-06-07 17:56:03
in reply to nevent1q…mwh0
Author Public Key
npub1lf5jdpupmcelz945y09tzawew6pqs5wkkp6dppeujgxxnqltgufsmzuul6Published at
2023-06-07 17:56:03Event JSON
{
"id": "6d19f83d32d3a804b43dc55d2696d4b432b976b0838bb598392c9ddca284dc0f",
"pubkey": "fa69268781de33f116b423cab175d976820851d6b074d0873c920c6983eb4713",
"created_at": 1686160563,
"kind": 1,
"tags": [
[
"e",
"6eddf1a13d41cd54af30531855ceb7d14eb31ca00a80520a5a643c560fb7dfbd",
"",
"root"
],
[
"e",
"9b630eb2b90d06d9548bc4bb88514d9ad5d3e86577ccdb32628c826d5c8c5c7c",
"",
"reply"
],
[
"p",
"41039e090f0185a2be08428c0e2334baa3ec18d6a2aec206d39baefcff777095"
]
],
"content": "📅 Original date posted:2017-02-08\n📝 Original message:You're never going to reach 100% agreement, and stifling the network\nliterally forever to please a tiny minority is daft.\n\nOn Feb 8, 2017 8:52 AM, \"alp alp via bitcoin-dev\" \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n10% say literally never. That seems like a significant disenfranchisement\nand lack of consensus.\n\nOn Mon, Feb 6, 2017 at 2:25 PM, t. khan via bitcoin-dev \u003cbitcoin-dev at lists.\nlinuxfoundation.org\u003e wrote:\n\n\u003e On Mon, Feb 6, 2017 at 2:53 PM, Luke Dashjr \u003cluke at dashjr.org\u003e wrote:\n\u003e\n\u003e\u003e On Monday, February 06, 2017 6:19:43 PM you wrote:\n\u003e\u003e \u003e \u003eMy BIP draft didn't make progress because the community opposes any\n\u003e\u003e block\n\u003e\u003e \u003e \u003esize increase hardfork ever.\n\u003e\u003e \u003e\n\u003e\u003e \u003e Luke, how do you know the community opposes that? Specifically, how did\n\u003e\u003e you\n\u003e\u003e \u003e come to this conclusion?\n\u003e\u003e\n\u003e\u003e http://www.strawpoll.me/12228388/r\n\u003e\n\u003e\n\u003e That poll shows 63% of votes want a larger than 1 MB block by this summer.\n\u003e How do you go from that to \"the community opposes any block increase ever\"?\n\u003e It shows the exact opposite of that.\n\u003e\n\u003e\n\u003e\u003e \u003e \u003eYour version doesn't address the current block size\n\u003e\u003e \u003e \u003eissues (ie, the blocks being too large).\n\u003e\u003e \u003e\n\u003e\u003e \u003e Why do you think blocks are \"too large\"? Please cite some evidence. I've\n\u003e\u003e \u003e asked this before and you ignored it, but an answer would be helpful to\n\u003e\u003e the\n\u003e\u003e \u003e discussion.\n\u003e\u003e\n\u003e\u003e Full node count is far below the safe minimum of 85% of economic activity.\n\u003e\u003e\n\u003e\n\u003e Is this causing a problem now? If so, what?\n\u003e\n\u003e\n\u003e\u003e Typically reasons given for people not using full nodes themselves come\n\u003e\u003e down\n\u003e\u003e to the high resource requirements caused by the block size.\n\u003e\n\u003e\n\u003e The reason people stop running nodes is because there's no incentive to\n\u003e counteract the resource costs. Attempting to solve this by making blocks\n\u003e *smaller* is like curing a disease by killing the patient. (Incentivizing\n\u003e full node operation would fix that problem.)\n\u003e\n\u003e - t.k.\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_______________________________________________\nbitcoin-dev mailing list\nbitcoin-dev at lists.linuxfoundation.org\nhttps://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170208/fab8e0e5/attachment-0001.html\u003e",
"sig": "c50474b702a6826960b1b2e295bcde0991d5dc2a4a6b6e920171f06b731fe6ce80a063997082c416070698c8204668dc84bb25bebad6bdb9ec56a752f432af62"
}