Tom Harding [ARCHIVE] on Nostr: 📅 Original date posted:2016-12-18 📝 Original message:James, I share your ...
📅 Original date posted:2016-12-18
📝 Original message:James,
I share your conviction that miners are the natural gatekeepers of the
maximum block size.
The trouble I see with Block75 is that linear growth won't work forever.
Also, by reading actual and not miners' preferred max blocksize, this
proposal is sensitive to randomness in block timing and tx rate, and so
incentivizes miners to manipulate their block content unnaturally in
either the up or down direction to influence the calculation.
The EB/AD scheme of Bitcoin Unlimited recognizes implementation of the
max blocksize by miners, who publish their preferred max blocksize. But
it expects forks of unpredictable (probably short) length as network
behavior evolves.
BIP100, which also recognizes miner implementation of the max blocksize,
but has a change support threshold, and like Block75 defines the timing
of max blocksize increases, looks superior to me.
On 12/18/2016 1:53 PM, James MacWhyte via bitcoin-dev wrote:
> Hi All,
>
> I'm coming late to the party. I like the Block75 proposal.
>
> Multiple people have said miners would/could stuff blocks with
> insincere transactions to increase the block size, but it was never
> adequately explained what they would gain from this. If there aren't
> enough legitimate transactions to fill up the block, where do you plan
> to earn extra income once the block is bigger?
>
> Miners would be incentivized to include as many legitimate
> transactions as possible, but if propagation time is as big an issue
> as some of you have said it is, miners would also be incentivized to
> keep their blocks small enough to propagate. So why not give them the
> choice? Once the block size gets too big to propagate effectively,
> miners would be naturally incentivized to limit how much data they put
> in each block, finding the perfect balance.
>
> In my opinion, none of the downsides presented so far have been a good
> argument. Risk of a 51% attack is not unique to this proposal, saying
> "we could also do that with hardcoded limits" doesn't actually point
> out any problem with this proposal, and miners already have the
> ability to add or withhold transactions from their blocks.
>
> We trust our miners to serve us by acting in their own best interests,
> and this proposal simply gives them more options for doing that. If
> anyone can make a strong argument against that would earn top marks in
> a high school debate class, I'd love to hear it!
>
> James
>
Published at
2023-06-07 17:54:52Event JSON
{
"id": "a0b009ec828317b2f493d05aebb90964e37fa65c3aa06fe92a67c4a5d3e7f781",
"pubkey": "dc329a02c970aabf03b87185ef51c86afe4586fe3a148508af898af3fabc56a3",
"created_at": 1686160492,
"kind": 1,
"tags": [
[
"e",
"93f229f84c7a0d580081719bdeab8a0791a31bea972b61b4a96af898141b5a6b",
"",
"root"
],
[
"e",
"00a2e1cbecaa3dc386459a646f2cfe1b7b143e3f85957d79d4bdd4c31254155d",
"",
"reply"
],
[
"p",
"52e5d0646af3ea5ccb6c4bd31237d6068258a11ace3ac40f02466a3f89342928"
]
],
"content": "📅 Original date posted:2016-12-18\n📝 Original message:James,\n\nI share your conviction that miners are the natural gatekeepers of the\nmaximum block size.\n\nThe trouble I see with Block75 is that linear growth won't work forever.\nAlso, by reading actual and not miners' preferred max blocksize, this\nproposal is sensitive to randomness in block timing and tx rate, and so\nincentivizes miners to manipulate their block content unnaturally in\neither the up or down direction to influence the calculation. \n\nThe EB/AD scheme of Bitcoin Unlimited recognizes implementation of the\nmax blocksize by miners, who publish their preferred max blocksize. But\nit expects forks of unpredictable (probably short) length as network\nbehavior evolves.\n\nBIP100, which also recognizes miner implementation of the max blocksize,\nbut has a change support threshold, and like Block75 defines the timing\nof max blocksize increases, looks superior to me.\n\n\nOn 12/18/2016 1:53 PM, James MacWhyte via bitcoin-dev wrote:\n\u003e Hi All,\n\u003e\n\u003e I'm coming late to the party. I like the Block75 proposal.\n\u003e\n\u003e Multiple people have said miners would/could stuff blocks with\n\u003e insincere transactions to increase the block size, but it was never\n\u003e adequately explained what they would gain from this. If there aren't\n\u003e enough legitimate transactions to fill up the block, where do you plan\n\u003e to earn extra income once the block is bigger?\n\u003e\n\u003e Miners would be incentivized to include as many legitimate\n\u003e transactions as possible, but if propagation time is as big an issue\n\u003e as some of you have said it is, miners would also be incentivized to\n\u003e keep their blocks small enough to propagate. So why not give them the\n\u003e choice? Once the block size gets too big to propagate effectively,\n\u003e miners would be naturally incentivized to limit how much data they put\n\u003e in each block, finding the perfect balance.\n\u003e\n\u003e In my opinion, none of the downsides presented so far have been a good\n\u003e argument. Risk of a 51% attack is not unique to this proposal, saying\n\u003e \"we could also do that with hardcoded limits\" doesn't actually point\n\u003e out any problem with this proposal, and miners already have the\n\u003e ability to add or withhold transactions from their blocks.\n\u003e\n\u003e We trust our miners to serve us by acting in their own best interests,\n\u003e and this proposal simply gives them more options for doing that. If\n\u003e anyone can make a strong argument against that would earn top marks in\n\u003e a high school debate class, I'd love to hear it!\n\u003e\n\u003e James\n\u003e",
"sig": "93ef6460e0e4b91e4a54920b1e52c5d59169074d0219a050a8ae97470205ff92b53e77c80149ccd28ecffc0f2b0953611d879c5aa89fafa4ef04b1937378ffa3"
}