From: Rusty Russell <rusty@rustcorp•com.au>
To: Btc Drak <btcdrak@gmail•com>, jl2012@xbt•hk
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] [BIP-draft] CHECKSEQUENCEVERIFY - An opcode for relative locktime
Date: Thu, 27 Aug 2015 12:38:42 +0930 [thread overview]
Message-ID: <87k2shig1x.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CADJgMzsLU5tQDLp0NWDwE6S476PdwvrOWOpn8oQ+5JPyoyi8gQ@mail.gmail.com>
Btc Drak via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> writes:
> This BIP has been assigned BIP112 by the BIP repository maintainer. I
> have updated the pull request accordingly.
>
> Regarding the suggestion to cannibalise version, by your own
> disadvantage list, we would lose fine grained control over txins which
> neuters the usefulness considerably. Also using version is also ugly
> because there isn't a semantic association with what we are trying to
> do, whereas, sequence is associated with transaction finality and is
> thus the more appropriate and logical field to use.
OK, having implemented lightning test code against the initial proposal,
I can give the following anecdata:
- I screwed up inversion in my initial implementation. Please kill it.
- 256 second granularity would be be fine in deployment, but a bit
painful for testing (I currently use 60 seconds, and "sleep 61"). 64
would work better for me, and works roughly as minutes.
- 1 year should be sufficient as a max; my current handwave is <= 1 day
per lightning hop, max 12 hops, though we have no deployment data.
- We should immediately deploy an IsStandard() rule which insists that
nSequence is 0xFFFFFFFF or 0, so nobody screws themselves when we
soft fork and they had random junk in there.
Aside: I'd also like to have nLockTime apply even if nSequence !=
0xFFFFFFFF (another mistake I made). So I'd like an IsStandard() rule
to say it nLockTime be 0 if an nSequence != 0xFFFFFFFF. Would that
screw anyone currently?
Thanks,
Rusty.
next prev parent reply other threads:[~2015-08-27 3:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 11:06 Btc Drak
2015-08-13 18:12 ` Mark Friedenbach
2015-08-13 19:20 ` Gregory Maxwell
2015-08-13 23:42 ` Joseph Poon
2015-08-14 0:47 ` Mark Friedenbach
2015-08-14 18:53 ` Matt Corallo
2015-08-14 21:29 ` Mark Friedenbach
2015-08-14 22:24 ` Jorge Timón
2015-08-17 19:58 ` Btc Drak
2015-08-19 10:37 ` Jorge Timón
2015-08-19 16:21 ` Mark Friedenbach
2015-08-19 21:27 ` Joseph Poon
2015-08-19 21:32 ` Jorge Timón
2015-08-20 21:23 ` Peter Todd
2015-08-24 0:25 ` Tom Harding
2015-08-24 1:01 ` Gregory Maxwell
2015-08-24 2:23 ` Jorge Timón
2015-08-24 2:37 ` Mark Friedenbach
2015-08-25 22:08 ` Mark Friedenbach
2015-08-25 22:36 ` Tier Nolan
2015-08-27 23:32 ` Mark Friedenbach
2015-09-16 22:40 ` Btc Drak
2015-09-16 23:23 ` Eric Lombrozo
2015-09-17 4:23 ` Mark Friedenbach
2015-09-18 1:21 ` Rusty Russell
2015-09-17 7:43 ` jl2012
2015-08-24 2:40 ` jl2012
2015-08-24 2:54 ` Mark Friedenbach
2015-08-24 7:00 ` jl2012
2015-08-25 10:15 ` Btc Drak
2015-08-27 3:08 ` Rusty Russell [this message]
2015-08-27 11:03 ` David A. Harding
2015-08-27 12:29 ` jl2012
2015-08-30 21:33 ` Rusty Russell
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=87k2shig1x.fsf@rustcorp.com.au \
--to=rusty@rustcorp$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=btcdrak@gmail$(echo .)com \
--cc=jl2012@xbt$(echo .)hk \
/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