From: Tomas <tomas@tomasvdw•nl>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Using a storage engine without UTXO-index
Date: Sat, 08 Apr 2017 21:23:40 +0200 [thread overview]
Message-ID: <1491679420.2446184.938577504.77C413F5@webmail.messagingengine.com> (raw)
In-Reply-To: <CALJP9GBn7cCTmzvDeG8DdKPO0YVTgyk9jB9Nn2PY_G=hbTYWvg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
On Sat, Apr 8, 2017, at 20:27, Tom Harding via bitcoin-dev wrote:
>
>
> On Apr 7, 2017 12:42, "Gregory Maxwell" <greg@xiph•org> wrote:
>> On Fri, Apr 7, 2017 at 6:52 PM, Tom Harding via bitcoin-dev
>> <bitcoin-dev@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.
[-- Attachment #2: Type: text/html, Size: 2170 bytes --]
next prev parent reply other threads:[~2017-04-08 19:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 22:12 Tomas
2017-04-06 23:38 ` Eric Voskuil
2017-04-07 0:17 ` Tomas
2017-04-08 22:37 ` Eric Voskuil
2017-04-08 23:58 ` Tomas
2017-04-11 1:44 ` Eric Voskuil
2017-04-11 8:43 ` Tomas
2017-04-11 9:41 ` Eric Voskuil
2017-04-11 10:04 ` Tomas
[not found] ` <CAAS2fgTEMCkDWdhCWt1EsUrnt3+Z_8m+Y1PTsff5Rc0CBnCKWQ@mail.gmail.com>
2017-04-07 0:48 ` Tomas
2017-04-07 1:09 ` Gregory Maxwell
2017-04-07 1:29 ` Tomas
2017-04-07 18:52 ` Tom Harding
2017-04-07 19:42 ` Gregory Maxwell
2017-04-08 18:27 ` Tom Harding
2017-04-08 19:23 ` Tomas [this message]
2017-04-07 7:55 ` Marcos mayorga
2017-04-07 8:47 ` Tomas
2017-04-07 14:14 ` Greg Sanders
2017-04-07 16:02 ` Tomas
2017-04-07 18:18 ` Gregory Maxwell
2017-04-07 18:39 ` Bram Cohen
2017-04-07 19:55 ` Eric Voskuil
2017-04-07 21:44 ` Tomas
2017-04-07 23:51 ` Eric Voskuil
2017-04-07 21:14 ` Tomas
2017-04-08 0:44 ` Gregory Maxwell
2017-04-08 7:28 ` Tomas
2017-04-08 19:23 ` Johnson Lau
2017-04-08 19:56 ` Tomas
2017-04-08 20:21 ` Johnson Lau
2017-04-08 20:42 ` Tomas
2017-04-08 22:12 ` Gregory Maxwell
2017-04-08 22:34 ` Tomas
2017-04-08 21:22 ` Troy Benjegerdes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1491679420.2446184.938577504.77C413F5@webmail.messagingengine.com \
--to=tomas@tomasvdw$(echo .)nl \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox