--- Log opened Mon May 16 00:00:25 2022
00:44 -!- filename [~kilitary@188.242.97.156] has quit [Remote host closed the connection]
02:05 -!- z9z0b3t1_ [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has joined #bitcoin-rust
02:09 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 256 seconds]
06:29 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has joined #bitcoin-rust
06:32 -!- z9z0b3t1_ [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 256 seconds]
09:11 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #bitcoin-rust
09:14 -!- _filename [~kilitary@188.242.97.156] has joined #bitcoin-rust
09:30 -!- _filename is now known as filename
09:32 -!- elsirion [~quassel@gateway/tor-sasl/elsirion] has quit [Ping timeout: 240 seconds]
09:32 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds]
09:32 -!- elsirion [~quassel@gateway/tor-sasl/elsirion] has joined #bitcoin-rust
10:35 -!- trev [~trev@user/trev] has quit [Remote host closed the connection]
10:46 -!- z9z0b3t1_ [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has joined #bitcoin-rust
10:49 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 256 seconds]
13:07 < M1asdfah[m]> a bech32 address can send to a bech32m address 
13:09 < M1asdfah[m]> If I sign a transaction with a bech32 and send it to a bech32m address. I see a p2wpkh script 
13:09 < M1asdfah[m]> OP_1 bad13233409567ab02dbdab8246a2f6094bda195b62ed0d6b2f6c9a00f350349
13:10 < M1asdfah[m]> for example 
13:14 < M1asdfah[m]> How can I spend a OP_1 <address> if it came from a bech32 address
13:15 < reardencode> M1asdfah[m]: addresses don't send to other addresses. bitcoin transactions consume UTXOs (which have locking scripts that may be represented by an address format) and produce UTXOs (which may have output scripts that can be represented by addresses)
13:16 < reardencode> If you have a UTXO who's locking script is `OP_1 <32 byte pubkey>` that script can be represented by a bech32m address
13:16 < reardencode> that locking script doesn't care what the locking script of the inputs to the transaction that created it was at all.
13:18 < M1asdfah[m]> Okay so signing a transaction and sending it from a bech32 to a bech32m and a bech32m to a bech32m is done the same way 
13:19 < M1asdfah[m]> Other then one signature is using ecdsa and another one is using shnorr 
13:20 < reardencode> bech32 addresses are used to represent SegWit v0 locking scripts, bech32m SegWit v1. You sign each of those according to the rules specified in their respective BIPs. The _outputs_ of the transaction you include either type of input may be of any type.
13:20 < reardencode> The rules for signing SegWit v0 and v1 differ in many ways, of which the signing algorithm is only one.
13:30 < M1asdfah[m]> I guess what I mean is I'm assuming that segwit v1 is compatiable with v0. So signing with v1 from a tx send from v0 will be different then signing a tx from v1
13:31 < M1asdfah[m]> In the BIP 341 I didn't see a whole lot about how to sign with v1 from a tx sent by v0
13:31 < reardencode> There is no cross restriction on the locking scripts of the output side of a bitcoin transaction based on the input side. Legacy, SegWit v0, v1, undefined versions, none of them restrict the types of outputs that can be created.
13:32 < reardencode> You must sign your _input_ with the method described by the BIP corresponding to that _input_'s locking script. It doesn't matter where that input came from, and it doesn't matter where it's going.
13:37 < M1asdfah[m]> So taproot wallets should beable to sign ecdsa for v0 as well as shnorr for v1
13:39 < reardencode> I think you're still confusing the input side vs. the output side.  If you have a taproot only wallet, it will only ever generate bech32m taproot addresses. It will only be able to sign with the segwit v1 sighash rules, and schnorr signatures. It can create outputs with any locking script, because the signature rules are for how the input is signed and do not say anything about what output 
13:39 < reardencode> scripts can be in the output side of the tx.
14:53 -!- afilini [~afilini@2001:bc8:1828:245::2] has quit [Ping timeout: 240 seconds]
14:54 -!- enick_582 [~afilini-m@2001:bc8:1828:245::2] has quit [Ping timeout: 248 seconds]
14:56 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has joined #bitcoin-rust
14:59 -!- z9z0b3t1_ [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 256 seconds]
15:07 -!- enick_582 [~afilini-m@2001:bc8:1828:245::2] has joined #bitcoin-rust
15:07 -!- afilini [~afilini@2001:bc8:1828:245::2] has joined #bitcoin-rust
19:03 -!- z9z0b3t1_ [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has joined #bitcoin-rust
19:06 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 246 seconds]
20:14 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #bitcoin-rust
20:23 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds]
20:26 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #bitcoin-rust
20:31 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds]
21:40 -!- trev [~trev@user/trev] has joined #bitcoin-rust
23:16 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has joined #bitcoin-rust
23:19 -!- z9z0b3t1_ [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 250 seconds]
--- Log closed Tue May 17 00:00:26 2022