public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP: Voluntary deposit bonds
Date: Mon, 29 Dec 2014 22:36:48 +0000	[thread overview]
Message-ID: <201412292236.49596.luke@dashjr.org> (raw)
In-Reply-To: <CANEZrP0zVTVdDWZCUk9wvcuAjBi4Eq+a8SQP4-R5aKrxDw_xMA@mail.gmail.com>

On Monday, December 29, 2014 9:10:20 PM Mike Hearn wrote:
> How does adding inputs to a coinbase differ from just having pay-to-fee
> transactions in the block?

Pay-to-fee transactions can be "stolen" by another block at the same or 
greater height. Additional inputs to the generation transaction are tied to 
that block alone.

Luke



  parent reply	other threads:[~2014-12-29 22:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29 19:21 [Bitcoin-development] BIP: Voluntary deposit bonds Sergio Lerner
2014-12-29 21:10 ` Mike Hearn
2014-12-29 21:34   ` Justus Ranvier
2014-12-30 10:47     ` Jorge Timón
2014-12-30 13:16       ` Justus Ranvier
2014-12-29 22:36   ` Luke Dashjr [this message]
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=201412292236.49596.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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