📅 Original date posted:2017-04-08
📝 Original message:On Sat, Apr 8, 2017, at 20:27, Tom Harding via bitcoin-dev wrote:
>
>
> On Apr 7, 2017 12:42, "Gregory Maxwell" <greg at xiph.org> wrote:
>> On Fri, Apr 7, 2017 at 6:52 PM, Tom Harding via bitcoin-dev
>> <bitcoin-dev at lists.linuxfoundation.org> wrote:
>> > A network in which many nodes maintain a transaction index also
>> > enables a
>> > class of light node applications that ask peers to prove
>> > existence and
>> > spentness of TXO's.
>>
>> Only with the additional commitment structure such as those proposed
>> by Peter Todd in his stxo/txo commitment designs, e.g.
>> https://petertodd.org/2016/delayed-txo-commitments
> Light nodes are improved by detecting invalid transactions, even
> before they are mined.
> _________________________________________________
I am not quite sure why you think this approach would help in this
regard. I may be missing part of how Core works here, but Bitcrust's
txindex is merely used to lookup transactions from hashes and currently,
and seems to fulfil the same role as Core's -txindex mode.
This can be pruned, and in the future auto-pruned as the "flat files"
used as base for all data allow for concurrent pruning. But unlike Core,
it is always needed as without UTXO index, it is needed to find outputs
during base load validation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170408/8cb653d5/attachment-0001.html>;
Tomas [ARCHIVE] /
npub1rs…9evk4
2023-06-07 17:59:44
in reply to nevent1q…5njr
Author Public Key
npub1rsp4w56r24w3zv4xy8zfgesep45qmf9rq6aghxfw3wr7yemqnnwsf9evk4Published at
2023-06-07 17:59:44Event JSON
{
"id": "d5ddf8c7caecdda3e5b4ed1e899068fd737384a5528ea1e990b08c1dbd3aace7",
"pubkey": "1c03575343555d1132a621c49466190d680da4a306ba8b992e8b87e267609cdd",
"created_at": 1686160784,
"kind": 1,
"tags": [
[
"e",
"d4a682be1f6603f0ff8798c52b7225cac6554e21f3aedb0c80e7d41cf71983ad",
"",
"root"
],
[
"e",
"3df0b2c8e611534b00ed330a52fcabfd2d80ac676ed183846ce6a9c28a8dc0f0",
"",
"reply"
],
[
"p",
"dc329a02c970aabf03b87185ef51c86afe4586fe3a148508af898af3fabc56a3"
]
],
"content": "📅 Original date posted:2017-04-08\n📝 Original message:On Sat, Apr 8, 2017, at 20:27, Tom Harding via bitcoin-dev wrote:\n\n\u003e \n\n\u003e \n\n\u003e On Apr 7, 2017 12:42, \"Gregory Maxwell\" \u003cgreg at xiph.org\u003e wrote:\n\n\u003e\u003e On Fri, Apr 7, 2017 at 6:52 PM, Tom Harding via bitcoin-dev\n\n\u003e\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e\u003e \u003e A network in which many nodes maintain a transaction index also\n\u003e\u003e \u003e enables a\n\u003e\u003e \u003e class of light node applications that ask peers to prove\n\u003e\u003e \u003e existence and\n\u003e\u003e \u003e spentness of TXO's.\n\n\u003e\u003e \n\n\u003e\u003e Only with the additional commitment structure such as those proposed\n\u003e\u003e by Peter Todd in his stxo/txo commitment designs, e.g.\n\n\u003e\u003e https://petertodd.org/2016/delayed-txo-commitments\n\n\u003e Light nodes are improved by detecting invalid transactions, even\n\u003e before they are mined.\n\u003e _________________________________________________\n\n\n\nI am not quite sure why you think this approach would help in this\nregard. I may be missing part of how Core works here, but Bitcrust's\ntxindex is merely used to lookup transactions from hashes and currently,\nand seems to fulfil the same role as Core's -txindex mode.\n\n\nThis can be pruned, and in the future auto-pruned as the \"flat files\"\nused as base for all data allow for concurrent pruning. But unlike Core,\nit is always needed as without UTXO index, it is needed to find outputs\nduring base load validation.\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170408/8cb653d5/attachment-0001.html\u003e",
"sig": "9025093309d5bf7a8f3f831c517fd6c6e08d50a65d47c09ef084d282bb743daeb45662fa6a9f129b4bffb19307995fe73a235dbcb1db8554dc1976771fdc23e4"
}