--- Log opened Mon Jul 17 00:00:03 2023
03:27 -!- jonatack1 [~jonatack@user/jonatack] has quit [Ping timeout: 245 seconds]
04:44 -!- jonatack1 [~jonatack@user/jonatack] has joined ##miniscript
06:00 -!- jonatack2 [~jonatack@user/jonatack] has joined ##miniscript
06:00 -!- jonatack1 [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
06:12 -!- salvatoshi [~salvatosh@genymobile-2-6-86.fib.nerim.net] has joined ##miniscript
09:13 -!- salvatoshi [~salvatosh@genymobile-2-6-86.fib.nerim.net] has quit [Ping timeout: 245 seconds]
09:14 -!- jonatack2 [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
09:15 -!- jonatack3 [~jonatack@user/jonatack] has joined ##miniscript
12:13 <@sipa> darosior: I think we're still talking past each other regarding IsSane()
12:15 <@sipa> If a miniscript has a timelock and no public key, then there is potentially nothing committing to the nSequence value, for example, and thus an attacker can set the nSequence value to whatever they want. In that sense, it doesn't match its apparent policy, because nothing constrains the nSequence.
12:18 <@sipa> It's a bit further removed from the usual properties miniscript looks at, as they're per-input-script, and this is really a whole-transaction concern, but IIRC, that's the rationale for wanting signatures for IsSane
12:19 <@sipa> And it's independent from malleability; that's a concern too that inevitably exists for non-signed satisfactions. But here it's really about the fact that the "after(N)" doesn't restrict anything if an attacker can set it to whatever they want.
13:58 < jeremyrubin> sipa: AND(after(N), Key(Well Known PK))
13:59 < jeremyrubin> you can 'defeat' the issane restriction with that, so really the checking for signed-ness is relying on the key actually being secret
14:01 <@sipa> Sure, but that's true for any reasoning about policy.
14:02 <@sipa> If you include any well-known key in a miniscript, its effective policy will not match the apparent one.
15:57 -!- sanket1729_ [~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com] has quit [Read error: Connection reset by peer]
15:58 -!- sanket_cell [~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com] has quit [Ping timeout: 264 seconds]
16:00 -!- sanket1729 [~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com] has joined ##miniscript
16:00 -!- sanket_cell [~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com] has joined ##miniscript
--- Log closed Tue Jul 18 00:00:03 2023