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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1WTzVA-0002LT-Iv
for bitcoin-development@lists.sourceforge.net;
Sat, 29 Mar 2014 20:05:12 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.170 as permitted sender)
client-ip=209.85.217.170; envelope-from=gmaxwell@gmail.com;
helo=mail-lb0-f170.google.com;
Received: from mail-lb0-f170.google.com ([209.85.217.170])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WTzV9-0002QD-OJ
for bitcoin-development@lists.sourceforge.net;
Sat, 29 Mar 2014 20:05:12 +0000
Received: by mail-lb0-f170.google.com with SMTP id s7so4688955lbd.15
for <bitcoin-development@lists.sourceforge.net>;
Sat, 29 Mar 2014 13:05:05 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.30.233 with SMTP id v9mr55067lbh.35.1396123505118; Sat,
29 Mar 2014 13:05:05 -0700 (PDT)
Received: by 10.112.89.68 with HTTP; Sat, 29 Mar 2014 13:05:05 -0700 (PDT)
In-Reply-To: <53372605.7010405@gmail.com>
References: <mailman.85219.1396122262.2178.bitcoin-development@lists.sourceforge.net>
<3dfcdc$g3rb2n@ironport9.mayo.edu> <53372605.7010405@gmail.com>
Date: Sat, 29 Mar 2014 13:05:05 -0700
Message-ID: <CAAS2fgTi8CetE44tBetbwrPNy=NWH79imSiivYKshxxb_J6h=Q@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Justus Ranvier <justusranvier@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WTzV9-0002QD-OJ
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>, "Goss, Brian C.,
M.D." <Goss.Brian@mayo.edu>
Subject: Re: [Bitcoin-development] Dust recycling
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: Sat, 29 Mar 2014 20:05:12 -0000
On Sat, Mar 29, 2014 at 12:59 PM, Justus Ranvier
<justusranvier@gmail.com> wrote:
> What would make it easier is if there was a standard output type for
> sending the entire transaction to miner fees,
Hm. maybe it could be called a "return operator" or something like that? :)
> that would make even large
> transactions propagate that would normally be dropped by fee/kB rules.
Use dust-b-gone and make it someone elses problem to get it relayed. :)
|
