From: Marc Bevand <m.bevand@gmail•com>
To: Bryan Bishop <kanzure@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Protocol-Level Pruning
Date: Thu, 16 Nov 2017 11:19:13 -0600 [thread overview]
Message-ID: <CADH-5r0D0Xhuy0TF=avA9z6cEbfa+jAhJ=cN3HvERn3GiqF3rA@mail.gmail.com> (raw)
In-Reply-To: <CABaSBaw_1WfCEiBXtVxPgJ=UMWji=MwxkVTeKX-BbuVb9N_h5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Ah, thanks, I suspected the idea was too simple and must have been
discussed before, but somehow I missed these proposals. I've got some
reading to do.
-Marc
On Thu, Nov 16, 2017 at 11:14 AM, Bryan Bishop <kanzure@gmail•com> wrote:
> It's not clear to me if you are have looked at the previous UTXO set
> commitment proposals.
>
> some utxo set commitment bookmarks (a little old)
> http://diyhpl.us/~bryan/irc/bitcoin/utxo-commitments-or-
> fraud-proofs.stdout.txt
>
> TXO bitfields
> http://diyhpl.us/wiki/transcripts/sf-bitcoin-meetup/
> 2017-07-08-bram-cohen-merkle-sets/
>
> delayed TXO commitments
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/
> 2016-May/012715.html
>
> TXO commitments do not need a soft-fork to be useful
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/
> 2017-February/013591.html
>
> rolling UTXO set hashes
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/
> 2017-May/014337.html
>
> lotta other resources available, including source code proposals..
>
> - Bryan
> http://heybryan.org/
> 1 512 203 0507 <(512)%20203-0507>
>
[-- Attachment #2: Type: text/html, Size: 2324 bytes --]
next prev parent reply other threads:[~2017-11-16 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 16:56 Marc Bevand
2017-11-16 17:14 ` Bryan Bishop
2017-11-16 17:19 ` Marc Bevand [this message]
2017-11-17 19:07 ` William Casarin
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='CADH-5r0D0Xhuy0TF=avA9z6cEbfa+jAhJ=cN3HvERn3GiqF3rA@mail.gmail.com' \
--to=m.bevand@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=kanzure@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