{"type":"rich","version":"1.0","author_name":"npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","author_url":"https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-11-26\n📝 Original message:On Thu, Nov 26, 2015 at 01:32:58PM -0800, Eric Lombrozo via bitcoin-dev wrote:\n\u003e After a little more though (and some comments from aj), I realize that the opcode naming convention is actually CHECK \u003ccondition \u003e VERIFY.\n\u003e \n\u003e Therefore, the full opcode name should be CHECKRELATIVELOCKTIMEVERIFY.\n\u003e \n\u003e However, this name is ridiculously long, so at least some part will require abbreviation.\n\u003e \n\u003e In typical script example usage, most sensible seems to be to abbreviate both CLTV and CRLTV.\n\n...and CRLTV is hard to visually distinguish from CLTV. :(\n\nYou know, calling it AGEVERIFY is short and sweet.\n\n-- \n'peter'[:-1]@petertodd.org\n00000000000000000ef246c814f8cb8c1a26bc3c6cb1286bdbc5f4140ed3fc79\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 650 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151126/47f980c2/attachment.sig\u003e"}