Sosthene00

11:34 ##taproot-bip-review: <@aj> xoyi-: 173 describes the address format (presented to users in wallets) rather than the scriptPubKey format which is what actually appears on chain, so 141 seems like a better fit
11:36 ##taproot-bip-review: < xoyi-> ah right. Thanks for clarifying @aj
12:10 ##taproot-bip-review: < waxwing> we (group 6) were confused about hash_type 0x00 - the taproot bip says the new tx digest has all the old sighash flags (1,2,3, +0x80) but this 0x00 seems to be a default, but it isn't explained what sighashing it refers to/defines?
12:10 ##taproot-bip-review: < waxwing> feel like i must have missed something.
12:11 ##taproot-bip-review: <@aj> waxwing: bip-taproot "Signature validation rules" says when hash_type = 00
12:13 ##taproot-bip-review: < waxwing> aj, yes that's what i/we read. i don't get it. what is this default value, what does it mean about sighashing? it's not the same as sighash_all (0x01), right?
12:13 ##taproot-bip-review: <@aj> waxwing: it is the same as sighash_all, except

Sosthene00

18:58 < Lexyon__> Well, hello everyone :)
19:00 <@sosthene> Hi
19:01 < waxwing> hi
19:01 <@sosthene> Ed said he would be here in an email
19:02 < waxwing> what are we going off, this? this right: https://github.com/ajtowns/taproot-review/blob/master/week-1.md
19:02 <@sosthene> yes
19:03 <@sosthene> I think since there's so many resources, we'd better focus on the BIP for now
19:03 < waxwing> right https://github.com/sipa/bips/blob/bip-schnorr/bip-taproot.mediawiki
19:03 <@sosthene> at least it feels like that's what everyone has been doing this week
19:03 < waxwing> do we want to answer each of the bullet point questions in the former?

Sosthene00

sosthene@sosthene-UX303LN:~/github/miniscript_marsu$ minis_ <<< "and(pk(A),or(99@pk(B),older(12960)))"
X    222.2800000000    77 and_v(vc:pk(A),or_d(c:pk(B),older(12960))) and(pk(A),or(99@pk(B),older(12960)))
<A> OP_CHECKSIGVERIFY <B> OP_CHECKSIG OP_IFDUP OP_NOTIF
  <a032> OP_CHECKSEQUENCEVERIFY
OP_ENDIF
sosthene@sosthene-UX303LN:~/github/miniscript_marsu$ minis_ <<< "and(pk(A),or(pk(B),older(12960)))"
X    187.0000000000    77 and_v(vc:pk(A),or_d(c:pk(B),older(12960))) and(pk(A),or(pk(B),older(12960)))
<A> OP_CHECKSIGVERIFY <B> OP_CHECKSIG OP_IFDUP OP_NOTIF
  <a032> OP_CHECKSEQUENCEVERIFY
OP_ENDIF

Sosthene00

Keybase proof

I hereby claim:

• I am sosthene00 on github.
• I am sosth (https://keybase.io/sosth) on keybase.
• I have a public key ASDHaE0TgLSgWi0Ik6Xbjmrohi0Bra8rX6uENR3rdhS93wo

To claim this, I am signing this object:

Sosthene00

# Back-up the .lnd dir
`cp -r .lnd/ .lnd.old`
# copy the .lnd dir to another machine that runs a non-pruned full node
`scp [source] [target]`
# Install GO
`wget https://dl.google.com/go/go1.12.3.linux-amd64.tar.gz`
`sha256sum go1.12.3.linux-amd64.tar.gz | awk -F " " '{ print $1 }'`
# output should be `3924819eed16e55114f02d25d03e77c916ec40b7fd15c8acb5838b63135b03df`
`tar -C /usr/local -xzf go1.12.3.linux-amd64.tar.gz`
`export PATH=$PATH:/usr/local/go/bin`

Sosthene00

### Keybase proof

I hereby claim:

  * I am boblechinois on github.
  * I am sosth (https://keybase.io/sosth) on keybase.
  * I have a public key ASCoa-z_K_4lsBlZIaOKzerg59pDqOqzie4Hfo46kNMDTgo

To claim this, I am signing this object: