summaryrefslogtreecommitdiff
path: root/9e/fa3ea2393d92615e1d3e0e518c1e76e1a0775b
blob: 45f13b2c7ba6b9f3d60735e891df377cabcc41d0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
Return-Path: <m.bevand@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 0458FB0A
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 16 Nov 2017 17:19:15 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f44.google.com (mail-oi0-f44.google.com
	[209.85.218.44])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8282D52B
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 16 Nov 2017 17:19:14 +0000 (UTC)
Received: by mail-oi0-f44.google.com with SMTP id h81so13345595oib.8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 16 Nov 2017 09:19:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=IgNvGPpCWPIRDEnCzuhbgf8jO0lxHvpIOHfM2C0E4qg=;
	b=eA/nd+efPHkweA0uHsZk718sVvRYnOPw0hxqssTfOT/ceQ8G7bf92L0BGpRuVGHQM9
	k7FA6qh/1Vpw7bMlcJjwrl1IHMdXPVUxXzaPWPElIlpIyRp+gJupjF2W8e6aI5TuCMPA
	SkZGkvNV/GOxNhpo6AuGDa2NNziR+r/imOXYqX4XpbSMoqin1cRSMNd3r6okkyUgCTtY
	FUDz3To4BjiH67kEI5lMvGr5e/YVDKnITN2tKWPJC9yD8Vn21yPFiy0M5wtyhNfLZwN4
	1R0jWsohYQ41lb0FI1MLfbG/yFBNIvggSO2llob20k2+30Pe/cSZ4A0s7xSFWYHx1eUE
	BWVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=IgNvGPpCWPIRDEnCzuhbgf8jO0lxHvpIOHfM2C0E4qg=;
	b=f0R7du1qvga1s72qXmaZDfPfOQXEi6FkdGPDhR2hHA1pEXtPBsuJh7FwCxpQaOhPIM
	lpyP9nt+JBKnF1CIgrNO5AfMMpGRC9VHm1B/yW6Uo4k+LBQxpV9H6EdFPzbMSEUaeq4S
	dUHbCY6M1od9FFEY5JwAKMOji+G+UlGOyzoshwOqRUoKrvF5sh8Vikyub1/00DFE4i5u
	PyaJjdBvypF0FR/SbdqWHqqvx6MtonH8vYE/DCDbzM/unaEbkpjTDRQ6AbYTN7lxNTRT
	OfzWsgq5XRKA4E5NXyE7iPGUx0iNVi7GE2MZeLW0YrFcEwKM5CsUIEMKdFaoSWUQy1ru
	VWnA==
X-Gm-Message-State: AJaThX60/4QSLwzqg8fyvECR2va2544r5sLaac65gcT5dON/NsU8RyYQ
	v7YMJRI+6MpPGtSQGA67Qy5dJC9RxzdBq8Sp9s+srQ==
X-Google-Smtp-Source: AGs4zMbPI+6Q83+X74UXJjVOfQNGsCLNZiAO7mpq/Vb/wQBcclb+M4wUWeP6mTHpE/KbxBj28d6udtxl+Ie7CIOqwkg=
X-Received: by 10.202.114.208 with SMTP id p199mr1682128oic.230.1510852753633; 
	Thu, 16 Nov 2017 09:19:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.124.70 with HTTP; Thu, 16 Nov 2017 09:19:13 -0800 (PST)
In-Reply-To: <CABaSBaw_1WfCEiBXtVxPgJ=UMWji=MwxkVTeKX-BbuVb9N_h5g@mail.gmail.com>
References: <CADH-5r0m0zUP545hN=Or3v8ujixeKZpLqqja0M+5wuZZOWhO4A@mail.gmail.com>
	<CABaSBaw_1WfCEiBXtVxPgJ=UMWji=MwxkVTeKX-BbuVb9N_h5g@mail.gmail.com>
From: Marc Bevand <m.bevand@gmail.com>
Date: Thu, 16 Nov 2017 11:19:13 -0600
Message-ID: <CADH-5r0D0Xhuy0TF=avA9z6cEbfa+jAhJ=cN3HvERn3GiqF3rA@mail.gmail.com>
To: Bryan Bishop <kanzure@gmail.com>
Content-Type: multipart/alternative; boundary="001a1134f3b4b03690055e1cd1c2"
X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE
	autolearn=disabled version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 16 Nov 2017 17:24:38 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Protocol-Level Pruning
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2017 17:19:15 -0000

--001a1134f3b4b03690055e1cd1c2
Content-Type: text/plain; charset="UTF-8"

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>
>

--001a1134f3b4b03690055e1cd1c2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Ah, thanks, I suspected the idea was too simple and m=
ust have been discussed before, but somehow I missed these proposals. I&#39=
;ve got some reading to do.<div><br></div><div>-Marc</div></div></div><div =
class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Nov 16, 2017 a=
t 11:14 AM, Bryan Bishop <span dir=3D"ltr">&lt;<a href=3D"mailto:kanzure@gm=
ail.com" target=3D"_blank">kanzure@gmail.com</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><div dir=3D"ltr">It&#39;s not clear to me if you =
are have looked at the previous UTXO set commitment proposals.<br><br>some =
utxo set commitment bookmarks (a little old)<br><a href=3D"http://diyhpl.us=
/~bryan/irc/bitcoin/utxo-commitments-or-fraud-proofs.stdout.txt" target=3D"=
_blank">http://diyhpl.us/~bryan/irc/<wbr>bitcoin/utxo-commitments-or-<wbr>f=
raud-proofs.stdout.txt</a><br><br>TXO bitfields<br><div><a href=3D"http://d=
iyhpl.us/wiki/transcripts/sf-bitcoin-meetup/2017-07-08-bram-cohen-merkle-se=
ts/" target=3D"_blank">http://diyhpl.us/wiki/<wbr>transcripts/sf-bitcoin-me=
etup/<wbr>2017-07-08-bram-cohen-merkle-<wbr>sets/</a><br><div><br><div>dela=
yed TXO commitments<br><a href=3D"https://lists.linuxfoundation.org/piperma=
il/bitcoin-dev/2016-May/012715.html" target=3D"_blank">https://lists.linuxf=
oundation.<wbr>org/pipermail/bitcoin-dev/<wbr>2016-May/012715.html</a></div=
><div><br></div><div><div>TXO commitments do not need a soft-fork to be use=
ful</div><div><a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoi=
n-dev/2017-February/013591.html" target=3D"_blank">https://lists.linuxfound=
ation.<wbr>org/pipermail/bitcoin-dev/<wbr>2017-February/013591.html</a></di=
v><div><br></div><div><div>rolling UTXO set hashes<br><a href=3D"https://li=
sts.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014337.html" target=
=3D"_blank">https://lists.linuxfoundation.<wbr>org/pipermail/bitcoin-dev/<w=
br>2017-May/014337.html</a><br><br>lotta other resources available, includi=
ng source code proposals..</div></div></div><div><br></div><div class=3D"m_=
8006929569735882325gmail_signature">- Bryan<br><a href=3D"http://heybryan.o=
rg/" target=3D"_blank">http://heybryan.org/</a><br><a href=3D"tel:(512)%202=
03-0507" value=3D"+15122030507" target=3D"_blank">1 512 203 0507</a></div><=
/div></div></div>
</blockquote></div><br></div>

--001a1134f3b4b03690055e1cd1c2--