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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1WTzwO-0004HE-T6
for bitcoin-development@lists.sourceforge.net;
Sat, 29 Mar 2014 20:33:20 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.179 as permitted sender)
client-ip=209.85.217.179; envelope-from=gmaxwell@gmail.com;
helo=mail-lb0-f179.google.com;
Received: from mail-lb0-f179.google.com ([209.85.217.179])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WTzwO-0007BU-4s
for bitcoin-development@lists.sourceforge.net;
Sat, 29 Mar 2014 20:33:20 +0000
Received: by mail-lb0-f179.google.com with SMTP id p9so4769444lbv.10
for <bitcoin-development@lists.sourceforge.net>;
Sat, 29 Mar 2014 13:33:13 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.18.229 with SMTP id z5mr3142516lad.27.1396125193441;
Sat, 29 Mar 2014 13:33:13 -0700 (PDT)
Received: by 10.112.89.68 with HTTP; Sat, 29 Mar 2014 13:33:13 -0700 (PDT)
In-Reply-To: <53372B14.3050901@gmail.com>
References: <mailman.85219.1396122262.2178.bitcoin-development@lists.sourceforge.net>
<3dfcdc$g3rb2n@ironport9.mayo.edu> <53372605.7010405@gmail.com>
<CAAS2fgTi8CetE44tBetbwrPNy=NWH79imSiivYKshxxb_J6h=Q@mail.gmail.com>
<53372B14.3050901@gmail.com>
Date: Sat, 29 Mar 2014 13:33:13 -0700
Message-ID: <CAAS2fgRAErVJJN8gAuNnBpgGjBx2U+0_sVwC351u7qvYvbpdfg@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: 1WTzwO-0007BU-4s
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:33:21 -0000
On Sat, Mar 29, 2014 at 1:20 PM, Justus Ranvier <justusranvier@gmail.com> wrote:
> On 03/29/2014 08:05 PM, Gregory Maxwell wrote:
>> Use dust-b-gone and make it someone elses problem to get it relayed. :)
> That's a sub-optimal solution, as it introduces a third party. What if
> his server goes down?
> An universal solution is preferable.
Then start the server yourself. There is no replacement for
aggregating multiple bits of dust in single transactions. Other ways
are less efficient.
You can already OP_RETURN to include your dust, but miners aren't
going to automatically take that over transactions paying more in
terms of fee/byte.
|
