From: "Jorge Timón" <jtimon@jtimon.cc>
To: Btc Drak <btcdrak@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Alternative name for CHECKSEQUENCEVERIFY (BIP112)
Date: Tue, 24 Nov 2015 13:31:55 +0100 [thread overview]
Message-ID: <CABm2gDqoq4pkXLS=4rKGOLGU0_0mq1_yMOHmLw73m=apiMRMpg@mail.gmail.com> (raw)
In-Reply-To: <CADJgMzs0w4L7ma42RCzT5dYDcG2aY1_04G1khcFPFPE6mmB=-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
I agree, I believe the first name that an op with equivalent functionality
had was simply op_maturity.
At least I remember we discussed such an opcode when discussing pegged
sidechains' design.
I kind of dislike the check_x_verify naming pattern. We want all new
operands to return if whatever they're checking/verifying fails, fine. Do
we have to repeat this redundant naming pattern forever due to that
discovery?
I hope not, but if that's the case my vote is for CMV.
As said before, I believe the documentation and code comments can become
much more clear with this change.
[-- Attachment #2: Type: text/html, Size: 636 bytes --]
next prev parent reply other threads:[~2015-11-24 12:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 10:30 [bitcoin-dev] Alternative name for CHECKSEQUENCEVERIFY (BIP112) 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 [this message]
2015-11-25 1:14 ` Eric Lombrozo
2015-11-26 21:32 ` Eric Lombrozo
2015-11-26 22:25 ` Peter Todd
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='CABm2gDqoq4pkXLS=4rKGOLGU0_0mq1_yMOHmLw73m=apiMRMpg@mail.gmail.com' \
--to=jtimon@jtimon.cc \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=btcdrak@gmail.com \
/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