Stefan Thomas [ARCHIVE] on Nostr: 📅 Original date posted:2012-05-26 📝 Original message:Zooko is spot on - slower ...
📅 Original date posted:2012-05-26
📝 Original message:Zooko is spot on - slower confirmations will give people a reason to set
higher fees. As soon as fees reach a level where they matter, even
botnet operators will be looking into ways of including transactions for
some extra profit.
In the meantime slightly slower confirmations aren't a problem. Consider
that even if it takes four blocks to get your transaction included
instead of one, once it is included, you still benefit from every new
block in terms of security. So if you're looking for six confirmations
for example, even a three block delay will only be a 50% delay for you.
And of course there are techniques for instant transactions which
continue to be refined and improved.
As for the proposed solutions: Punishing 1-tx blocks is complete and
utter nonsense. It's trivial to include a bogus second transaction.
Any additional challenges towards miners like hashes of the previous
block are at best useless. If I was running a botnet, I'd just grab that
hash from a website (pretty good chance Blockchain.info will have it :P)
or mining pool or wherever and keep going undeterred. At worst they may
affect scalability one day. You might imagine a peer-to-peer network of
miners who for cost reasons don't download all blocks anymore, but
verify only a percentage of them at random. They might then exchange
messages about invalid blocks including a proof (invalid tx, merkle
branch) why the block is invalid. This is just one idea, the point is
that assumptions about what a legitimate miner looks like may not always
hold in the future.
Finally, there is an ethical aspect as well. If a miner wishes not to
include my transaction that is his choice. He has no more an obligation
to sell his service to me than I have to buy it from him. If I really,
really want him to include my transaction I will have to offer to pay more.
If we as developers think that confirmations are too slow or that more
blocks should include transactions, then the right measures would be:
- Educating users about the relationship between confirmation speed and fees
- Raising the default transaction fee
Every market has a supply curve, so it is economically to be expected
that there will be some miners who don't include transactions, simply
because they are at that end of the supply curve where it is not worth
it for them to sell their service. All markets must have a certain
tension - there must be miners who don't include transactions for there
to be users who want their transactions included more quickly. In other
words there must be somebody not confirming if confirmations are to have
value. If you interfere with that all you'll accomplish is keep
transaction fees below market level, which will make the transition from
inflation-financed hashing to transaction-financed hashing more painful
and disruptive.
Cheers,
Stefan
Published at
2023-06-07 10:10:09Event JSON
{
"id": "8046054ff9b8135e66552660c44b131bfb8e1dab1abe22f2583d31492d8bacde",
"pubkey": "49f07bd32c0108a2903a0fa59f904ed312e0ea427d3269eb5fa910eb4a9e22c4",
"created_at": 1686132609,
"kind": 1,
"tags": [
[
"e",
"bea123cfa1dde96d98089cdcf953f77564e34363cd7b11c4a3504634664d4aa2",
"",
"root"
],
[
"e",
"13fea1c194708e5897692a1240969f593b8c4acf259f64f2eb164fa64eed8dc9",
"",
"reply"
],
[
"p",
"29ef37dbe6ee79a52907a84f1511b5ba3f9b3ef1097043f6dfb60cca6b03a59c"
]
],
"content": "📅 Original date posted:2012-05-26\n📝 Original message:Zooko is spot on - slower confirmations will give people a reason to set\nhigher fees. As soon as fees reach a level where they matter, even\nbotnet operators will be looking into ways of including transactions for\nsome extra profit.\n\nIn the meantime slightly slower confirmations aren't a problem. Consider\nthat even if it takes four blocks to get your transaction included\ninstead of one, once it is included, you still benefit from every new\nblock in terms of security. So if you're looking for six confirmations\nfor example, even a three block delay will only be a 50% delay for you.\nAnd of course there are techniques for instant transactions which\ncontinue to be refined and improved.\n\nAs for the proposed solutions: Punishing 1-tx blocks is complete and\nutter nonsense. It's trivial to include a bogus second transaction.\n\nAny additional challenges towards miners like hashes of the previous\nblock are at best useless. If I was running a botnet, I'd just grab that\nhash from a website (pretty good chance Blockchain.info will have it :P)\nor mining pool or wherever and keep going undeterred. At worst they may\naffect scalability one day. You might imagine a peer-to-peer network of\nminers who for cost reasons don't download all blocks anymore, but\nverify only a percentage of them at random. They might then exchange\nmessages about invalid blocks including a proof (invalid tx, merkle\nbranch) why the block is invalid. This is just one idea, the point is\nthat assumptions about what a legitimate miner looks like may not always\nhold in the future.\n\nFinally, there is an ethical aspect as well. If a miner wishes not to\ninclude my transaction that is his choice. He has no more an obligation\nto sell his service to me than I have to buy it from him. If I really,\nreally want him to include my transaction I will have to offer to pay more.\n\nIf we as developers think that confirmations are too slow or that more\nblocks should include transactions, then the right measures would be:\n\n- Educating users about the relationship between confirmation speed and fees\n- Raising the default transaction fee\n\nEvery market has a supply curve, so it is economically to be expected\nthat there will be some miners who don't include transactions, simply\nbecause they are at that end of the supply curve where it is not worth\nit for them to sell their service. All markets must have a certain\ntension - there must be miners who don't include transactions for there\nto be users who want their transactions included more quickly. In other\nwords there must be somebody not confirming if confirmations are to have\nvalue. If you interfere with that all you'll accomplish is keep\ntransaction fees below market level, which will make the transition from\ninflation-financed hashing to transaction-financed hashing more painful\nand disruptive.\n\nCheers,\n\nStefan",
"sig": "f21cc2e8a25fff5fe1be904b2a4e4a3bfdec670e9fc2f16f0df09ab6f83e7f30f2efeef7925b44ad80377b492702996e87d8b62420d7fcf84edf3a10e3ddfdf0"
}