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
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gcbd-bitcoin-development@m.gmane.org>)
id 1W3yQ0-0005yP-9p for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jan 2014 01:40:20 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of m.gmane.org
designates 80.91.229.3 as permitted sender)
client-ip=80.91.229.3;
envelope-from=gcbd-bitcoin-development@m.gmane.org;
helo=plane.gmane.org;
Received: from plane.gmane.org ([80.91.229.3])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1W3yPy-0001qD-7L
for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jan 2014 01:40:20 +0000
Received: from list by plane.gmane.org with local (Exim 4.69)
(envelope-from <gcbd-bitcoin-development@m.gmane.org>)
id 1W3yPp-0006kR-6Y for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jan 2014 02:40:09 +0100
Received: from 179.111.9.210 ([179.111.9.210])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00 for <bitcoin-development@lists.sourceforge.net>;
Fri, 17 Jan 2014 02:40:09 +0100
Received: from fragabr by 179.111.9.210 with local (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00 for <bitcoin-development@lists.sourceforge.net>;
Fri, 17 Jan 2014 02:40:09 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: bitcoin-development@lists.sourceforge.net
From: =?UTF-8?B?RMOibmllbA==?= Fraga <fragabr@gmail.com>
Date: Thu, 16 Jan 2014 23:39:59 -0200
Organization: http://www.youtube.com/DanielFragaBR
Message-ID: <lba1l3$4tg$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: 179.111.9.210
X-Newsreader: Claws Mail 3.9.0cvs128 (GTK+ 2.24.20; x86_64-unknown-linux-gnu)
X-Spam-Score: 2.2 (++)
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
(fragabr[at]gmail.com)
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [80.91.229.3 listed in list.dnswl.org]
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is
CUSTOM_MED
-0.0 SPF_PASS SPF: sender matches SPF record
0.9 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO
-0.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain 2.0 FSL_HELO_BARE_IP_2 FSL_HELO_BARE_IP_2
1.2 NML_ADSP_CUSTOM_MED ADSP custom_med hit,
and not from a mailing list
X-Headers-End: 1W3yPy-0001qD-7L
Subject: [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 01:40:20 -0000
Someone sent me a very small donation (0.00121 BTC) without
paying fees. I don't know who sent it and I know this type of
transaction are usually rejected by miners. Take a look at it below:
https://imageshack.com/i/ngv5g8j
Even with the a low probability of confirmation, I
was hoping that after a few days it could be included in a block, but
Blockchain.info simply removed it (I know the sender sent from a
Blockchain.info wallet, because he added a note):
https://blockchain.info/pt/tx/3cde47ee3979a46b36bd61bdb0caf9c11dea58ac99f17fb17b95728766de70e0
As you can see now it shows as "Transaction not found".
My suggestion is: it would be nice if the receiver could have a
chance to pay the fee when the sender didn't pay any fee. For example,
I could pay a fee of 0.0001 BTC and receive 0.00121 BTC. In the end I'd
have 0.00111 BTC. Better than nothing.
Would it be technically possible to do that or it would be too
much trouble to change the protocol to allow the receiver to pay an
optional fee?
Ps: I'm not a programmer, but if the receiver could
optionally "attach" some fee to the transaction, even if he/she didn't
sent the transaction, this could be solved. Bitcoin-qt could even warn
the receiver he received a transaction without fee and if he wants
faster confirmation he could pay a fee.
Ps2: if this is a silly suggestion, just ignore it. I tried on
Bitcointalk, but nobody answered.
--
Linux 3.12.0: One Giant Leap for Frogkind
http://www.youtube.com/DanielFragaBR
http://mcxnow.com
Bitcoin: 12H6661yoLDUZaYPdah6urZS5WiXwTAUgL
|
