--- Log opened Mon Jul 26 00:00:17 2021 --- Log opened Mon Jul 26 00:27:26 2021 00:27 -!- gnusha [~gnusha@user/gnusha] has joined ##miniscript 00:27 [Users ##miniscript] 00:27 [@andytoshi] [ amanr ] [ gnusha ] [ meshcollider ] [ sanket1729 ] 00:27 [@sipa ] [ darosior ] [ hugohn ] [ michaelfolkson] [ sanket_cell_] 00:27 [ _0x0ff ] [ enick_49711] [ jnewbery] [ paairs ] [ sebx2a ] 00:27 [ achow101 ] [ FelixWeis ] [ kalle ] [ robertspigler ] 00:27 -!- Irssi: ##miniscript: Total of 19 nicks [2 ops, 0 halfops, 0 voices, 17 normal] 00:28 -!- Channel ##miniscript created Thu May 20 00:29:16 2021 00:30 -!- Irssi: Join to ##miniscript was synced in 163 secs 01:07 < darosior> sanket1729: re the discussion on #41, what was the rationale behind making miniscripts with timelock conflicts well-typed? 01:09 < sanket1729> darosior: Just to allow more expression power for miniscripts. 01:10 < sanket1729> Even if there is one path containing such conflict, it does not rule out other script satisfaction paths 01:10 < sanket1729> similar to how we don't rule out miniscripts that might contain a satisfaction path which require more than 200 opcodes 01:10 < darosior> Yeah, makes sense 02:27 < sanket1729> sipa: bitcoin core would allow descriptors of the form tr(03). Is this intentional or is it a bug? 02:27 < sanket1729> I am using importdescriptors in watch only mode wallet 06:50 -!- roconnor [~roconnor@host-45-78-208-14.dyn.295.ca] has joined ##miniscript 07:39 <@sipa> sanket1729: yes 07:44 < sanket1729> So, that would just not map to any valid taproot address/scriptpubkey. But is allowed 07:44 <@sipa> the 03 is ignored 07:44 <@sipa> similar to how xpub derivation is handled 07:45 <@sipa> if that happens to land on an odd-y key that's also fine; only the x part is considered part of the public key 07:45 < sanket1729> understood 08:33 -!- dr-orlovsky [~dr-orlovs@31.14.40.18] has joined ##miniscript 22:42 -!- roconnor [~roconnor@host-45-78-208-14.dyn.295.ca] has quit [Ping timeout: 265 seconds] --- Log closed Tue Jul 27 00:00:21 2021