From: Michael Gronager <gronager@mac•com>
To: Pieter Wuille <pieter.wuille@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net,
Andreas Schildbach <andreas@schildbach•de>
Subject: Re: [Bitcoin-development] HTTP REST API for bitcoind
Date: Tue, 23 Jul 2013 11:53:07 +0200 [thread overview]
Message-ID: <7B546311-BBC6-45CB-8983-87DF722F0FA1@mac.com> (raw)
In-Reply-To: <20130723093759.GB6198@vps7135.xlshosting.net>
>
> 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.
>
next prev parent reply other threads:[~2013-07-23 9:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 19:42 Jeff Garzik
2013-07-22 22:06 ` Michael Hendricks
2013-07-23 8:27 ` Andreas Schildbach
2013-07-23 8:45 ` Michael Gronager
2013-07-23 9:37 ` Pieter Wuille
2013-07-23 9:53 ` Michael Gronager [this message]
2013-07-23 10:17 ` Andreas Schildbach
2013-07-23 10:27 ` Pieter Wuille
2013-07-23 9:30 ` Andy Parkins
2013-07-23 9:42 ` Pieter Wuille
2013-07-23 9:52 ` Andy Parkins
2013-07-23 9:56 ` Pieter Wuille
2013-07-23 10:02 ` Andy Parkins
2013-07-23 10:06 ` Pieter Wuille
2013-07-23 9:47 ` Peter Todd
2013-07-23 10:00 ` Andy Parkins
2013-07-23 10:17 ` Peter Todd
2013-07-23 11:45 ` Andy Parkins
2013-07-23 10:19 ` Pieter Wuille
2013-07-23 10:29 ` Andreas Schildbach
2013-07-23 10:36 ` Pieter Wuille
2013-07-23 15:48 ` Michael Hendricks
2013-07-23 19:36 ` Mark Friedenbach
2013-08-10 20:30 ` Rune Kjær Svendsen
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=7B546311-BBC6-45CB-8983-87DF722F0FA1@mac.com \
--to=gronager@mac$(echo .)com \
--cc=andreas@schildbach$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pieter.wuille@gmail$(echo .)com \
/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