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
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
|
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 <bendavenport@gmail.com>) id 1W3yc2-0006bu-EF
for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jan 2014 01:52:46 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.171 as permitted sender)
client-ip=209.85.214.171; envelope-from=bendavenport@gmail.com;
helo=mail-ob0-f171.google.com;
Received: from mail-ob0-f171.google.com ([209.85.214.171])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W3yc1-0002PG-AD
for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jan 2014 01:52:46 +0000
Received: by mail-ob0-f171.google.com with SMTP id wm4so3671698obc.2
for <bitcoin-development@lists.sourceforge.net>;
Thu, 16 Jan 2014 17:52:40 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.60.120.8 with SMTP id ky8mr4442071oeb.3.1389923559893; Thu,
16 Jan 2014 17:52:39 -0800 (PST)
Received: by 10.76.122.80 with HTTP; Thu, 16 Jan 2014 17:52:39 -0800 (PST)
In-Reply-To: <lba1l3$4tg$1@ger.gmane.org>
References: <lba1l3$4tg$1@ger.gmane.org>
Date: Thu, 16 Jan 2014 17:52:39 -0800
Message-ID: <CALimQCWvM8tBKE7S5QNx68e=8eh3ouEMk9udv2ZWiXdue2zYhg@mail.gmail.com>
From: Ben Davenport <bendavenport@gmail.com>
To: =?ISO-8859-1?Q?D=E2niel_Fraga?= <fragabr@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b2e742c0d72ff04f020cc94
X-Spam-Score: -0.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
(bendavenport[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1W3yc1-0002PG-AD
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
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 01:52:46 -0000
--047d7b2e742c0d72ff04f020cc94
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
You can create a transaction which spends the output to yourself, attaching
a fee to that transaction. In order for miners to grab the transaction fee
on that transaction, they would have to also mine the original transaction.
Likely, you'd have to do this by hand, but software could be written to
simplify doing it. No protocol changes needed.
Ben
On Thu, Jan 16, 2014 at 5:39 PM, D=E2niel Fraga <fragabr@gmail.com> wrote:
> 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/3cde47ee3979a46b36bd61bdb0caf9c11dea58ac99f=
17fb17b95728766de70e0
>
> 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
>
>
>
>
> -------------------------------------------------------------------------=
-----
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=3D119420431&iu=3D/4140/ostg=
.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7b2e742c0d72ff04f020cc94
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">You can create a transaction which spends the output to yo=
urself, attaching a fee to that transaction. In order for miners to grab th=
e transaction fee on that transaction, they would have to also mine the ori=
ginal transaction. Likely, you'd have to do this by hand, but software =
could be written to simplify doing it. No protocol changes needed.<div>
<br></div><div>Ben</div></div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Thu, Jan 16, 2014 at 5:39 PM, D=E2niel Fraga <span dir=
=3D"ltr"><<a href=3D"mailto:fragabr@gmail.com" target=3D"_blank">fragabr=
@gmail.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">=A0 =A0 =A0 =A0 Someone sent me a very small=
donation (0.00121 BTC) without<br>
paying fees. I don't know who sent it and I know this type of<br>
transaction are usually rejected by miners. Take a look at it below:<br>
<br>
<a href=3D"https://imageshack.com/i/ngv5g8j" target=3D"_blank">https://imag=
eshack.com/i/ngv5g8j</a><br>
<br>
=A0 =A0 =A0 =A0 Even with the a low probability of confirmation, I<br>
was hoping that after a few days it could be included in a block, but<br>
Blockchain.info simply removed it (I know the sender sent from a<br>
Blockchain.info wallet, because he added a note):<br>
<br>
<a href=3D"https://blockchain.info/pt/tx/3cde47ee3979a46b36bd61bdb0caf9c11d=
ea58ac99f17fb17b95728766de70e0" target=3D"_blank">https://blockchain.info/p=
t/tx/3cde47ee3979a46b36bd61bdb0caf9c11dea58ac99f17fb17b95728766de70e0</a><b=
r>
<br>
=A0 =A0 =A0 =A0 As you can see now it shows as "Transaction not found&=
quot;.<br>
<br>
=A0 =A0 =A0 =A0 My suggestion is: it would be nice if the receiver could ha=
ve a<br>
chance to pay the fee when the sender didn't pay any fee. For example,<=
br>
I could pay a fee of 0.0001 BTC and receive 0.00121 BTC. In the end I'd=
<br>
have 0.00111 BTC. Better than nothing.<br>
<br>
=A0 =A0 =A0 =A0 Would it be technically possible to do that or it would be =
too<br>
much trouble to change the protocol to allow the receiver to pay an<br>
optional fee?<br>
<br>
=A0 =A0 =A0 =A0 Ps: I'm not a programmer, but if the receiver could<br>
optionally "attach" some fee to the transaction, even if he/she d=
idn't<br>
sent the transaction, this could be solved. Bitcoin-qt could even warn<br>
the receiver he received a transaction without fee and if he wants<br>
faster confirmation he could pay a fee.<br>
<br>
=A0 =A0 =A0 =A0 Ps2: if this is a silly suggestion, just ignore it. I tried=
on<br>
Bitcointalk, but nobody answered.<br>
<br>
--<br>
Linux 3.12.0: One Giant Leap for Frogkind<br>
<a href=3D"http://www.youtube.com/DanielFragaBR" target=3D"_blank">http://w=
ww.youtube.com/DanielFragaBR</a><br>
<a href=3D"http://mcxnow.com" target=3D"_blank">http://mcxnow.com</a><br>
Bitcoin: 12H6661yoLDUZaYPdah6urZS5WiXwTAUgL<br>
<br>
<br>
<br>
---------------------------------------------------------------------------=
---<br>
CenturyLink Cloud: The Leader in Enterprise Cloud Services.<br>
Learn Why More Businesses Are Choosing CenturyLink Cloud For<br>
Critical Workloads, Development Environments & Everything In Between.<b=
r>
Get a Quote or Start a Free Trial Today.<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D119420431&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D119420431&iu=3D/4140/ostg.clktrk</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div>
--047d7b2e742c0d72ff04f020cc94--
|
