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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1W42Av-0001q2-Ok
for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jan 2014 05:41:01 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([192.3.11.21])
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1W42At-0001ng-T3 for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jan 2014 05:41:01 +0000
Received: from ishibashi.localnet (unknown
[IPv6:2001:470:5:265:be5f:f4ff:febf:4f76])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id 366241080833;
Fri, 17 Jan 2014 05:41:14 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Fri, 17 Jan 2014 05:40:52 +0000
User-Agent: KMail/1.13.7 (Linux/3.12.6-gentoo; KDE/4.11.2; x86_64; ; )
References: <lba1l3$4tg$1@ger.gmane.org> <lba369$sp9$1@ger.gmane.org>
<CANOOu=-cA7TTfAtfRy1WL+Dy6EQPwjcTH1m=u+f9RB73wC=btw@mail.gmail.com>
In-Reply-To: <CANOOu=-cA7TTfAtfRy1WL+Dy6EQPwjcTH1m=u+f9RB73wC=btw@mail.gmail.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201401170540.53093.luke@dashjr.org>
X-Spam-Score: -0.3 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1W42At-0001ng-T3
Cc: =?iso-8859-1?q?D=E2niel_Fraga?= <fragabr@gmail.com>
Subject: Re: [Bitcoin-development] Suggestion: allow receivers to pay
optional fee for transactions without fees
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: Fri, 17 Jan 2014 05:41:01 -0000
On Friday, January 17, 2014 2:39:31 AM Christophe Biocca wrote:
> To clarify, there are proposals to make miners recognize this
> situation and account for it, only eligius is running it at the moment
> IIRC:
> http://bitcoin.stackexchange.com/questions/8390/are-there-any-pools-or-larg
> e-miners-running-child-pays-for-parent-patch Right now if you were to try
> it likely wouldn't result in inclusion. But this is on the radar, and I
> suspect it'll eventually get merged into mainline.
If you did it and relayed directly to Eligius, it'd probably get mined.. the
hard part is creating the transaction - once that's done it's smooth sailing
;)
Side note: mining nodes should *not* be running mainline. In fact, they should
be setting up their own customised transaction policies.
|
