From: Justus Ranvier <justus.ranvier@monetas.net>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP: Voluntary deposit bonds
Date: Mon, 29 Dec 2014 21:34:07 +0000 [thread overview]
Message-ID: <54A1C8CF.50907@monetas.net> (raw)
In-Reply-To: <CANEZrP0zVTVdDWZCUk9wvcuAjBi4Eq+a8SQP4-R5aKrxDw_xMA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
-----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.
- --
Justus Ranvier | Monetas <http://monetas.net/>
<mailto:justus@monetas.net> | Public key ID : C3F7BB2638450DB5
| BM-2cTepVtZ6AyJAs2Y8LpcvZB8KbdaWLwKqc
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCAAGBQJUocjPAAoJEMP3uyY4RQ21zrMH/1f3vjac9XqOZbDItjiD6XXU
EkpRUROjyQAs6/tO6dwWAIcXgulYREAJsU/udQNkTYteIDFlDzwkYL+NLXpYtwHs
BiZJEEwmAEHFgOD3QmmqhTx867zIbEYIB/dpHlMOppE6fhTKFr9z6JdqAKlNcHHW
tkW5sq8q9uq7StiUs3/mmZ0XXeEb84N+bPiJ9S7kuTm9QWnrF1oMLhAk4M6yX8hn
7MUowmfc9RZ4uIFkqxk6gkWJSRx7dlnCRP2TRhyABpZwAcZANuPhqBOZ6eJ6T9Fs
DOJ14c5JYachXW5z8GqR+abeq0JPE76kEQt145B4degJ4DTQLLhlfdvjbuJvzy4=
=Kfe2
-----END PGP SIGNATURE-----
[-- Attachment #2: 0x38450DB5.asc --]
[-- Type: application/pgp-keys, Size: 14542 bytes --]
next prev parent reply other threads:[~2014-12-29 22:36 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 [this message]
2014-12-30 10:47 ` Jorge Timón
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=54A1C8CF.50907@monetas.net \
--to=justus.ranvier@monetas.net \
--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