Luke-Jr [ARCHIVE] on Nostr: 📅 Original date posted:2012-05-24 📝 Original message:On Thursday, May 24, 2012 ...
📅 Original date posted:2012-05-24
📝 Original message:On Thursday, May 24, 2012 4:33:12 PM Jeff Garzik wrote:
> There appears to be some non-trivial mining power devoted to mining
> empty blocks. Even with satoshi's key observation -- hash a fixed
> 80-byte header, not the entire block -- some miners still find it
> easier to mine empty blocks, rather than watch the network for new
> transactions.
>
> Therefore I was wondering what people thought about a client
> implementation change:
>
> - Do not store or relay empty blocks, if time since last block < X
> (where X = 60 minutes, perhaps)
>
> or even stronger,
>
> - Ensure latest block includes at least X percent of mempool
> unconfirmed TXs
These are problematic for legitimate miners:
1) The freedom to reject transactions based on fees or spam filters, is
severely restricted. As mentioned in other replies, this is an important point
of Bitcoin's design.
1b) This punishes miners with superior transaction spam filtering. As with all
spam filtering, it is often an "arms race" and therefore the filter rules must
be kept private by the miners, and therefore cannot be disclosed for the
validating clients to take into consideration.
2) For a few seconds after a new block is received, the new transaction merkle
root(s) are not finished calculating. During this time, most miners are
working on "blank" blocks with the new previousblockhash but no transactions.
If those blocks are ignored, miners are forced to shutdown mining during this
time.
3) As you mentioned, illegitimate miners can easily workaround these
restrictions (even the second one, by flooding the network with their own
transactions). This puts the legitimate miners at a disadvantage in their own
search for valid blocks, unless they also come up with counter-measures
themselves.
The argument that these are not rule changes is flawed:
1) As of right now, 99% of the network runs a single client. Anything this
client rejects does de facto become a rule change.
2) Even if there were a diverse ecosystem of clients in place, discouragement
rules that potentially affect legitimate miners significantly mess with the
odds of finding a block.
3) If legitimate miners do not adopt counter-rules to bypass these new
restrictions, the illegitimate miners are left with an even larger percentage
of blocks found.
To summarize, I believe such a change as proposed would be very harmful to
Bitcoin.
Luke
Published at
2023-06-07 10:09:32Event JSON
{
"id": "060ff55cce11a36fb685ad3903080e1aad378ea6f2f21c92dba3b80d6949dcd0",
"pubkey": "6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1",
"created_at": 1686132572,
"kind": 1,
"tags": [
[
"e",
"bea123cfa1dde96d98089cdcf953f77564e34363cd7b11c4a3504634664d4aa2",
"",
"root"
],
[
"e",
"2b5cbd2553948f4e41dbda518df25537dc11454e577bbdeedc5e70b9c42cc52f",
"",
"reply"
],
[
"p",
"b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11"
]
],
"content": "📅 Original date posted:2012-05-24\n📝 Original message:On Thursday, May 24, 2012 4:33:12 PM Jeff Garzik wrote:\n\u003e There appears to be some non-trivial mining power devoted to mining\n\u003e empty blocks. Even with satoshi's key observation -- hash a fixed\n\u003e 80-byte header, not the entire block -- some miners still find it\n\u003e easier to mine empty blocks, rather than watch the network for new\n\u003e transactions.\n\u003e \n\u003e Therefore I was wondering what people thought about a client\n\u003e implementation change:\n\u003e \n\u003e - Do not store or relay empty blocks, if time since last block \u003c X\n\u003e (where X = 60 minutes, perhaps)\n\u003e \n\u003e or even stronger,\n\u003e \n\u003e - Ensure latest block includes at least X percent of mempool\n\u003e unconfirmed TXs\n\nThese are problematic for legitimate miners:\n1) The freedom to reject transactions based on fees or spam filters, is \nseverely restricted. As mentioned in other replies, this is an important point \nof Bitcoin's design.\n1b) This punishes miners with superior transaction spam filtering. As with all \nspam filtering, it is often an \"arms race\" and therefore the filter rules must \nbe kept private by the miners, and therefore cannot be disclosed for the \nvalidating clients to take into consideration.\n2) For a few seconds after a new block is received, the new transaction merkle \nroot(s) are not finished calculating. During this time, most miners are \nworking on \"blank\" blocks with the new previousblockhash but no transactions. \nIf those blocks are ignored, miners are forced to shutdown mining during this \ntime.\n3) As you mentioned, illegitimate miners can easily workaround these \nrestrictions (even the second one, by flooding the network with their own \ntransactions). This puts the legitimate miners at a disadvantage in their own \nsearch for valid blocks, unless they also come up with counter-measures \nthemselves.\n\nThe argument that these are not rule changes is flawed:\n1) As of right now, 99% of the network runs a single client. Anything this \nclient rejects does de facto become a rule change.\n2) Even if there were a diverse ecosystem of clients in place, discouragement \nrules that potentially affect legitimate miners significantly mess with the \nodds of finding a block.\n3) If legitimate miners do not adopt counter-rules to bypass these new \nrestrictions, the illegitimate miners are left with an even larger percentage \nof blocks found.\n\nTo summarize, I believe such a change as proposed would be very harmful to \nBitcoin.\n\nLuke",
"sig": "ac6e7f4df21990fc58e2247ee42d4cbed5c070136ef3814e391913666f26330d22ead23f13267a88e65a20aad61000c92d4f3023110f3faacc95603b384635a0"
}