📅 Original date posted:2013-07-23
📝 Original message:>
> The only way to do this safely at an SPV security assumption, is by
> having an address-indexed committed merkle UTXO-set tree, like the
> one proposed by Alan Reiner, and being implemented by Mark
> Friedenback. I know Michael Gronager has something similar implemented,
> but I don't know whether it is script-indexed.
The MerkleTrie I have in libcoin is indexed on UTXOs only. However, adding
an extra index for scripts would be pretty easy (half day of coding), or even having the two merged into one index.
The burden imposed on validating nodes for keeping such an index is really minimal. When using the UTXO MerkleTrie I switch off the sqlite index of these and vise versa, so there are hardly any measurable timing difference.
However, the MerkleTrie index is currently re-build on startup (which takes ~30 sec on my laptop), keeping it synced with disk would be optimal and in the long run necessary as even the UTXO set will grow over time.
> To be actually useful,
> it likely needs to be enforced by miners - putting a significant
> burden on validation nodes. Still, if it can be done efficiently,
> I think this would be worth it, but more research is needed first in
> any case.
>
Michael Gronager [ARCHIVE] /
npub1nc…gw452
2023-06-07 15:04:56
in reply to nevent1q…a706
Author Public Key
npub1nc78dlt7hp3v5dl32qu3m678h2j0ss374glcjnz8df75xcx7ngpq4gw452Published at
2023-06-07 15:04:56Event JSON
{
"id": "cb7c456ef97fd917d231da9331231296142e6cd4b3d36ed17e20c1d62ebbe575",
"pubkey": "9e3c76fd7eb862ca37f150391debc7baa4f8423eaa3f894c476a7d4360de9a02",
"created_at": 1686150296,
"kind": 1,
"tags": [
[
"e",
"2548e3bbd5806f0a91f1440e5be19b1893f723d052860cba20b98f557d042316",
"",
"root"
],
[
"e",
"ae20f8408ece0bf33997cccdaba631bb7ed3f7fc1e6a4d54f02bcbf70c35a77a",
"",
"reply"
],
[
"p",
"5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6"
]
],
"content": "📅 Original date posted:2013-07-23\n📝 Original message:\u003e \n\u003e The only way to do this safely at an SPV security assumption, is by\n\u003e having an address-indexed committed merkle UTXO-set tree, like the\n\u003e one proposed by Alan Reiner, and being implemented by Mark\n\u003e Friedenback. I know Michael Gronager has something similar implemented,\n\u003e but I don't know whether it is script-indexed.\n\nThe MerkleTrie I have in libcoin is indexed on UTXOs only. However, adding\nan extra index for scripts would be pretty easy (half day of coding), or even having the two merged into one index.\n\nThe burden imposed on validating nodes for keeping such an index is really minimal. When using the UTXO MerkleTrie I switch off the sqlite index of these and vise versa, so there are hardly any measurable timing difference.\n\nHowever, the MerkleTrie index is currently re-build on startup (which takes ~30 sec on my laptop), keeping it synced with disk would be optimal and in the long run necessary as even the UTXO set will grow over time.\n\n\u003e To be actually useful,\n\u003e it likely needs to be enforced by miners - putting a significant\n\u003e burden on validation nodes. Still, if it can be done efficiently,\n\u003e I think this would be worth it, but more research is needed first in\n\u003e any case.\n\u003e",
"sig": "cfcb39db439905d11a09add0d629bed3ebcbc4220197ea6ed1d970d820f1d039d313bce83cdf703062e21fbee13125fb12a74dfcbf14e330837155227e992bb1"
}