From: "Jorge Timón" <jtimon@jtimon.cc>
To: Luke-Jr <luke@dashjr.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Fill-or-kill transaction
Date: Sat, 19 Sep 2015 07:09:23 +0200 [thread overview]
Message-ID: <CABm2gDo0XBXL7SNwZmXJJKQO6-MmCtmwcFJat-bkp6_8Ue4Y3A@mail.gmail.com> (raw)
In-Reply-To: <201509190201.01455.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
How them being expensive to generate make them less likely to be reorged?
Would an op_return output used as a nonce to make the hash of the
transaction contain some proof of work make the non-coinbase expirable
transaction more secure against reorgs?
I'm afraid your point is irrelevant.
On Sep 19, 2015 4:01 AM, "Luke Dashjr" <luke@dashjr.org> wrote:
> On Thursday, September 17, 2015 7:14:38 PM Jorge Timón via bitcoin-dev
> wrote:
> > 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
> maturity requirement, but *also* are expensive to generate.
> Mere OP_CHECKMATURITYVERIFY (aka rcltv) has no cost to use...
>
> Luke
>
[-- Attachment #2: Type: text/html, Size: 1148 bytes --]
next prev parent reply other threads:[~2015-09-19 5:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 18:41 [bitcoin-dev] Fill-or-kill transaction jl2012
2015-09-17 19:07 ` Mark Friedenbach
2015-09-17 19:14 ` Jorge Timón
2015-09-17 22:44 ` Peter Todd
2015-09-18 3:27 ` jl2012
2015-09-18 6:42 ` Btc Drak
2015-09-18 9:12 ` jl2012
2015-09-19 15:31 ` Tom Harding
2015-09-18 13:08 ` Jorge Timón
2015-09-22 17:45 ` Jorge Timón
2015-09-19 2:01 ` Luke Dashjr
2015-09-19 5:09 ` Jorge Timón [this message]
2015-09-17 19:12 ` Btc Drak
2015-09-17 22:33 ` Chun Wang
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=CABm2gDo0XBXL7SNwZmXJJKQO6-MmCtmwcFJat-bkp6_8Ue4Y3A@mail.gmail.com \
--to=jtimon@jtimon.cc \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=luke@dashjr.org \
/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