To fix the bitcoin utxo set, we need tiered storage. ProVably unspendable outputs are pruned, which makes sense, but proBably unspendable outputs stay stored in RAM.
This is dumb. We should write these to disk and only pull from disk when part of a block or upon spending tx notification. Yes, it takes longer to eval block/tx, but by definition this should a rare event.
What is wrong with my thinking?
drgo / Quantoshi.xyz
npub1fa…nthnd
2025-12-10 03:21:38 UTC
Author Public Key
npub1fa8c9prxnrlkdtjl48adfsxyaduz8tas075l2n4f6903y9awjmxqanthndPublished at
2025-12-10 03:21:38 UTCEvent JSON
{
"id": "9ebc337805a1d8e8b913226043109a6eb4a575945d27c6f37845d3adcb211b83",
"pubkey": "4f4f82846698ff66ae5fa9fad4c0c4eb7823afb07fa9f54ea9d15f1217ae96cc",
"created_at": 1765336898,
"kind": 1,
"tags": [],
"content": "To fix the bitcoin utxo set, we need tiered storage. ProVably unspendable outputs are pruned, which makes sense, but proBably unspendable outputs stay stored in RAM. \n\nThis is dumb. We should write these to disk and only pull from disk when part of a block or upon spending tx notification. Yes, it takes longer to eval block/tx, but by definition this should a rare event. \n\nWhat is wrong with my thinking?",
"sig": "1f69fd8fb626c4ad33f51bda97bbae94c24835c3f89cdd0f9376372f7e6b49d36ef5bca76d6262cfde4255f019767ef6cabd31a88c51b0fcee63c2f4b3831dfc"
}