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
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tamas@bitsofproof.com>) id 1WXErY-0003BW-Mp
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 19:05:44 +0000
X-ACL-Warn:
Received: from wp059.webpack.hosteurope.de ([80.237.132.66])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1WXErX-0003YA-3f
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 19:05:44 +0000
Received: from [37.143.74.116] (helo=[192.168.2.2]); authenticated
by wp059.webpack.hosteurope.de running ExIM with esmtpsa
(TLS1.0:RSA_AES_128_CBC_SHA1:16)
id 1WXErQ-0007Bx-49; Mon, 07 Apr 2014 21:05:36 +0200
Content-Type: multipart/signed;
boundary="Apple-Mail=_12475426-1B12-4179-82BF-B1F72273A51A";
protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Tamas Blummer <tamas@bitsofproof.com>
In-Reply-To: <CAAS2fgTE8YKPtkw7Kwuvzs-tXAG_2S2FFpZEPb2W3--pT9c7VA@mail.gmail.com>
Date: Mon, 7 Apr 2014 21:05:48 +0200
Message-Id: <EF231ACC-7B6C-44F2-B154-A3EFD014B081@bitsofproof.com>
References: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com>
<5342C833.5030906@gmail.com>
<CAAS2fgTqBfEPXh2dfcL_ke6c0wfXw4qUM1rAYMkAHcAM6mYH+g@mail.gmail.com>
<6D430188-CE00-44B1-BD8C-B623CF04D466@icloudtools.net>
<CANEZrP1-9LpPw4WuY8bfsEG0OLoDECXTfQCoZsZ4tmOn2H7Omw@mail.gmail.com>
<6D6E55CE-2F04-4C34-BEE6-98AEF1478346@bitsofproof.com>
<CAAS2fgQaJ6P4Aj2A5Zox+CiGQK6jHvF1CkLH1R6xbadYhUXO2g@mail.gmail.com>
<8A6DEBA4-EA59-4BAE-95CF-C964C2DBB84B@bitsofproof.com>
<CAAS2fgTE8YKPtkw7Kwuvzs-tXAG_2S2FFpZEPb2W3--pT9c7VA@mail.gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
X-Mailer: Apple Mail (2.1874)
X-bounce-key: webpack.hosteurope.de; tamas@bitsofproof.com; 1396897543;
36e74af1;
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1WXErX-0003YA-3f
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 19:05:44 -0000
--Apple-Mail=_12475426-1B12-4179-82BF-B1F72273A51A
Content-Type: multipart/alternative;
boundary="Apple-Mail=_D0836864-F796-4C1F-AB93-0E4D60707E3F"
--Apple-Mail=_D0836864-F796-4C1F-AB93-0E4D60707E3F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
Maybe it is not a question of the maturity of the implementation but =
that of the person making presumptions of it.
I consider a fully pruned blockchain being equivalent to the UTXO. Block =
that hold no
more unspent transaction are reduced to a header. There is however no =
harm if more retained.
Tamas Blummer
http://bitsofproof.com
On 07.04.2014, at 21:02, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> On Mon, Apr 7, 2014 at 12:00 PM, Tamas Blummer <tamas@bitsofproof.com> =
wrote:
>> Once a single transaction in pruned in a block, the block is no =
longer
>> eligible to be served to other nodes.
>> Which transactions are pruned can be rather custom e.g. even =
depending on
>> the wallet(s) of the node,
>> therefore I guess it is more handy to return some bitmap of =
pruned/full
>> blocks than ranges.
>=20
> This isn't at all how pruning works in Bitcoin-QT (nor is it how I
> expect pruning to work for any mature implementation). Pruning can
> work happily on a whole block at a time basis regardless if all the
> transactions in it are spent or not.
>=20
--Apple-Mail=_D0836864-F796-4C1F-AB93-0E4D60707E3F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=us-ascii
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div>Maybe it is not a question of the maturity of =
the implementation but that of the person making presumptions of =
it.</div><div><br></div><div>I consider a fully pruned blockchain being =
equivalent to the UTXO. Block that hold no</div><div>more unspent =
transaction are reduced to a header. There is however no harm if more =
retained.</div><br><div apple-content-edited=3D"true"><span =
style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; widows: =
2; float: none; display: inline !important;">Tamas Blummer</span><br =
style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; widows: =
2;"><span style=3D"color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;"><span style=3D"color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; orphans: 2; =
widows: 2; float: none; display: inline !important;"><a =
href=3D"http://bitsofproof.com">http://bitsofproof.com</a></span>
</span></div>
<br><div><div>On 07.04.2014, at 21:02, Gregory Maxwell <<a =
href=3D"mailto:gmaxwell@gmail.com">gmaxwell@gmail.com</a>> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">On Mon, Apr 7, 2014 at 12:00 PM, Tamas Blummer <<a =
href=3D"mailto:tamas@bitsofproof.com">tamas@bitsofproof.com</a>> =
wrote:<br><blockquote type=3D"cite">Once a single transaction in pruned =
in a block, the block is no longer<br>eligible to be served to other =
nodes.<br>Which transactions are pruned can be rather custom e.g. even =
depending on<br>the wallet(s) of the node,<br>therefore I guess it is =
more handy to return some bitmap of pruned/full<br>blocks than =
ranges.<br></blockquote><br>This isn't at all how pruning works in =
Bitcoin-QT (nor is it how I<br>expect pruning to work for any =
mature implementation). Pruning can<br>work happily on a whole block at =
a time basis regardless if all the<br>transactions in it are spent or =
not.<br><br></blockquote></div><br></body></html>=
--Apple-Mail=_D0836864-F796-4C1F-AB93-0E4D60707E3F--
--Apple-Mail=_12475426-1B12-4179-82BF-B1F72273A51A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJTQvcNAAoJEPZykcUXcTkcxI4IAJM8KsBvmdYqE/IXlWiN9f0f
795+E9Km78I1SsffXQkMl9OpQsVt1F9wiqJZ1Oj652ZoyLFhn7BzubbcBmhW4Mqd
llr4dLuZYGUJmt1sI4I8xtj3zqwJbdwcZOTVQnCqb++C8znUGkC3w6eJylT+VE+E
OVnMcE0PBH8+cmnUUWwN5gNHiqUMCcB/fLFzSRa/tzAROOjAHBW9HcIomWizCl8C
fcfa5qK6wVyB77il8ScS7ciqJH1MEQvYN/zIlkbYFihUEKluc/YOZDrr68+I0MNU
eszruFufmqw54f38Y24JsA8B3M4VVxKrk7QT5cSrSCGAJTWdr8faXA7R/ze6a2g=
=BA+n
-----END PGP SIGNATURE-----
--Apple-Mail=_12475426-1B12-4179-82BF-B1F72273A51A--
|
