馃搮 Original date posted:2014-11-27
馃摑 Original message:Heya,
I was wondering about BIP 65 regarding the OP_CHECKLOCKTIMEVERIFY, and thought it might make more sense to instead have a OP_CHECKLOCKTIME which would simply push an OP_TRUE or OP_FALSE onto the stack?
That way someone could include multiple OP_CHECKLOCKTIME conditions in a single script. It is trivial to always emulate OP_CHECKLOCKTIMEVERIFY by using a OP_CHECKLOCKTIME OP_VERIFY sequence.
As a second question, would it possibly make more sense to, rather than relying on the nLockTime in a transaction, allow an opcode that would use similar semantics, but against an item in the stack? Then you could essentially include multiple nLockTimes in a single script and make arbitrarily interesting (complicated?) scripts based on block height and/or block timestamp.
The OP_CHECKLOCKTIMEVERIFY can still be easily implemented, by using
nLockTimeThatWouldBeInTx OP_CHECKLOCKTIME OP_VERIFY
Just something that came to mind while reading about OP_CHECKLOCKTIMEVERIFY.
Thanks,
RicMoo
.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂><(((潞>
Richard Moore ~ Founder
Genetic Mistakes Software inc.
phone: (778) 882-6125
email: ricmoo at geneticmistakes.com <mailto:ricmoo at geneticmistakes.com>
www: http://GeneticMistakes.com <http://geneticmistakes.com/>;
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20141127/be90f9d6/attachment.html>;
Richard Moore [ARCHIVE] /
npub1rx鈥etyf
2023-06-07 15:27:37
in reply to nevent1q鈥z4v
Author Public Key
npub1rxqlcf4n2aw0urx6l4g7rjkyng8d5w0lkqphnaycrchyh3dwktzsejetyfPublished at
2023-06-07 15:27:37Event JSON
{
"id": "8403a3c6202fdb65f9c7e160bac4867965f41f59fbab62f1ac47d17cc2215c40",
"pubkey": "1981fc26b3575cfe0cdafd51e1cac49a0eda39ffb00379f4981e2e4bc5aeb2c5",
"created_at": 1686151657,
"kind": 1,
"tags": [
[
"e",
"99bba744eb2cf1c3395be4b6816ad01aa750a4d43915a19a11da272c80fbe683",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "馃搮 Original date posted:2014-11-27\n馃摑 Original message:Heya,\n\nI was wondering about BIP 65 regarding the OP_CHECKLOCKTIMEVERIFY, and thought it might make more sense to instead have a OP_CHECKLOCKTIME which would simply push an OP_TRUE or OP_FALSE onto the stack?\n\nThat way someone could include multiple OP_CHECKLOCKTIME conditions in a single script. It is trivial to always emulate OP_CHECKLOCKTIMEVERIFY by using a OP_CHECKLOCKTIME OP_VERIFY sequence.\n\n\nAs a second question, would it possibly make more sense to, rather than relying on the nLockTime in a transaction, allow an opcode that would use similar semantics, but against an item in the stack? Then you could essentially include multiple nLockTimes in a single script and make arbitrarily interesting (complicated?) scripts based on block height and/or block timestamp.\n\nThe OP_CHECKLOCKTIMEVERIFY can still be easily implemented, by using\n\nnLockTimeThatWouldBeInTx OP_CHECKLOCKTIME OP_VERIFY\n\n\nJust something that came to mind while reading about OP_CHECKLOCKTIMEVERIFY.\n\nThanks,\n\nRicMoo\n\n.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂\u003e\u003c(((潞\u003e\n\nRichard Moore ~ Founder\nGenetic Mistakes Software inc.\nphone: (778) 882-6125\nemail: ricmoo at geneticmistakes.com \u003cmailto:ricmoo at geneticmistakes.com\u003e\nwww: http://GeneticMistakes.com \u003chttp://geneticmistakes.com/\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20141127/be90f9d6/attachment.html\u003e",
"sig": "a7bf8e76ae2cb22ea62a40160f4f486f8bd06e742cf1287f3e443b6ad814f44293a101be5486ef84008d8a08d9d3b6e1d37e8cf2609020521ede2d7cc9c6507b"
}