From: "Dâniel Fraga" <fragabr@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Suggestion: allow receivers to pay optional fee for transactions without fees
Date: Fri, 17 Jan 2014 00:06:13 -0200 [thread overview]
Message-ID: <lba369$sp9$1@ger.gmane.org> (raw)
In-Reply-To: <CALimQCWvM8tBKE7S5QNx68e=8eh3ouEMk9udv2ZWiXdue2zYhg@mail.gmail.com>
This is good news! Thank you very much Ben for the answer.
On Thu, 16 Jan 2014 17:52:39 -0800
Ben Davenport <bendavenport@gmail•com> wrote:
> 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âniel 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/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
> >
> >
> >
> >
> > ------------------------------------------------------------------------------
> > 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=119420431&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists•sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> >
>
--
Linux 3.12.0: One Giant Leap for Frogkind
http://www.youtube.com/DanielFragaBR
http://mcxnow.com
Bitcoin: 12H6661yoLDUZaYPdah6urZS5WiXwTAUgL
next prev parent reply other threads:[~2014-01-17 2:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 1:39 Dâniel Fraga
2014-01-17 1:52 ` Ben Davenport
2014-01-17 2:06 ` Dâniel Fraga [this message]
2014-01-17 2:39 ` Christophe Biocca
2014-01-17 5:40 ` Luke-Jr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='lba369$sp9$1@ger.gmane.org' \
--to=fragabr@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox