Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <mh.in.england@gmail.com>) id 1Y5haJ-000279-DF for bitcoin-development@lists.sourceforge.net; Mon, 29 Dec 2014 21:10:39 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=mh.in.england@gmail.com; helo=mail-we0-f175.google.com; Received: from mail-we0-f175.google.com ([74.125.82.175]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Y5ha6-0002Hi-HH for bitcoin-development@lists.sourceforge.net; Mon, 29 Dec 2014 21:10:38 +0000 Received: by mail-we0-f175.google.com with SMTP id k11so116214wes.34 for <bitcoin-development@lists.sourceforge.net>; Mon, 29 Dec 2014 13:10:20 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.92.116 with SMTP id cl20mr116795206wjb.71.1419887420536; Mon, 29 Dec 2014 13:10:20 -0800 (PST) Sender: mh.in.england@gmail.com Received: by 10.194.188.9 with HTTP; Mon, 29 Dec 2014 13:10:20 -0800 (PST) In-Reply-To: <54A1A99E.1020604@certimix.com> References: <54A1A99E.1020604@certimix.com> Date: Mon, 29 Dec 2014 21:10:20 +0000 X-Google-Sender-Auth: Gv8q2idX32atCi4zf7BrDps4Zk8 Message-ID: <CANEZrP0zVTVdDWZCUk9wvcuAjBi4Eq+a8SQP4-R5aKrxDw_xMA@mail.gmail.com> From: Mike Hearn <mike@plan99.net> To: Sergio Lerner <sergiolerner@certimix.com> Content-Type: multipart/alternative; boundary=047d7bd910c252803d050b614dcb X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Y5ha6-0002Hi-HH Cc: bitcoin-development <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] BIP: Voluntary deposit bonds X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Mon, 29 Dec 2014 21:10:39 -0000 --047d7bd910c252803d050b614dcb Content-Type: text/plain; charset=UTF-8 Could you explain a bit further Sergio? I'm not sure I fully understand the proposal. How does adding inputs to a coinbase differ from just having pay-to-fee transactions in the block? --047d7bd910c252803d050b614dcb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_extra">Could you explain a bit further= Sergio? I'm not sure I fully understand the proposal.</div><div class= =3D"gmail_extra"><br></div><div class=3D"gmail_extra">How does adding input= s to a coinbase differ from just having pay-to-fee transactions in the bloc= k?</div></div> --047d7bd910c252803d050b614dcb--