From: Gregory Maxwell <gmaxwell@gmail•com>
To: Sergio Lerner <sergiolerner@certimix•com>
Cc: bitcoin-development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP: Voluntary deposit bonds
Date: Tue, 30 Dec 2014 04:51:51 +0000 [thread overview]
Message-ID: <CAAS2fgSvq_Tnon1C+xED06VYPizj+XTiDu0xm0MvCg_9-ejcjA@mail.gmail.com> (raw)
In-Reply-To: <54A1A99E.1020604@certimix.com>
On Mon, Dec 29, 2014 at 7:21 PM, Sergio Lerner
<sergiolerner@certimix•com> wrote:
> I propose to allow miners to voluntarily lock funds by letting miners
> add additional inputs to the coinbase transaction. Currently the
> coinbase transaction does not allow any real input to be added (only a
> pseudo-input).
> This is a hard-fork, and we could include it the next time a hardfork is
> made.
> The modifications to the code are minimal (no more than 12 lines
> modified where IsCoinBase() is called), and they generally involve
> removing code, not adding.
If the motivation is purely enabling different rules in a soft-fork
than I think nothing needs to be done.
Instead of providing inputs to a coinbase: you provide an unusual
anyone can spend transaction in the block which pays to fees; and
simultaneously add a soft-forking rule that makes that anyone can
spend rule no longer anyone can spend.
To make that more concrete. E.g. You make your anyone can spend
output "PUSH<hash of coinbase output script_pubkeys> OP_NOP3". Now
this anyone can pay transaction is really just a coinbase input.
The construction is reasonably efficient, and also more flexible-- in
that it could control the data under the hash in more flexible ways
than available in the existing sighash flags.
As an aside, I'm not sure that I agree with the claim that making
coinbases have inputs is a simple modification... as we use one of the
inputs already as the special coinbase field and at least that must be
special cased.
next prev parent reply other threads:[~2014-12-30 4:51 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
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 [this message]
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=CAAS2fgSvq_Tnon1C+xED06VYPizj+XTiDu0xm0MvCg_9-ejcjA@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=sergiolerner@certimix$(echo .)com \
/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