đź“… Original date posted:2018-01-27
đź“ť Original message:Miners can fill their blocks with transactions paying very high fees at no
cost because they get the fees back to themselves. They can do this for
different purposes, like trying to increase the recommended fee. Here I
propose a backwards-compatible solution to this problem.
The solution would be to reward the fees of the current block to the miner
of the next block (or X blocks after the current one). That way, if a miner
floods its own block with very high fee transactions, those fees are no
longer given back to itself, but to the miner of future blocks which could
potentially be anyone. Flooding blocks with fake txs is now discouraged.
However, filling blocks with real transactions paying real fees is still
encouraged because you could be the one to mine the block that would claim
this reward.
The way to implement this in a backwards-compatible fashion would be to
enforce miners to set an anyone-can-spend output in the coinbase
transaction of the block (by adding this as a rule for verifying new
blocks). The miner of 100 blocks after the current one can add a secondary
transaction spending this block's anyone-can-spend coinbase transaction
(due to the coinbase needing 100 blocks to mature) and thus claiming the
funds. This way, the block reward of a block X is always transferred to the
miner of block X+100.
Implementing this would require a soft-fork. Since that secondary
transaction needs no signature whatsoever, the overhead caused by that
extra transaction is negligible.
Possible Downside: When the fork is activated, the miners won’t get any
reward for mining blocks for a period of 100 blocks. They could choose to
power off the mining equipment for maintenance or to save power over that
period, so the hashrate could drop temporarily. However, if the hashrate
drops too much, blocks would take much longer to mine, and miners wouldn’t
want that either since they want to go through those 100 reward-less blocks
as soon as possible so they can start getting rewards from mining again.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180127/70e96d79/attachment.html>;
Nathan Parker [ARCHIVE] /
npub1z3…cufx6
2023-06-07 18:10:17
in reply to nevent1q…yu9t
Author Public Key
npub1z3ny0acp9dcludslt2e2kw2ddn3hlreqfpngfwq62fqx439k43yq0cufx6Published at
2023-06-07 18:10:17Event JSON
{
"id": "1145310c66fcc602f162f9f12410321c7c8bb5abfa63e3bcf7724327e0fd5cf8",
"pubkey": "146647f7012b71fe361f5ab2ab394d6ce37f8f20486684b81a52406ac4b6ac48",
"created_at": 1686161417,
"kind": 1,
"tags": [
[
"e",
"8aa1a2e99bfee38bd0f906d936318c57f05a80fcd4e5ba689c4b18f16da0811f",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2018-01-27\n📝 Original message:Miners can fill their blocks with transactions paying very high fees at no\ncost because they get the fees back to themselves. They can do this for\ndifferent purposes, like trying to increase the recommended fee. Here I\npropose a backwards-compatible solution to this problem.\n\nThe solution would be to reward the fees of the current block to the miner\nof the next block (or X blocks after the current one). That way, if a miner\nfloods its own block with very high fee transactions, those fees are no\nlonger given back to itself, but to the miner of future blocks which could\npotentially be anyone. Flooding blocks with fake txs is now discouraged.\nHowever, filling blocks with real transactions paying real fees is still\nencouraged because you could be the one to mine the block that would claim\nthis reward.\n\nThe way to implement this in a backwards-compatible fashion would be to\nenforce miners to set an anyone-can-spend output in the coinbase\ntransaction of the block (by adding this as a rule for verifying new\nblocks). The miner of 100 blocks after the current one can add a secondary\ntransaction spending this block's anyone-can-spend coinbase transaction\n(due to the coinbase needing 100 blocks to mature) and thus claiming the\nfunds. This way, the block reward of a block X is always transferred to the\nminer of block X+100.\n\nImplementing this would require a soft-fork. Since that secondary\ntransaction needs no signature whatsoever, the overhead caused by that\nextra transaction is negligible.\n\nPossible Downside: When the fork is activated, the miners won’t get any\nreward for mining blocks for a period of 100 blocks. They could choose to\npower off the mining equipment for maintenance or to save power over that\nperiod, so the hashrate could drop temporarily. However, if the hashrate\ndrops too much, blocks would take much longer to mine, and miners wouldn’t\nwant that either since they want to go through those 100 reward-less blocks\nas soon as possible so they can start getting rewards from mining again.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20180127/70e96d79/attachment.html\u003e",
"sig": "eff1daf965dce399b62048d8cf6734f78d0d4f7f6856c597018d7493068f2d2613e5f79febaf3f554c257ed088946c54e0eeae582ba6b7c46449667b12de2bb3"
}