From: Stephen Morse <stephencalebmorse@gmail•com>
To: Adam Back <adam@cypherspace•org>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] [BIP draft] Consensus-enforced transaction replacement signalled via sequence numbers
Date: Tue, 2 Jun 2015 10:10:30 -0400 [thread overview]
Message-ID: <CABHVRKRympU4LAeD7xG9bX3PvWMNcJaa1RMff+fukn0wSRr81A@mail.gmail.com> (raw)
In-Reply-To: <CALqxMTFkWOfWXOnVAnZESkVWHtbZLc=T_sQDoTofr66mcb6_gQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
>
> That would also introduce the anomaly of a script that was once valid
> becoming later invalid, when nothing varies other than time. That is
> not super compatible with the current model of reprocessing
> transactions in later blocks if the block they were first in gets
> reorged.
>
Very good point.
>
> (Not a huge flexibility loss as you can implement "not after" by
> making it the previous holders responsibility to spend a "not before"
> back to themselves.)
>
Do you mean something like the below?
scriptPubKey:
IF
{A's pub} CHECKSIGVERIFY
ELSE
{curr_height + 100} CLTV {B's pub} CHECKSIGVERIFY
This ensures that Alice has to spend the output in the next 100 blocks or
risk it being taken from her (she just has to put an OP_TRUE on the end of
her scriptSig). So, it seems we can forget about an inverted CLTV/CSV,
great!
Best,
Stephen
[-- Attachment #2: Type: text/html, Size: 1839 bytes --]
next prev parent reply other threads:[~2015-06-02 14:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 1:49 Mark Friedenbach
2015-06-02 3:45 ` Stephen Morse
2015-06-02 4:16 ` Mark Friedenbach
2015-06-02 4:34 ` Stephen Morse
2015-06-02 15:42 ` Tier Nolan
2015-06-02 12:52 ` Stephen
2015-06-02 13:11 ` Adam Back
2015-06-02 14:10 ` Stephen Morse [this message]
2015-06-02 15:44 ` Mark Friedenbach
2015-06-17 1:00 ` Mark Friedenbach
2015-06-17 1:20 ` Gregory Maxwell
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=CABHVRKRympU4LAeD7xG9bX3PvWMNcJaa1RMff+fukn0wSRr81A@mail.gmail.com \
--to=stephencalebmorse@gmail$(echo .)com \
--cc=adam@cypherspace$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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