Tadas Varanavičius [ARCHIVE] on Nostr: 📅 Original date posted:2013-03-11 📝 Original message:On 03/11/2013 08:17 PM, ...
📅 Original date posted:2013-03-11
📝 Original message:On 03/11/2013 08:17 PM, Benjamin Lindner wrote:
> The problem of UTXO in principal scales with the block size limit. Thus it should be fixed BEFORE you consider increasing the block size limit. Otherwise you just kick the can down the road, making it bigger.
Let's assume bitcoin has scaled up to 2000 tx/s. We all want this,
right?
https://en.bitcoin.it/wiki/Scalability. Block size is 500 MB.
CPU, network and archival blockchain storage seem to solvable.
Let's say SatoshiDice-like systems are doing informational transactions
that produce unspendable outputs, because they can and users are paying
for it anyway (proved in real life). 400 unspendable outputs per second
would be realistic.
This would be bloating UTXO data at a speed of 52 GB/year. That's a very
big memory leak. And this is just the unspendable outputs.
Bitcoin cannot scale up until such dust output spamming is discouraged
at the protocol level.
Published at
2023-06-07 11:35:24Event JSON
{
"id": "c003a07270c209417ab03cdd2b81e20361a5b7c437941aa356976d862cb5e0f5",
"pubkey": "cfba5f423d25750803554a7cc7d141c492ed9f37a777de29d3a4d030d5c88c58",
"created_at": 1686137724,
"kind": 1,
"tags": [
[
"e",
"ac08c1a6c33933128b534f22efee5bb15c3746d60deefafe520b9c4fff7b646d",
"",
"root"
],
[
"e",
"32cffa07ad87f115e79f13939e36a059abd89d6fe98720fbef2eeeb22bd44030",
"",
"reply"
],
[
"p",
"498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84"
]
],
"content": "📅 Original date posted:2013-03-11\n📝 Original message:On 03/11/2013 08:17 PM, Benjamin Lindner wrote:\n\u003e The problem of UTXO in principal scales with the block size limit. Thus it should be fixed BEFORE you consider increasing the block size limit. Otherwise you just kick the can down the road, making it bigger.\n\nLet's assume bitcoin has scaled up to 2000 tx/s. We all want this, \nright? https://en.bitcoin.it/wiki/Scalability. Block size is 500 MB. \nCPU, network and archival blockchain storage seem to solvable.\n\nLet's say SatoshiDice-like systems are doing informational transactions \nthat produce unspendable outputs, because they can and users are paying \nfor it anyway (proved in real life). 400 unspendable outputs per second \nwould be realistic.\n\nThis would be bloating UTXO data at a speed of 52 GB/year. That's a very \nbig memory leak. And this is just the unspendable outputs.\n\nBitcoin cannot scale up until such dust output spamming is discouraged \nat the protocol level.",
"sig": "a5a2ac899e0ad156dd2a7097940b528aabbee33f39a5dff251315995e861549e7ac7941654ed421c1ef5a2f7a1aac59b3af3e2c3b997812362b85aa338bd8ec7"
}