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 ) 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 In-Reply-To: Date: Mon, 7 Apr 2014 21:05:48 +0200 Message-Id: References: <5342C833.5030906@gmail.com> <6D430188-CE00-44B1-BD8C-B623CF04D466@icloudtools.net> <6D6E55CE-2F04-4C34-BEE6-98AEF1478346@bitsofproof.com> <8A6DEBA4-EA59-4BAE-95CF-C964C2DBB84B@bitsofproof.com> To: Gregory Maxwell 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 wrote: > On Mon, Apr 7, 2014 at 12:00 PM, Tamas Blummer = 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
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.


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.

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.


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