--- Log opened Tue Dec 01 00:00:32 2020
02:18 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
02:18 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined ##miniscript
03:31 -!- jeremyrubin [~jr@c-73-15-215-148.hsd1.ca.comcast.net] has quit [Ping timeout: 256 seconds]
05:14 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
05:15 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined ##miniscript
08:44 -!- jeremyrubin [~jr@c-73-15-215-148.hsd1.ca.comcast.net] has joined ##miniscript
09:27 < andytoshi> sipa: is the plan for taproot addresses to use bech32 (and fix to 32 byte length)? or do you want a new BCH code already?
09:27 < andytoshi> i understand gmax is already searching for one..
09:27 < andytoshi> also, do you know off the top of your head whether blech32 is vulnerable to the same lengcth extension thing?
09:28 < sipa> andytoshi: see the mailing disk discussion
09:28 < sipa> i'm planning to write an update on it today
09:28 < sipa> going to agree with rusty's suggestion of using the new checksum for v1+ addresses
09:28 < sipa> it's the same BCH code, but a different constant xored in at the end
09:29 < sipa> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-October/018236.html
09:29 < andytoshi> ok, wonderful. will wait for your update. thanks for the link!
09:30 < sipa> greg and i managed to write and run code that exhaustively analyzed the properties of all 2^30 possible constants
09:34 < andytoshi> nicee
09:35 < sipa> and yes, i believe blech32 has the same inherent issue
10:07 < sipa> andytoshi, sanket1729_: thoughts? https://github.com/sipa/miniscript/pull/51
10:28 < sipa> https://github.com/sipa/miniscript/pull/52/files
10:28 < sipa> what does rust-miniscript do?
10:37 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 272 seconds]
10:38 -!- jonatack [~jon@109.232.227.138] has joined ##miniscript
11:36 < andytoshi> c: inherits all malleability properties in rust-miniscript
11:36 < sipa> ok, that sounds correct
11:37 < sipa> we'd have detected discrepancy before when doing cross-implementation testing i think
11:37 < sipa> if it wasn't
11:37 < andytoshi> yeah i think so 
11:37 < sipa> interesting that the web page is wrong but both implementations are correct
11:37 < andytoshi> we use an enum for e/f/neither rather than a pair of booleans
11:37 < andytoshi> so it would be hard to propagate e without propagating f
11:38 < andytoshi> yeah .. i suspect we were both thinking "just passthrough everything" when implementing
11:38 < andytoshi> the spec could even say s=s_x rather than just s
11:39 < sipa> indeed
11:39 < sipa> i think it can also pass through o,n,d,u
11:40 < sipa> (currently it says pass through o,n,d but u is of course always implied)
12:47 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
12:49 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined ##miniscript
19:07 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection]
20:18 -!- shesek [~shesek@164.90.217.137] has joined ##miniscript
20:18 -!- shesek [~shesek@164.90.217.137] has quit [Changing host]
20:18 -!- shesek [~shesek@unaffiliated/shesek] has joined ##miniscript
20:51 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection]
23:00 -!- jeremyrubin [~jr@c-73-15-215-148.hsd1.ca.comcast.net] has quit [Ping timeout: 256 seconds]
--- Log closed Wed Dec 02 00:00:33 2020