From: Tamas Blummer <tamas@bitsofproof•com>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
Date: Mon, 7 Apr 2014 21:05:48 +0200 [thread overview]
Message-ID: <EF231ACC-7B6C-44F2-B154-A3EFD014B081@bitsofproof.com> (raw)
In-Reply-To: <CAAS2fgTE8YKPtkw7Kwuvzs-tXAG_2S2FFpZEPb2W3--pT9c7VA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1083 bytes --]
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.
>
> 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.
>
[-- Attachment #1.2: Type: text/html, Size: 3113 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2014-04-07 19:05 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 11:34 Mike Hearn
2014-04-07 12:17 ` Ricardo Filipe
2014-04-07 13:43 ` Andreas Schildbach
2014-04-07 14:05 ` Mike Hearn
2014-04-07 14:15 ` Eric Martindale
2014-04-07 14:23 ` Mike Hearn
2014-04-07 19:46 ` Troy Benjegerdes
2014-04-08 3:13 ` kjj
2014-04-08 7:50 ` Mike Hearn
2014-04-09 10:38 ` Wendell
2014-04-09 11:15 ` Wladimir
2014-04-07 14:45 ` Tom Harding
2014-04-07 12:19 ` Jameson Lopp
2014-04-07 12:26 ` Pieter Wuille
2014-04-07 12:34 ` Mike Hearn
2014-04-07 12:34 ` Jameson Lopp
2014-05-20 18:38 ` Isidor Zeuner
2014-04-07 13:50 ` Gregory Maxwell
2014-04-07 13:53 ` Gregory Maxwell
2014-04-07 13:58 ` Jameson Lopp
2014-04-07 14:04 ` Gregory Maxwell
2014-04-08 11:28 ` Jesus Cea
2014-04-07 15:45 ` Justus Ranvier
2014-04-07 15:53 ` Gregory Maxwell
2014-04-07 16:02 ` Jameson Lopp
2014-04-07 16:27 ` Mark Friedenbach
2014-04-07 16:57 ` Gregory Maxwell
2014-04-07 17:01 ` Mark Friedenbach
2014-04-07 17:16 ` Gregory Maxwell
2014-04-07 17:35 ` Brent Shambaugh
2014-04-07 17:40 ` Mike Hearn
2014-04-07 17:44 ` Gregory Maxwell
2014-04-07 17:45 ` Tamas Blummer
2014-04-07 17:50 ` Justus Ranvier
2014-04-07 18:30 ` Arne Brutschy
2014-04-07 17:56 ` Brent Shambaugh
2014-04-07 17:46 ` Justus Ranvier
2014-04-07 17:39 ` Chris Williams
2014-04-07 18:23 ` Mike Hearn
2014-04-07 18:35 ` Tamas Blummer
2014-04-07 18:49 ` Gregory Maxwell
2014-04-07 19:00 ` Tamas Blummer
2014-04-07 18:48 ` Mark Friedenbach
2014-04-07 19:02 ` Gregory Maxwell
2014-04-07 19:05 ` Tamas Blummer [this message]
2014-04-07 19:03 ` Gregory Maxwell
2014-04-07 19:13 ` Tier Nolan
2014-04-07 19:20 ` Tamas Blummer
2014-04-07 19:13 ` Mark Friedenbach
2014-04-07 19:36 ` Tamas Blummer
2014-04-07 21:46 ` Ricardo Filipe
2014-04-07 19:30 ` Paul Lyon
2014-04-07 19:50 ` Tamas Blummer
2014-04-07 21:48 ` Tier Nolan
2014-04-07 21:56 ` Gregory Maxwell
2014-04-08 3:44 ` Jeff Garzik
2014-04-08 7:24 ` Jean-Paul Kogelman
2014-04-08 7:59 ` Tamas Blummer
2014-04-08 17:18 ` Andrew LeCody
2014-04-07 17:07 ` Drak
2014-05-20 8:15 ` bitcoingrant
2014-05-20 8:42 ` Mike Hearn
2014-05-20 14:37 ` Eugen Leitl
2014-05-20 14:52 ` Gmail
2014-05-20 18:46 ` Andy Alness
2014-05-20 19:17 ` Jeff Garzik
2014-05-20 20:09 ` Andy Alness
2014-05-20 20:22 ` Jeff Garzik
2014-04-07 21:55 Paul Lyon
2014-04-07 22:14 ` Tier Nolan
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=EF231ACC-7B6C-44F2-B154-A3EFD014B081@bitsofproof.com \
--to=tamas@bitsofproof$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@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