--- Log opened Wed Jan 08 00:00:42 2025
01:45 -!- jdlcdl [~jdlcdl@apointe-a-pitre-651-1-82-116.w90-36.abo.wanadoo.fr] has joined ##miniscript
02:42 < jdlcdl> I have a question about how op_cltv works when an absolute timestamp is on top of stack and nLockTime is 0 or a recent blockheight.  Bip65 implies that script would error out, even if current time were greater than top of stack -- because top-of-stack and nLockTime are not the same 'locktime type'.  Is my understanding correct?
02:55 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
02:55 -!- jonatack [~jonatack@user/jonatack] has joined ##miniscript
03:05 < darosior> jdlcdl: yes. See also "detecting timelock mixing" in the Miniscript BIP and at https://bitcoin.sipa.be/miniscript/
03:07 < jdlcdl> Thank you
06:19 -!- pyth [~pyth@ppp-124-120-8-32.revip2.asianet.co.th] has joined ##miniscript
09:07 -!- pyth [~pyth@ppp-124-120-8-32.revip2.asianet.co.th] has quit [Ping timeout: 276 seconds]
09:47 -!- jdlcdl [~jdlcdl@apointe-a-pitre-651-1-82-116.w90-36.abo.wanadoo.fr] has quit [Quit: Leaving]
11:18 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: WeeChat 4.5.0]
11:28 -!- jonatack [~jonatack@user/jonatack] has joined ##miniscript
12:53 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: WeeChat 4.5.1]
12:59 -!- jonatack [~jonatack@user/jonatack] has joined ##miniscript
13:10 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: WeeChat 4.5.1]
13:13 -!- jonatack [~jonatack@user/jonatack] has joined ##miniscript
16:13 -!- andytoshi [~apoelstra@user/andytoshi] has quit [Quit: Lost terminal]
19:36 -!- andytoshi [~apoelstra@user/andytoshi] has joined ##miniscript
22:31 -!- jdlcdl [~jdlcdl@apointe-a-pitre-651-1-82-116.w90-36.abo.wanadoo.fr] has joined ##miniscript
--- Log closed Thu Jan 09 00:00:44 2025