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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mark@monetize.io>) id 1WXEqk-0001Zi-RY
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 19:04:54 +0000
Received: from mail-pb0-f52.google.com ([209.85.160.52])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXEqj-00087R-Sm
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 19:04:54 +0000
Received: by mail-pb0-f52.google.com with SMTP id rr13so7150323pbb.39
for <bitcoin-development@lists.sourceforge.net>;
Mon, 07 Apr 2014 12:04:48 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:organization:user-agent
:mime-version:to:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=is5dpOWC6AAy+PcgeTtacF/CbJ1zpkfB0xAtZz4h5+A=;
b=Rj5hj4LStFMCJ74ARZjHClrJy8/RBn19Wf+1dEpmKc2eBd+wt1xtFsaE37KIstpONc
PJQl9LO9S71pbOE8W42fUKZSagak5V6vv9cEd4GHajDQ+j9rYuX+JR52CJUTFwUjNb3s
Nnpc8yif31Cq5fSF82vFfIKV0PqQ6AzOQOwF3fkhgBTyQ8waaUcGlAsFVXOE5aWW3KE1
UlfjfZuTwEA8gEDpfwcrViZXW0YpSRo98Wk/V3REED2RmW2+scek7zv27a8TvwCVrAO6
G7APphVYc2M6BfJp4Xe0byteacUu7qJdH9qLSbxsD1Ll2SEQ/qji4qhTA/a4p8TTYfyW
9HFg==
X-Gm-Message-State: ALoCoQl9iOiDpLUwxoOs0ojMEAwhOt9J+76gzHyBf6dAbptduCWA8+daLDk+U+8QVvcQ5/ccpqu0
X-Received: by 10.66.102.4 with SMTP id fk4mr32643481pab.59.1396897487975;
Mon, 07 Apr 2014 12:04:47 -0700 (PDT)
Received: from [192.168.127.194] (50-0-36-93.dsl.dynamic.sonic.net.
[50.0.36.93]) by mx.google.com with ESMTPSA id
tk5sm38431935pbc.63.2014.04.07.12.04.45
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Mon, 07 Apr 2014 12:04:47 -0700 (PDT)
Message-ID: <5342F2FA.6080902@monetize.io>
Date: Mon, 07 Apr 2014 11:48:26 -0700
From: Mark Friedenbach <mark@monetize.io>
Organization: Monetize.io Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
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>
In-Reply-To: <8A6DEBA4-EA59-4BAE-95CF-C964C2DBB84B@bitsofproof.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1WXEqj-00087R-Sm
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:04:55 -0000
On 04/07/2014 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.
The point is that the node has decided not to prune transactions from
that block, so that it is capable of returning full blocks within that
range.
|
