--- Log opened Sat Mar 05 00:00:17 2022 00:00 -!- shesek [~shesek@164.90.217.137] has joined #bitcoin-wizards 00:01 -!- shesek [~shesek@164.90.217.137] has quit [Changing host] 00:01 -!- shesek [~shesek@user/shesek] has joined #bitcoin-wizards 00:58 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has joined #bitcoin-wizards 01:17 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…] 02:03 -!- kexkey [~kexkey@static-198-54-132-136.cust.tzulo.com] has quit [Ping timeout: 252 seconds] 02:05 -!- kexkey [~kexkey@static-198-54-132-88.cust.tzulo.com] has joined #bitcoin-wizards 02:06 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-wizards 02:15 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Quit: Leaving...] 02:38 -!- jonatack [jonatack@user/jonatack] has quit [Ping timeout: 272 seconds] 02:40 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has joined #bitcoin-wizards 03:43 -!- dllud [~dllud@136.138.62.94.rev.vodafone.pt] has quit [Read error: Connection reset by peer] 03:44 -!- dllud [~dllud@136.138.62.94.rev.vodafone.pt] has joined #bitcoin-wizards 04:30 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has left #bitcoin-wizards [Closing Window] 04:30 < jeremyrubin> i probably should have included that, i'm aware (and working on!) that problem in miniscript :) 04:31 < jeremyrubin> roconnor_: but it goes deeper than that since if the annex is to be used for a cost of validation hint things get funky, so you kind of either need to pick things like locktimes and allow it on the stack or validation costs and then not allow it 04:31 < jeremyrubin> So i think that we *cannot* use the annex for validation cost hints since it already winds up on the stack through sigs 04:31 < jeremyrubin> instead, we should make annex2.0 be for cost hints 04:32 < jeremyrubin> (annex for validation cost hints + on the stack = undecidability for satisfiers) 04:34 < jeremyrubin> simple example: and(X, Y) where X and Y both commit to the annex via a signature, but can use different amounts of cost based on the response from one to another. So if X signs first and requires an annex with 10avwu, then Y signs, but requires 11avwu, then X must re-sign and might require 12avwu, etc 05:53 -!- real_or_random [~real_or_r@user/real-or-random/x-4440763] has quit [Quit: ZNC 1.8.2 - https://znc.in] 05:54 -!- real_or_random [~real_or_r@user/real-or-random/x-4440763] has joined #bitcoin-wizards 06:10 -!- vysn [~vysn@user/vysn] has quit [Ping timeout: 240 seconds] 06:10 < roconnor_> Why would things get funky? 06:42 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…] 06:55 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has joined #bitcoin-wizards 07:16 < jeremyrubin> For the reasons I have after 07:17 < jeremyrubin> *gave 07:17 < roconnor_> I just seen an undecidability assertion. Maybe I don't understand what validation cost hints are. 07:18 < roconnor_> oh for satsifiers, not validators. 07:18 < jeremyrubin> Yes 07:20 < jeremyrubin> I posted on the ML list. Maybe it's just a matter of "don't write scripts like that"? 07:20 < jeremyrubin> But it seems like it's worth understanding better, and something where my feelings is that the annex for validation cost should be something checkable after running the script 07:20 < jeremyrubin> As opposed to smth the script can read 07:21 < roconnor_> It's probably important to sign a (bound on) the costs that you are willing to authorize. 07:22 < jeremyrubin> That doesn't quite fix it 07:22 < jeremyrubin> Since you want a tight bound 07:22 < jeremyrubin> Otherwise your txn will be too expensive 07:22 < jeremyrubin> Maybe bound and bisect? 07:23 < roconnor_> I mean you prefer a tight bound, but you don't require it. 07:23 < jeremyrubin> Well it's unfortunate for users 07:24 < jeremyrubin> But sure. 07:24 < roconnor_> And users prefer cooperative closes to channels. 07:24 < jeremyrubin> It's equivalent to eg having users include a anchor output per participant in a contract 07:25 < jeremyrubin> Or a bunch of op returns 07:25 < jeremyrubin> Since this decreases the # of txns that can go into a block 07:25 < jeremyrubin> But maybe for a worthy benefit 07:25 < jeremyrubin> It's also annoying that there's one bound vs bound per signer 07:30 < roconnor_> As long as the cost of a checksig is constant independent of the signature's value, it doesn't seem likely to be a problem. 07:31 < roconnor_> resigning a new weight shouldn't change the weight. 07:38 < jeremyrubin> It is though if the weight can be read on the stack 07:38 < jeremyrubin> The annex weight 07:39 < roconnor_> ya, that's along the lines of dont write scripts like that. 07:39 < roconnor_> I mean there are safe things you can do with the weight on the stack, and then there are stupid things you can do. 07:40 < roconnor_> Maybe similar games can be played with the locktime on the stack. 07:40 < jeremyrubin> I don't think so 07:40 < jeremyrubin> Since the locktime is not able to be put on the stack 07:40 < jeremyrubin> If it were, then possibly 07:41 < roconnor_> If we add CAT we can probably get the locktime on the stack. 07:41 < jeremyrubin> Well that's a different question 07:41 < roconnor_> oh, what's the current question? 07:41 < jeremyrubin> With cureent scripts I'm only aware of how you can get a couple locktime values on the stack 07:42 < jeremyrubin> Which is if the lock time is the max value 07:42 < jeremyrubin> But even then I think some of the bits are masked so we don't know the exact value it is 07:43 < jeremyrubin> Lower bound + upper bound would give you exact value. But generally you can't know what the value is exactly except that case 07:48 < jeremyrubin> In any case, im not really sure if it's a problem or not, but it's worth having thorough analysis of any annex use cases before we do one. 07:48 < jeremyrubin> I like annex for lock times 2.0, but I'm skeptical about adding weight. 07:54 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has joined #bitcoin-wizards 08:02 -!- vysn [~vysn@user/vysn] has joined #bitcoin-wizards 08:38 -!- vysn [~vysn@user/vysn] has quit [Ping timeout: 240 seconds] 08:38 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has left #bitcoin-wizards [Closing Window] 09:13 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…] 09:19 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-wizards 09:42 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Remote host closed the connection] 10:12 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-wizards 10:27 -!- mauz [~mauz@82.66.125.193] has joined #bitcoin-wizards 10:34 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-wizards 10:37 -!- solocshaw [~Thunderbi@gateway/vpn/pia/solocshaw] has joined #bitcoin-wizards 10:46 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Ping timeout: 240 seconds] 11:03 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection] 11:06 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has joined #bitcoin-wizards 11:10 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-wizards 11:44 -!- solocshaw [~Thunderbi@gateway/vpn/pia/solocshaw] has quit [Ping timeout: 268 seconds] 11:46 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Quit: Leaving...] 12:13 < roconnor_> If we add weight to the annex and want to maniuplate it from script we'd probably add a CheckWeightVerify opcode that does an inequality comparision with the weight value, like is done with locktimes. 12:34 -!- solocshaw [~Thunderbi@gateway/vpn/pia/solocshaw] has joined #bitcoin-wizards 13:15 -!- bfsfhkacjzgcytf9 [~bfsfhkacj@user/bfsfhkacjzgcytf] has quit [Quit: The Lounge - https://thelounge.chat] 13:15 -!- jesseposner [~jesse@user/jesseposner] has joined #bitcoin-wizards 13:16 -!- bfsfhkacjzgcytf9 [~bfsfhkacj@user/bfsfhkacjzgcytf] has joined #bitcoin-wizards 13:19 -!- mauz [~mauz@82.66.125.193] has quit [Quit: Leaving...] 13:40 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…] 14:41 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has joined #bitcoin-wizards 15:11 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…] 15:35 -!- Saloframes [~Saloframe@user/Saloframes] has quit [Quit: Leaving] 17:35 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has joined #bitcoin-wizards 17:35 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has quit [Client Quit] 17:40 -!- vysn [~vysn@user/vysn] has joined #bitcoin-wizards 18:04 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 245 seconds] 19:09 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has joined #bitcoin-wizards 19:11 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has quit [Client Quit] 21:18 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-wizards 21:37 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Quit: Leaving...] 23:09 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has joined #bitcoin-wizards 23:09 -!- DeanGuss [~dean@user/deanguss] has quit [Quit: buhbye] 23:13 -!- DeanGuss [~dean@nonplayercharacter.me] has joined #bitcoin-wizards 23:13 -!- DeanGuss [~dean@nonplayercharacter.me] has quit [Changing host] 23:13 -!- DeanGuss [~dean@user/deanguss] has joined #bitcoin-wizards 23:23 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…] 23:35 -!- tromp [~textual@dhcp-077-249-230-040.chello.nl] has joined #bitcoin-wizards 23:36 -!- plankster [~plankster@user/plankers] has quit [Quit: No Ping reply in 180 seconds.] 23:37 -!- plankster [~plankster@user/plankers] has joined #bitcoin-wizards 23:44 -!- geyaeb [~geyaeb@gateway/tor-sasl/geyaeb] has quit [Ping timeout: 240 seconds] 23:46 -!- geyaeb [~geyaeb@gateway/tor-sasl/geyaeb] has joined #bitcoin-wizards --- Log closed Sun Mar 06 00:00:17 2022