diff options
author | Luke Dashjr <luke@dashjr.org> | 2015-09-19 02:01:00 +0000 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2015-09-19 02:01:52 +0000 |
commit | 48601e0420b176941f727e21c34da55fd3bbbcde (patch) | |
tree | f84a2317f5ddcfd45911b7125a0daf738aca6bb9 | |
parent | d0140c704858295f41d86deb6ec584b7b20c39c1 (diff) | |
download | pi-bitcoindev-48601e0420b176941f727e21c34da55fd3bbbcde.tar.gz pi-bitcoindev-48601e0420b176941f727e21c34da55fd3bbbcde.zip |
Re: [bitcoin-dev] Fill-or-kill transaction
-rw-r--r-- | ff/e738d6d72d1f74cd0cf022e2f72474aaffb0b0 | 66 |
1 files changed, 66 insertions, 0 deletions
diff --git a/ff/e738d6d72d1f74cd0cf022e2f72474aaffb0b0 b/ff/e738d6d72d1f74cd0cf022e2f72474aaffb0b0 new file mode 100644 index 000000000..83f2b73db --- /dev/null +++ b/ff/e738d6d72d1f74cd0cf022e2f72474aaffb0b0 @@ -0,0 +1,66 @@ +Return-Path: <luke@dashjr.org> +Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org + [172.17.192.35]) + by mail.linuxfoundation.org (Postfix) with ESMTPS id 94D4513C3 + for <bitcoin-dev@lists.linuxfoundation.org>; + Sat, 19 Sep 2015 02:01:52 +0000 (UTC) +X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 +Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21]) + by smtp1.linuxfoundation.org (Postfix) with ESMTP id 477ED1BA + for <bitcoin-dev@lists.linuxfoundation.org>; + Sat, 19 Sep 2015 02:01:52 +0000 (UTC) +Received: from ishibashi.localnet (unknown + [IPv6:2001:470:5:265:61b6:56a6:b03d:28d6]) + (Authenticated sender: luke-jr) + by zinan.dashjr.org (Postfix) with ESMTPSA id 75E4B1080053; + Sat, 19 Sep 2015 02:01:02 +0000 (UTC) +X-Hashcash: 1:25:150919:bitcoin-dev@lists.linuxfoundation.org::XtEIBVLqNPfJ+oh1:biRtf +X-Hashcash: 1:25:150919:jtimon@jtimon.cc::2mQIlAdb3pPuE=4W:awJzG +X-Hashcash: 1:25:150919:mark@friedenbach.org::xLQewdzd=lhCOf7b:vV0g +From: Luke Dashjr <luke@dashjr.org> +To: bitcoin-dev@lists.linuxfoundation.org, + Jorge =?iso-8859-15?q?Tim=F3n?= <jtimon@jtimon.cc> +Date: Sat, 19 Sep 2015 02:01:00 +0000 +User-Agent: KMail/1.13.7 (Linux/4.1.6-gentoo; KDE/4.14.8; x86_64; ; ) +References: <a50b82c156c805a284386d80a42cc926@xbt.hk> + <CAOG=w-vGqsAcw5vdY8SaGVe4Q6XX1J=GCsZftWgjES_N_5c2pA@mail.gmail.com> + <CABm2gDp_afyqskEV8QmO43=-6R_2OJm36GVQxcQO_3ao2jC1gw@mail.gmail.com> +In-Reply-To: <CABm2gDp_afyqskEV8QmO43=-6R_2OJm36GVQxcQO_3ao2jC1gw@mail.gmail.com> +X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F +X-PGP-Key-ID: BD02942421F4889F +X-PGP-Keyserver: hkp://pgp.mit.edu +MIME-Version: 1.0 +Content-Type: Text/Plain; + charset="iso-8859-15" +Content-Transfer-Encoding: quoted-printable +Message-Id: <201509190201.01455.luke@dashjr.org> +X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD + autolearn=ham version=3.3.1 +X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on + smtp1.linux-foundation.org +Subject: Re: [bitcoin-dev] Fill-or-kill transaction +X-BeenThere: bitcoin-dev@lists.linuxfoundation.org +X-Mailman-Version: 2.1.12 +Precedence: list +List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org> +List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> +List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> +List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> +List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> +List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> +X-List-Received-Date: Sat, 19 Sep 2015 02:01:52 -0000 + +On Thursday, September 17, 2015 7:14:38 PM Jorge Tim=F3n via bitcoin-dev wr= +ote: +> As Mark points out this can be made safe by requiring that all the outputs +> of a transaction that can expire have op_maturity/csv/rcltv of 100. That +> makes them as reorg-safe as coinbase transactions. + +Not quite as safe. Remember that mined bitcoins have not only a 100-block=20 +maturity requirement, but *also* are expensive to generate. +Mere OP_CHECKMATURITYVERIFY (aka rcltv) has no cost to use... + +Luke + |