--- Log opened Mon Dec 09 00:00:13 2024
00:17 -!- itsarjn [~itsarjn@user/itsarjn] has joined #bitcoin-wizards
00:28 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
00:34 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #bitcoin-wizards
00:49 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-wizards
02:16 -!- itsarjn [~itsarjn@user/itsarjn] has quit [Remote host closed the connection]
02:45 -!- brunoerg [~brunoerg@2804:14c:3bfb:37:3ccf:80f4:c304:eb9f] has quit [Remote host closed the connection]
02:46 -!- mcey_ [~emcy@85.255.233.191] has joined #bitcoin-wizards
02:49 -!- emcy__ [~emcy@85.255.233.191] has quit [Ping timeout: 246 seconds]
03:20 -!- fluffypony [~fluffypon@user/fluffypony] has quit [Quit: peace out, A town]
03:30 -!- brunoerg [~brunoerg@2804:14d:5285:84b2::1001] has joined #bitcoin-wizards
04:47 -!- itsarjn [~itsarjn@user/itsarjn] has joined #bitcoin-wizards
04:57 -!- itsarjn_ [~itsarjn@user/itsarjn] has joined #bitcoin-wizards
05:00 -!- itsarjn [~itsarjn@user/itsarjn] has quit [Ping timeout: 260 seconds]
05:15 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 260 seconds]
05:18 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-wizards
05:21 -!- itsarjn [~itsarjn@user/itsarjn] has joined #bitcoin-wizards
05:24 -!- itsarjn_ [~itsarjn@user/itsarjn] has quit [Ping timeout: 252 seconds]
05:33 -!- mcey_ [~emcy@85.255.233.191] has quit [Quit: Leaving]
05:39 -!- itsarjn [~itsarjn@user/itsarjn] has quit [Remote host closed the connection]
05:40 -!- itsarjn [~itsarjn@user/itsarjn] has joined #bitcoin-wizards
05:42 -!- mcey [~emcy@85.255.233.191] has joined #bitcoin-wizards
05:45 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 245 seconds]
05:47 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:49 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-wizards
06:00 < andytoshi> reading through WK's message on bitcoin-dev where he asks about an "OP_SUCCESS that may be present but unexecuted without auto-succeeding the script" opcode
06:01 < andytoshi> ISTR the existing "OP_SUCCESS passes the script if it's present at all, regardless of execution" semantics came from some argument to do with signature aggregation
06:01 < andytoshi> like, if we did what WK was suggesting then it'd be hard to do future softforks because old and new nodes might disagree on the aggregation state
06:02 < andytoshi> but now i can't recreate this argument
06:02 < andytoshi> does anybody remember it?
06:02 < andytoshi> sipa ?
06:08 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
06:16 < _aj_> OP_SUCCESS is searched in a first pass before any execution happens, yes
06:16 < _aj_> if you didn't do that, you wouldn't be able to soft fork in OP_ELSEIF or multibyte opcodes where the second byte is OP_IF/ELSE/ENDIF
06:18 < andytoshi> could you have some OP_SUCCESS opcodes that work the current way, and some that work WK's way?
06:18 < andytoshi> you'd need to use the current ones for constructions like you're describing ... but "normal" softforks could use the WK ones
06:23 < instagibbs> is he basically asking for an old school OP_RETURN?
06:25 < _aj_> it's just code, you could do anything
06:25 < instagibbs> wow
06:30 < instagibbs> err no, OP_RETURN would result in top of stack introspection for success/fail, but close
06:33 < andytoshi> instagibbs: heh yeah, it's basically an old-school op_return
06:33 < andytoshi> though ofc now you can't put opcodes into witness data so it's not trivially broken
06:33 < instagibbs> :) 
06:34 < instagibbs> the other half of OP_RETURN
06:46 < sipa> andytoshi: the point of OP_SUCCESSx is being able to soft-fork in any semantics, for the case where they're present at all
06:47 < sipa> including, you can have a softfork that changes an OP_SUCCESSx to mean "marks script execution as succesful if executed according to old rules"
06:47 < andytoshi> hah, that's cute
07:17 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #bitcoin-wizards
07:44 -!- brunoerg [~brunoerg@2804:14d:5285:84b2::1001] has quit [Remote host closed the connection]
07:45 -!- brunoerg [~brunoerg@2804:14d:5285:84b2::1001] has joined #bitcoin-wizards
07:46 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
07:49 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #bitcoin-wizards
07:50 -!- brunoerg [~brunoerg@2804:14d:5285:84b2::1001] has quit [Ping timeout: 246 seconds]
08:01 -!- brunoerg [~brunoerg@2804:14d:5285:84b2::1001] has joined #bitcoin-wizards
08:12 -!- brunoerg [~brunoerg@2804:14d:5285:84b2::1001] has quit [Remote host closed the connection]
08:13 -!- brunoerg [~brunoerg@2804:14d:5285:84b2::1001] has joined #bitcoin-wizards
08:18 -!- brunoerg [~brunoerg@2804:14d:5285:84b2::1001] has quit [Ping timeout: 265 seconds]
08:51 < Ademan> _aj_: the "search" for OP_SUCCESS processes the script opcode-by-opcode (rather than byte-by-byte) though doesn't it? Otherwise an OP_SUCCESS byte in the middle of a pubkey could cause unexpected success.
09:38 -!- brunoerg [~brunoerg@187.183.60.117] has joined #bitcoin-wizards
09:52 < instagibbs> it requires parsing the script yes
09:56 -!- mcey_ [~emcy@85.255.233.191] has joined #bitcoin-wizards
09:58 -!- mcey [~emcy@85.255.233.191] has quit [Ping timeout: 244 seconds]
10:02 < _aj_> Ademan: it parsers until it finds an OP_SUCCESS then abandons; a byte prior to the first OP_SUCCESS that's behind a PUSH opcode will be treated as PUSH data, not an OP_SUCCESS
10:02 < _aj_> parses
10:22 < Ademan> thanks
10:39 -!- itsarjn [~itsarjn@user/itsarjn] has quit [Remote host closed the connection]
10:40 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
10:46 -!- itsarjn [~itsarjn@user/itsarjn] has joined #bitcoin-wizards
10:57 < jeremyrubin> andytoshi: It also means that OP_SUCCESSx semantics are not really "upgradable", e.g., if used for things like TXHASH, unknown flag patterns (for future soft forking) have to be processed as NOP since you won't know till you execute.
10:58 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #bitcoin-wizards
10:59 -!- RickSanchez [~RickSanch@syn-098-102-191-082.biz.spectrum.com] has quit [Quit: Leaving...]
11:05 < andytoshi> right, makes sense
11:06 < andytoshi> so, curiously, it looks like WK wants a "weak SUCCESS" opcode to be used as part of the actual script logic. not as an upgrade mechanism
11:06 < andytoshi> so it sounds like we could softfork one ofthe exsiting successx's to have this behavior
11:07 < andytoshi> just one
11:11 < jeremyrubin> idk what WK is, but maybe? It's like an anti-opreturn? I think good semantics would maybe be to have it drop the stack and altstack, push a true, and stop execution (or continue execution, but the remaining script is argument free, e.g., <H> CTV, <N> CLTV, etc?
11:17 -!- brunoerg [~brunoerg@187.183.60.117] has quit [Read error: Connection reset by peer]
11:18 -!- brunoerg [~brunoerg@187.183.60.117] has joined #bitcoin-wizards
11:23 -!- brunoerg [~brunoerg@187.183.60.117] has quit [Ping timeout: 260 seconds]
11:25 -!- brunoerg [~brunoerg@2804:14c:3bfb:37:14e9:ff53:e373:da0b] has joined #bitcoin-wizards
11:36 < andytoshi> jeremyrubin: WK is weiking, who posted a message on bitcoin-dev which made me ask this
11:36 < andytoshi> yeah, like an "anti-opreturn". you execute it and it quits with success
11:37 -!- fluffypony [~fluffypon@user/fluffypony] has joined #bitcoin-wizards
11:37 < sipa> OP_RETURN_TRUE
12:11 -!- itsarjn [~itsarjn@user/itsarjn] has quit [Remote host closed the connection]
12:51 -!- Murch[m] [~murch@user/murch] has quit [Ping timeout: 248 seconds]
12:51 -!- Murch[m] [~murch@2620:6e:a000:ce11::1b] has joined #bitcoin-wizards
13:32 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
13:35 -!- MyNetAz [~MyNetAz@user/MyNetAz] has quit [Read error: Connection reset by peer]
13:37 -!- MyNetAz [~MyNetAz@user/MyNetAz] has joined #bitcoin-wizards
14:12 -!- MyNetAz [~MyNetAz@user/MyNetAz] has quit [Remote host closed the connection]
14:14 -!- MyNetAz [~MyNetAz@user/MyNetAz] has joined #bitcoin-wizards
14:32 -!- CrashTestDummy [~CrashTest@ool-ad028632.dyn.optonline.net] has joined #bitcoin-wizards
14:32 -!- CrashTestDummy [~CrashTest@ool-ad028632.dyn.optonline.net] has quit [Read error: Connection reset by peer]
14:35 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
14:42 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #bitcoin-wizards
14:54 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
15:00 -!- MyNetAz [~MyNetAz@user/MyNetAz] has quit [Remote host closed the connection]
15:02 -!- MyNetAz [~MyNetAz@user/MyNetAz] has joined #bitcoin-wizards
16:15 -!- solocshaw [~Thunderbi@2601:2c3:c080:2310:41d7:deb3:ea1:339f] has joined #bitcoin-wizards
16:15 -!- mcey_ [~emcy@85.255.233.191] has quit [Remote host closed the connection]
16:16 -!- mcey [~emcy@85.255.233.191] has joined #bitcoin-wizards
17:16 -!- greypw149 [~greypw@user/greypw] has joined #bitcoin-wizards
17:17 -!- greypw14 [~greypw@user/greypw] has quit [Remote host closed the connection]
17:17 -!- greypw149 is now known as greypw14
18:52 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
19:24 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-wizards
19:40 -!- solocshaw [~Thunderbi@2601:2c3:c080:2310:41d7:deb3:ea1:339f] has quit [Quit: solocshaw]
20:01 < Ademan> jeremyrubin: if I steal the CTV test vectors do I need to include an appropriate BSD license for it?
20:35 -!- itsarjn [~itsarjn@user/itsarjn] has joined #bitcoin-wizards
21:08 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-wizards
21:19 -!- twistedline [~bitcoin@185.193.125.44] has quit []
21:19 -!- twistedline [~bitcoin@185.193.125.44] has joined #bitcoin-wizards
21:34 -!- itsarjn [~itsarjn@user/itsarjn] has quit [Remote host closed the connection]
21:37 -!- itsarjn [~itsarjn@user/itsarjn] has joined #bitcoin-wizards
21:39 -!- Guest84 [~Guest84@2a06:c701:4ce5:5800:d17c:9b72:efad:9eeb] has joined #bitcoin-wizards
21:39 -!- Guest84 [~Guest84@2a06:c701:4ce5:5800:d17c:9b72:efad:9eeb] has quit [Client Quit]
21:41 -!- itsarjn [~itsarjn@user/itsarjn] has quit [Ping timeout: 260 seconds]
21:43 -!- itsarjn [~itsarjn@user/itsarjn] has joined #bitcoin-wizards
21:52 -!- itsarjn [~itsarjn@user/itsarjn] has quit [Remote host closed the connection]
21:55 -!- itsarjn [~itsarjn@user/itsarjn] has joined #bitcoin-wizards
22:01 -!- mcey_ [~emcy@85.255.233.191] has joined #bitcoin-wizards
22:01 -!- mcey [~emcy@85.255.233.191] has quit [Remote host closed the connection]
22:01 -!- mcey_ [~emcy@85.255.233.191] has quit [Remote host closed the connection]
22:02 -!- mcey_ [~emcy@85.255.233.191] has joined #bitcoin-wizards
22:16 -!- MyNetAz [~MyNetAz@user/MyNetAz] has quit [Read error: Connection reset by peer]
22:17 -!- MyNetAz [~MyNetAz@user/MyNetAz] has joined #bitcoin-wizards
22:36 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-wizards
22:37 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 244 seconds]
23:31 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #bitcoin-wizards
23:32 -!- itsarjn [~itsarjn@user/itsarjn] has quit [Remote host closed the connection]
23:35 -!- itsarjn [~itsarjn@user/itsarjn] has joined #bitcoin-wizards
23:40 -!- itsarjn [~itsarjn@user/itsarjn] has quit [Ping timeout: 265 seconds]
23:44 -!- itsarjn [~itsarjn@user/itsarjn] has joined #bitcoin-wizards
23:47 -!- jon_atack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
23:48 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-wizards
23:54 -!- itsarjn [~itsarjn@user/itsarjn] has quit [Remote host closed the connection]
23:56 -!- itsarjn [~itsarjn@user/itsarjn] has joined #bitcoin-wizards
--- Log closed Tue Dec 10 00:00:14 2024