From: "Jorge Timón" <jtimon@jtimon•cc>
To: Justus Ranvier <justus.ranvier@monetas•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP: Voluntary deposit bonds
Date: Tue, 30 Dec 2014 11:47:46 +0100 [thread overview]
Message-ID: <CABm2gDo4XFvcYhwhiTu3L8Hf6dQMohSk5GE2dg8wQWky1iuS1w@mail.gmail.com> (raw)
In-Reply-To: <54A1C8CF.50907@monetas.net>
On Mon, Dec 29, 2014 at 10:34 PM, Justus Ranvier
<justus.ranvier@monetas•net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 12/29/2014 09:10 PM, Mike Hearn wrote:
>> How does adding inputs to a coinbase differ from just having
>> pay-to-fee transactions in the block?
>
> If a miner includes pay-to-fee transactions in a block, those fees
> could be claimed by another miner in the case the first miner's block
> is orphaned.
>
> Inputs to a generation transaction can not be similarly poached.
>
> That difference makes some services possible that would can not be
> safely achieved with pay-to-fee transactions.
What services?
I must be missing something obvious about the motivation.
I understand the difference between "paying to myself only when I mine
the next block" and "offering fees to whoever mines this tx".
But how does allowing miners to pay to themselves in this way help
with security and future lower subsidies at all?
next prev parent reply other threads:[~2014-12-30 10:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 19:21 Sergio Lerner
2014-12-29 21:10 ` Mike Hearn
2014-12-29 21:34 ` Justus Ranvier
2014-12-30 10:47 ` Jorge Timón [this message]
2014-12-30 13:16 ` Justus Ranvier
2014-12-29 22:36 ` Luke Dashjr
2014-12-29 22:35 ` Luke Dashjr
2014-12-30 4:51 ` Gregory Maxwell
2014-12-30 16:25 ` Sergio Lerner
2014-12-30 18:28 ` Gregory Maxwell
2014-12-31 18:25 ` Stephen Morse
2015-01-03 3:48 ` Peter Todd
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=CABm2gDo4XFvcYhwhiTu3L8Hf6dQMohSk5GE2dg8wQWky1iuS1w@mail.gmail.com \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=justus.ranvier@monetas$(echo .)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