📅 Original date posted:2015-12-12
📝 Original message:It is a common practice in commercial banks that a dormant account might
be confiscated. Confiscating or deleting dormant UTXOs might be too
controversial, but allowing the UTXOs set growing without any limit
might not be a sustainable option. People lose their private keys.
People do stupid things like sending bitcoin to 1BitcoinEater. We
shouldn’t be obliged to store everything permanently. This is my
proposal:
Dormant UTXOs are those UTXOs with 420000 confirmations. In every block
X after 420000, it will commit to a hash for all UTXOs generated in
block X-420000. The UTXOs are first serialized into the form:
txid|index|value|scriptPubKey, then a sorted Merkle hash is calculated.
After some confirmations, nodes may safely delete the UTXO records of
block X permanently.
If a user is trying to redeem a dormant UTXO, in addition the signature,
they have to provide the scriptPubKey, height (X), and UTXO value as
part of the witness. They also need to provide the Merkle path to the
dormant UTXO commitment.
To confirm this tx, the miner will calculate a new Merkle hash for the
block X, with the hash of the spent UTXO replaced by 1, and commit the
hash to the current block. All full nodes will keep an index of latest
dormant UTXO commitments so double spending is not possible. (a
"meta-UTXO set")
If all dormant UTXOs under a Merkle branch are spent, hash of the branch
will become 1. If all dormant UTXOs in a block are spent, the record for
this block could be forgotten. Full nodes do not need to remember which
particular UTXO is spent or not, since any person trying to redeem a
dormant UTXO has to provide such information.
It becomes the responsibility of dormant coin holders to scan the
blockchain for the current status of the UTXO commitment for their coin.
They may also need to pay extra fee for the increased tx size.
This is a softfork if there is no hash collision but this is a
fundamental assumption in Bitcoin anyway. The proposal also works
without segregated witness, just by replacing "witness" with "scriptSig"
jl2012 at xbt.hk [ARCHIVE] /
npub1kc…wjfw4
2023-06-07 17:46:12
in reply to nevent1q…nytd
Author Public Key
npub1kc0zulxt7j4a0ayhzhrz7jk84y7tm4026qcky7w97hlfkxxap24qnwjfw4Published at
2023-06-07 17:46:12Event JSON
{
"id": "c1e8b117b7f02d66ff1072a411c82f45e2949d815b44aa387c769a7d98e8b929",
"pubkey": "b61e2e7ccbf4abd7f49715c62f4ac7a93cbdd5ead0316279c5f5fe9b18dd0aaa",
"created_at": 1686159972,
"kind": 1,
"tags": [
[
"e",
"3a132d93c9c4c5dfbfb11ddb31dd151bd41288218a2dab2ec24f273a7cf079bf",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2015-12-12\n📝 Original message:It is a common practice in commercial banks that a dormant account might \nbe confiscated. Confiscating or deleting dormant UTXOs might be too \ncontroversial, but allowing the UTXOs set growing without any limit \nmight not be a sustainable option. People lose their private keys. \nPeople do stupid things like sending bitcoin to 1BitcoinEater. We \nshouldn’t be obliged to store everything permanently. This is my \nproposal:\n\nDormant UTXOs are those UTXOs with 420000 confirmations. In every block \nX after 420000, it will commit to a hash for all UTXOs generated in \nblock X-420000. The UTXOs are first serialized into the form: \ntxid|index|value|scriptPubKey, then a sorted Merkle hash is calculated. \nAfter some confirmations, nodes may safely delete the UTXO records of \nblock X permanently.\n\nIf a user is trying to redeem a dormant UTXO, in addition the signature, \nthey have to provide the scriptPubKey, height (X), and UTXO value as \npart of the witness. They also need to provide the Merkle path to the \ndormant UTXO commitment.\n\nTo confirm this tx, the miner will calculate a new Merkle hash for the \nblock X, with the hash of the spent UTXO replaced by 1, and commit the \nhash to the current block. All full nodes will keep an index of latest \ndormant UTXO commitments so double spending is not possible. (a \n\"meta-UTXO set\")\n\nIf all dormant UTXOs under a Merkle branch are spent, hash of the branch \nwill become 1. If all dormant UTXOs in a block are spent, the record for \nthis block could be forgotten. Full nodes do not need to remember which \nparticular UTXO is spent or not, since any person trying to redeem a \ndormant UTXO has to provide such information.\n\nIt becomes the responsibility of dormant coin holders to scan the \nblockchain for the current status of the UTXO commitment for their coin. \nThey may also need to pay extra fee for the increased tx size.\n\nThis is a softfork if there is no hash collision but this is a \nfundamental assumption in Bitcoin anyway. The proposal also works \nwithout segregated witness, just by replacing \"witness\" with \"scriptSig\"",
"sig": "2dabe6ce984a409bbd140cb6faa0ca6fc1ac0e069c73749196cf1d94dc41bf26da18f2f375953edd599cc40abf404fd8961061de990d3502938fd9be96336b8c"
}