From: Peter Todd <pete@petertodd•org>
To: Eric Lombrozo <elombrozo@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Alternative name for CHECKSEQUENCEVERIFY (BIP112)
Date: Thu, 26 Nov 2015 17:25:56 -0500 [thread overview]
Message-ID: <20151126222556.GC6550@savin.petertodd.org> (raw)
In-Reply-To: <523E7E80-A958-4333-96FB-1E0D36BB128F@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
On Thu, Nov 26, 2015 at 01:32:58PM -0800, Eric Lombrozo via bitcoin-dev wrote:
> After a little more though (and some comments from aj), I realize that the opcode naming convention is actually CHECK <condition > VERIFY.
>
> Therefore, the full opcode name should be CHECKRELATIVELOCKTIMEVERIFY.
>
> However, this name is ridiculously long, so at least some part will require abbreviation.
>
> In typical script example usage, most sensible seems to be to abbreviate both CLTV and CRLTV.
...and CRLTV is hard to visually distinguish from CLTV. :(
You know, calling it AGEVERIFY is short and sweet.
--
'peter'[:-1]@petertodd.org
00000000000000000ef246c814f8cb8c1a26bc3c6cb1286bdbc5f4140ed3fc79
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-11-26 22:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 10:30 Btc Drak
2015-11-24 12:20 ` Peter Todd
2015-11-24 12:35 ` Jorge Timón
2015-11-24 12:31 ` Jorge Timón
2015-11-25 1:14 ` Eric Lombrozo
2015-11-26 21:32 ` Eric Lombrozo
2015-11-26 22:25 ` Peter Todd [this message]
2015-11-25 23:05 ` Mark Friedenbach
2015-11-25 23:41 ` Eric Lombrozo
2015-11-26 22:23 ` Matt Corallo
2015-11-27 4:02 ` Rusty Russell
2015-11-27 8:10 ` Eric Lombrozo
2015-11-27 4:08 ` Dave Scotese
2015-11-27 10:14 ` Jorge Timón
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=20151126222556.GC6550@savin.petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=elombrozo@gmail$(echo .)com \
/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