--- Log opened Wed Aug 18 00:00:41 2021
00:12 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
00:51 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-pr-reviews
01:21 -!- b10c [uid500648@id-500648.charlton.irccloud.com] has joined #bitcoin-core-pr-reviews
03:11 -!- honkingsandwich [~honkingsa@73.112.94.0] has quit [Remote host closed the connection]
07:02 -!- medomisa [~medomisa@BSN-143-170-179.dynamic.siol.net] has joined #bitcoin-core-pr-reviews
07:02 < medomisa> Hey everyone
07:03 < medomisa> first timer here. Have expirience with coding, would like to follow along 
07:03 -!- honkingsandwich [~honkingsa@73.112.94.0] has joined #bitcoin-core-pr-reviews
07:07 -!- medomisa [~medomisa@BSN-143-170-179.dynamic.siol.net] has quit [Quit: Connection closed]
07:26 < jnewbery> you've very welcome medomisa. We get started in about 2.5 hours
07:40 < Talkless> Hi. How long should I expect to wait for i2p connections..? 
07:40 < Talkless> keeps trying but: https://paste.debian.net/1208117/
07:44 -!- babasancheti [~babasanch@43.249.232.30] has quit [Quit: Client closed]
07:47 -!- babasancheti [~babasanch@43.249.232.30] has joined #bitcoin-core-pr-reviews
08:11 < laanwj> that doesn't look like the SAM proxy is working correctly, it's closing the connection and even stopping listening; any errors in your I2P logs?
08:15 -!- muhblockchain [~muhblockc@user/muhblockchain] has joined #bitcoin-core-pr-reviews
08:31 -!- davterra [~davterra@143.198.56.186] has quit [Quit: Leaving]
08:38 -!- hernan [~hernan@OL121-235.fibertel.com.ar] has joined #bitcoin-core-pr-reviews
08:40 -!- hernanmarino [~hernanmar@OL121-235.fibertel.com.ar] has joined #bitcoin-core-pr-reviews
08:41 -!- hernan [~hernan@OL121-235.fibertel.com.ar] has quit [Client Quit]
08:49 < josibake> Talkless: if you are using a fresh install of i2p, SAM bridge is disabled by default. once you enable it, you should be good
08:54 < Talkless> josibake: it's enabmed = true on my Debian machine
08:54 < Talkless> enabled*
08:57 < Talkless> josibake: seeing some kind of issues in i2p log which I don't grok https://paste.debian.net/1208128/
09:01 < josibake> Talkless: if you're able to make the pr review club in an hour, we can work through troubleshooting it 
09:02 < Talkless> josibake: I'll try to fix it, I believe issiues is that it's in VirtualBox with NAT mode, I see firewall issues in host logs...
09:03 -!- muhblockchain [~muhblockc@user/muhblockchain] has quit [Ping timeout: 240 seconds]
09:10 < Talkless> josibake: works after changing VirtualBox network card mode
09:21 < hebasto> Talkless: which mode works?
09:21 < Talkless> hebasto: I believe it's called "Bridge", it's localized...
09:21 < hebasto> thanks!
09:22 < Talkless> hebasto: VirtualBox does some magic in kernel so that VM has it's own IP address, and kinda goes around your host fw :|
09:22 < Talkless> just for got to use that :/
09:22 < Talkless> forgot
09:30 -!- shaman [~shaman@61.0.94.146] has joined #bitcoin-core-pr-reviews
09:30 -!- naiza [~naiza@180.188.251.67] has joined #bitcoin-core-pr-reviews
09:46 -!- raj [~raj_@2409:4061:28c:fa97:95e1:3ff7:ebaa:9cf0] has joined #bitcoin-core-pr-reviews
09:52 -!- Blue_Moon [~Blue_Moon@189.149.186.140] has joined #bitcoin-core-pr-reviews
09:54 < jarolrod> ✌⊂(✰‿✰)つ✌
09:55 -!- sugarjig [~sugarjig@c-73-152-17-189.hsd1.va.comcast.net] has joined #bitcoin-core-pr-reviews
09:56 < larryruane> Talkless: In case you haven't seen my comment here: https://github.com/bitcoin/bitcoin/issues/22634#issuecomment-901204272 I had a similar experience (and I am running in a Virtualbox VM also), except that just by restarting the node, the I2P began working
09:58 < Talkless> larryruane: maybe it would have been working via default NAT, but.. I have "paranoid" firewall setup in host where local and outgoing traffic is filtered :D
09:58 < Talkless> While bridge mode just works transparently
10:00 < josibake> #startmeeting
10:00 < emzy> Hi
10:00 -!- darius27 [~darius27@c-73-252-226-175.hsd1.ca.comcast.net] has joined #bitcoin-core-pr-reviews
10:00 < josibake> hello everyone! welcome to another special edition of the bitcoin pr review club
10:00 < larryruane> hi!
10:00 < raj> hello
10:00 < Talkless> hi
10:00 < hernanmarino> hi everyone !
10:00 < janb> hi !
10:00 < darius27> hi!
10:00 < theStack> hi
10:00 < jnewbery> hi
10:00 < josibake> today we are going to be testing bitcoin's upcoming 22.0 release
10:01 < josibake> to help us along, we will be following this guide: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/22.0-Release-Candidate-Testing-Guide
10:01 -!- dulce [~dulce@172.92.166.62] has joined #bitcoin-core-pr-reviews
10:01 < michaelfolkson> hi
10:01 -!- sriramdvt [~sriramdvt@183.83.132.111] has joined #bitcoin-core-pr-reviews
10:01 < josibake> not only is this a great way to help out bitcoin development by testing, but its also a great way to get experience compiling bitcoin on your own
10:02 < josibake> for starters, is this anyone's first time?
10:02 < schmidty> hi
10:02 < jarolrod> hi
10:02 < naiza> hi
10:02 -!- Azorcode [~Azorcode@186-88-143-193.genericrev.cantv.net] has joined #bitcoin-core-pr-reviews
10:02 < josibake> (also, give us a hi if you plan to follow along!)
10:02 < sriramdvt> hi
10:02 < raj> not first time in club, but first time in rc testing.. 
10:02 < shaman> Hello everyone !
10:02 < Talkless> hi
10:02 < josibake> raj: awesome! thanks for joining
10:02 < sugarjig> hi
10:02 -!- chunkblob [~chunkblob@cpe-184-153-97-30.nyc.res.rr.com] has joined #bitcoin-core-pr-reviews
10:02 < Azorcode> Hello Everyone 
10:03 -!- svav [~svav@82-69-86-143.dsl.in-addr.zen.co.uk] has joined #bitcoin-core-pr-reviews
10:03 < chunkblob> hi!
10:03 < dulce> Hola mundo!
10:04 < svav> Hi
10:04 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
10:04 < josibake> for any newcomers (and just as a reminder), its encouraged to just blurt out questions! no need to ask for permission first or worry about if you're interrupting another question
10:04 < Talkless> raj: I beleive I've been in clube maybo once.. :/ first RC testing too
10:04 < josibake> Talkless: welcome!
10:05 < josibake> to begin, you'll need to either compile from source or get a pre-compiled binary. if you've never compiled from source before, you might want to go with the pre-compiled binary
10:05 -!- lightlike [~lightlike@user/lightlike] has joined #bitcoin-core-pr-reviews
10:05 < josibake> setting up dependencies and compiling can take a long time when it's the first time 
10:05 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 240 seconds]
10:06 -!- lukedashjr is now known as luke-jr
10:07 -!- hello35 [~hello@66.135.147.73] has joined #bitcoin-core-pr-reviews
10:07 < josibake> we'll give a few minutes for people to get their release candidate, but no need to wait on everyone else if you'd like to start working through the sections or have questions
10:09 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
10:09 < janb> are we testing on signet or also on mainnet ? 
10:10 < raj> josibake, I was wondering, does such testing guides for RCs are produced for each release? or only this one for the review club?  
10:10 < babasancheti> will there be a jitsi meet or just IRC?
10:11 < michaelfolkson> I never set up command line environment when compiling (or wipe, recreate data dir) :) Testing with no data dir definitely makes sense for some things
10:11 < josibake> raj: ideally, we would have a guide for every major release! the guides are produced independent of the pr review club
10:11 < josibake> going over the guide in the club is a great way to get more people involved with testing, tho
10:12 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 252 seconds]
10:12 < josibake> babasancheti: the pr review club is just IRC
10:12 -!- dino28 [~dino@8.17.206.220] has joined #bitcoin-core-pr-reviews
10:12 < raj> Understood. Ya it is a great place to start learning a lot of non-code stuffs around core.. 
10:13 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
10:13 < svav> I don't run a bitcoin node at the moment, but if I did, what is the best way to test the new release without affecting your existing node?
10:13 -!- cole97 [~cole@216.30.182.10] has joined #bitcoin-core-pr-reviews
10:13 < babasancheti> josibake Okay, Thanks
10:13 < josibake> michaelfolkson: bitcoin core will always setup a data directory, it just uses the default one if you don't specify
10:13 < Talkless> svav: I would suggest running virtual machine, like using VirtualBox
10:13 < josibake> here we are specifying to make sure we can easily clean up later and that we also don't interfere with your regular bitcoin setup
10:14 < sugarjig> svav You could also run the new version inside of a Docker container
10:14 < josibake> svav: if you setup the custom data directory, it won't interfere with your existing setup!
10:14 < josibake> you can also do a VM, as others are suggesting
10:15 < raj> I have ran basic build and tests for rc2. But would have to go through the manual testing of each sections, and thats gonna take some time. Not sure if I can complete it within a session of a review club. 
10:15 < josibake> does everyone have their release candidate?
10:15 -!- lukedashjr [~luke-jr@user/luke-jr] has quit [Ping timeout: 240 seconds]
10:15 < emzy> svav: -datadir=/tmp/22-rc-test  is used in the Testing-Guide
10:16 < josibake> raj: no worries! the goal is to get people started and help address any issues people might have while working through the guide. unlikely we will get through all of it in one hour
10:16 -!- babasancheti [~babasanch@43.249.232.30] has quit [Quit: Client closed]
10:17 < Talkless> raj: test meaning unit test with make check, or also functional tests?
10:17 < janb> josibake: yes got the RC :) 
10:17 < raj> svav, you can always run a node in regtest/signet mode in your laptop, and that wont take up much disk space. Its better to have a bitcoind in your local work machine, than try it in your dedicated full node. 
10:17 < darius27> i have the RC too
10:17 < josibake> for the upcoming 22.0 release, some of the major highlights are no more Tor v2, new I2P connections, and more support for external signers! these are the main sections in the guide
10:17 < Talkless> yes, I am currenlty on the step with hw wallet.
10:18 < josibake> there is also a section at the end about the new guix build system! that has it's own guide (linked in the testing guide)
10:18 < raj> I need to setup an emulator, can anyone suggest which one (trezor/coldcard) is easier? 
10:19 < josibake> raj: coldcard emulator is macOnly. i setup the trezor emulator on linux and got it working
10:19 < hernanmarino> raj: coldcard emulator works only on Mac, afaik
10:19 < Talkless> raj: just did trezor, ColdCard is for macos only?
10:19 < raj> josibake, Oh. I missed that.. 
10:20 -!- lightlike [~lightlike@user/lightlike] has quit [Ping timeout: 245 seconds]
10:20 < emzy> I'm doing a fresh guix build right now.
10:20 -!- dino28 [~dino@8.17.206.220] has quit [Quit: Connection closed]
10:20 < josibake> for the tor and i2p sections, does anyone have ideas on other ways we could have tested this? or other features we could have tested?
10:22 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has joined #bitcoin-core-pr-reviews
10:22 < janb> josibake: just by selfdiscovery ? 
10:22 < michaelfolkson> Testing I2P nodes behave the same as clearnet nodes and Tor nodes?
10:23 < michaelfolkson> Whether a I2P node can be a block relay node etc, whether the I2P seeds work etc
10:23 < josibake> janb: correct! we could have not provided any manual peers 
10:23 < josibake> michaelfolkson: absolutely. I2P seeds is another great thing to test
10:24 < emzy> just for info. My I2P seed has 7 incoming I2P connections.
10:25 < Talkless> "IP2 seeds" ?
10:25 < michaelfolkson> There must be some more edge cases to test with low numbers of I2P nodes currently on the network. Though maybe DoS testing would be harsh :)
10:25 < josibake> emzy: awesome! if you post your address, maybe others can try to connecting to you using addnode :) 
10:26 < emzy> that's mine: gehtac45oaghz54ypyopim64mql7oad2bqclla74l6tfeolzmodq.b32.i2p
10:26 < janb> emzy: mainnet or signet ? 
10:26 < josibake> Talkless: i2p seeds, referring to the hardcoded dnsseeds servers
10:26 < Talkless> josibake: thanks
10:26 < josibake> this is so a brand new node on a network (i2p, tor, ipv4 etc) has at least one trusted peer to start with
10:27 < emzy> there is no dnsseed feature for i2p (only). So If you need some hardcodes i2p nodes to bootstrap.
10:28 < josibake> emzy: good call-out, i had thought there was (or that it was being worked on)
10:28 < emzy> There AFAK is no way, because there is no DNS in I2P
10:28 < emzy> btw. the list of hardcodes nodes is here: https://github.com/bitcoin/bitcoin/blob/fd9c22ca69d814815554bfe8acf995cc30afdc2e/contrib/seeds/nodes_main.txt
10:29 < janb> emzy: ty ! 
10:29 < michaelfolkson> (at the bottom of emzy's link)
10:29 < emzy> ipv4, ipv6 and tor nodes are every time picked new from the dnsseed nodes. I2P is manual added.
10:29 -!- observer22 [~observer@cpe-23-242-148-67.socal.res.rr.com] has joined #bitcoin-core-pr-reviews
10:30 < josibake> emzy: i added you using addnode, you should see a connection from bucvabwhehqwt53yhsp6evdcirigjqa6xjljul6wzxors7ccjv7q.b32.i2p
10:30 < emzy> josibake: I do \o/
10:31 < emzy> in          i2p    786 168130   24   52                 56 54891 bucvabwhehqwt53yhsp6evdcirigjqa6xjljul6wzxors7ccjv7q.b32.i2p:0      70016/Satoshi:22.0.0/
10:31 < michaelfolkson> You're on your temporary release testing node though right josibake? Would be good to get some more persistent connections :)
10:32 < josibake> michaelfolkson: correct! just the one for this guide. i am planning to upgrade my raspi to 22.0rc2 this weekend
10:32 < josibake> unless someone finds a terrible bug during this review session ;)
10:32 < michaelfolkson> Haha. Hard to judge how reckless that is
10:32 < josibake> if other people want to try adding emzy or myself, you can use this command: 
10:33 < josibake> bitcoin-cli -datadir=<datadir> addnode bucvabwhehqwt53yhsp6evdcirigjqa6xjljul6wzxors7ccjv7q.b32.i2p add
10:33 < michaelfolkson> Splitting between persistent full node for testing and persistent full node for verifying real money transactions is a good idea I think. You'd be more conservative with your node verifying real money transactions
10:33 < josibake> did anyone have any questions/issues with the Tor section?
10:34 < josibake> michaelfolkson: agreed! having a machine dedicated to running new releases is another great way people can help out with reporting bugs, etc
10:35 < josibake> emzy: invisible internet pals!
10:35 -!- davterra [~davterra@143.198.56.186] has joined #bitcoin-core-pr-reviews
10:35 < emzy> :)
10:36 < michaelfolkson> Is it impossible to maintain a connection to a Tor v2 node now?
10:36 < michaelfolkson> This release ignores them
10:36 < Talkless> my local: c44qol5cgfost64wch7q5dxsj3sf3urk6qi3mrhvbm6jqzbinlaq.b32.i2p
10:37 < michaelfolkson> "but we are still able to connect to them for IBD" ah interesting
10:37 < josibake> michaelfolkson: that's a good question :) any ideas on how we could test that?
10:37 < michaelfolkson> Try to make a connection to a Tor v2 address :)
10:37 < Talkless> michaelfolkson: yeah I've thought there was a bug in "-netinfo", got headers but "zero" connections :) . Theyr'e not displayed in -netinfo
10:39 < josibake> afaik, even using addnode will still ignore a tor v2 (i think i tested this awhile back)
10:39 < josibake> the problem with testing this is a lot of tor v2 peers are starting to go offlline
10:40 < michaelfolkson> Obviously if you are running an older version of Core you are still connected to Tor v2 nodes (unless they go offline)
10:40 < michaelfolkson> But I think Tor is trying to get everyone to upgrade to v3 so yeah makes sense there are fewer and fewer
10:41 < michaelfolkson> Network partition between Tor v2 nodes and Tor v3 nodes :)
10:42 < raj> If you can't find a tor peer, you can try connecting to your existing full node's tor address. It could be a v2.  
10:42 -!- cole97 [~cole@216.30.182.10] has quit [Quit: Connection closed]
10:43 < michaelfolkson> raj: Yeah setting up your own node for testing that is always an option
10:43 < emzy> if you need tor v2 nodes. For now there are these: https://github.com/bisq-network/bisq/blob/04294a4691f437778b472e340301ab8a0813b8f4/core/src/main/java/bisq/core/btc/nodes/BtcNodes.java#L51
10:43 < emzy> Bisq still needs them. So they will be up.
10:44 < michaelfolkson> Why does Bisq still need them?
10:44 < Talkless> I wonder why there's no "i2p" column in "-netinfo" ? It displays i2p local address, ipv4/6/onion/total.
10:44 < emzy> in short bitcoinj
10:44 < josibake> emzy: thanks for the list! if someone is able to test manually connecting to a tor v2 node, give a shout in the chat
10:44 < janb> josibake: is there an IRC channel for bitcoin testing questions (or to find some ppl the coordinate some testing) ? 
10:45 < michaelfolkson> emzy: Impossible to get a merge into bitcoinj?
10:45 < emzy> Talkless: I think the column is only visable if there is more then 0.
10:45 < janb> Talkless: there is an I2p colomn 
10:45 < michaelfolkson> I think it is strongly recommended not to use Tor v2 now
10:46 < michaelfolkson> janb: This IRC channel works for PR review or testing questions
10:46 < emzy> michaelfolkson: no. Next version will have v3 onions. Already all in bitcoinj. But dev. on bisq is slow.
10:46 < josibake> janb: not a dedicated irc channel for testing, no
10:46 < michaelfolkson> emzy: Fair enough
10:46 < janb> tnx michaelfolkson 
10:46 < janb> josibake: tnx
10:47 < michaelfolkson> I think at least a couple of the Lightning implementations have upgraded to Tor v3
10:47 < josibake> Talkless: you can also use -netinfo 4
10:47 < josibake> you should see i2p listed as one of the "net" options
10:47 < janb> I2P does some discovery once connected to some I2P nodes :)  
10:48 -!- common [~common@user/common] has joined #bitcoin-core-pr-reviews
10:49 < josibake> has anyone been able to get to the hardware wallet section?
10:49 < janb> josibake: no sorry
10:49 < josibake> even if you haven't been able to the tests yourself, any ideas on other things we could test?
10:49 -!- dulce [~dulce@172.92.166.62] has quit [Ping timeout: 245 seconds]
10:49 < josibake> janb: no worries! the setup is a bit involved :) 
10:50 < michaelfolkson> Talkless: netinfo guidance was added here https://github.com/bitcoin/bitcoin/pull/20829
10:51 < michaelfolkson> I couldn't decide between using the emulator or using an actual HW wallet and ended up doing neither
10:51 < michaelfolkson> Decision paralysis
10:51 < Talkless> michaelfolkson: happens
10:51 < josibake> michaelfolkson: you still have 9 minutes to decide :)
10:51 < michaelfolkson> Wladimir said don't use production HW wallet
10:52 -!- jiii [~jiii@6.69.broadband9.iol.cz] has joined #bitcoin-core-pr-reviews
10:52 < Talkless> wait, these i2p addresses, these are for signet or..?
10:52 < Talkless> pasted here
10:52 < Talkless> previously 
10:53 < emzy> michaelfolkson: what about using a different new passphrase on the production HW wallet?
10:53 < josibake> Talkless: mainnet , if you were following the guide. the only section of the guide on signet is the HW section
10:53 < emzy> Talkless: mainnet. 
10:53 < emzy> this is my signet one: xdsvygoyhjnepvryvriukmcsljdin6j4lfuxu4vgk6a2gqtwzzsq.b32.i2p
10:53 < josibake> emzy: thats possible, but in general if you have any real funds on a hw, its best to keep it as far away from a computer as possible
10:54 < emzy> yes, best to use a test HW wallet. 
10:54 < josibake> fwiw, i did use an empty coldcard when i was testing and used it on testnet. i think trezor and coldcard both support being used on testnet
10:55 < Talkless> emzy: thanks, connected!
10:55 < emzy> Talkless: yes there is a new incoming connetion.
10:55 < michaelfolkson> I just think keep anything to do with real funds on separate machine/HW wallet to dev/testing. Don't want to do any dumb stuff (or forget whether you are in mainnet VM or testnet/signet VM etc)
10:56 < hernanmarino> josiblake: i tested with an actual trezor on signet. Had some difficulties when i had to provide a passphrase
10:57 < hernanmarino> but not a bug, just my ignorance on how to provide a passphrase using hwi 
10:57 -!- raj [~raj_@2409:4061:28c:fa97:95e1:3ff7:ebaa:9cf0] has quit [Quit: Leaving]
10:57 < josibake> hernanmarino: gotcha, when i used the emulator i didn't set it up with a passphrase. 
10:58 < Talkless> if were'e speaking about wallet emulators, I get this in bitcoin-qt after clicking "Create a new wallet" while emulator and bridge are running:
10:58 < Talkless> "'/home/vincas/code/bitcoin/HWI.git/hwi.py' error: Could not open client or get fingerprint information: Unsupported device"
10:58 < emzy> I think Trezor one is the only HW wallet that get the passphrase from the host.
10:58 < emzy> Oh maybe also Ledger
10:58 < Talkless> no, sorry, bridge not running...
10:59 < josibake> Talkless: did you install the correct udev?
10:59 < michaelfolkson> Ledger doesn't support testnet/signet right?
10:59 < Talkless> emzy: Ledger has second pin for passthraze, idk if there's mode to enter passphraze every time after tunring on
11:00 < josibake> lastly, any thoughts or questions on GUIX builds? (no worries if you didnt get that far)
11:00 < Talkless> josibake: Trezor desktop app worked without udev, and sudo ./hwi.py.. failed due to missing imports
11:00 < Talkless> (because .hwi installed in local user while sudo runs as root..?)
11:00 < emzy> josibake: GUIX build is still runing. And looks good on Debian 11.
11:01 < Talkless> "sudo ./hwi.py installudevrules" works now :|
11:01 < josibake> emzy: nice! thanks for running it
11:01 < Talkless> idk what was wrong
11:01 < josibake> also, we are at time!
11:01 < josibake> #stopmeeting
11:01 < hernanmarino> Also, i couldn't find a way to provide my passphrase through bitcoin core. But I think that situation is expected in the current release, and we must interact through hwi before using core, right ??
11:01 < janb> josibake: thanks for hosting
11:01 < josibake> big thanks to everyone for joining and taking time to help test bitcoin core!
11:01 < jnewbery> thanks josibake!
11:01 < schmidty> thanks josibake! 
11:01 < emzy> btw. For GUIX builds there is an IRC channel: #bitcoin-core-builds
11:01 < Talkless> thans josibake :)
11:02 < Talkless> thanks
11:02 < josibake> don't forget to update the testing ticket! especially if you found something interesting 
11:02 < theStack> thanks josibake 
11:02 < hernanmarino> thanks josiebake
11:02 < emzy> thanks josibake!
11:02 < darius27> thanks for hosting josibake! and the testing guide is great
11:02 < michaelfolkson> Thanks josibake, awesome release testing notes too. Made me think about what I should be doing in PR testing generally :)
11:02 < josibake> hernanmarino: this is a pretty new feature, so afaik, hwi is the only hardware wallet interface that exists right now. in theory, anyone can write one tho
11:03 < hernanmarino> josibake: thanks
11:03 < josibake> michaelfolkson: thanks! gotta give credit to jarolrod, tho. i mostly copied his 0.21 testing guide 
11:03 -!- observer22 [~observer@cpe-23-242-148-67.socal.res.rr.com] has quit [Quit: Connection closed]
11:05 < Talkless> I do see emu.py producing log output into console when I click "Create new wallet', so it does communicate...
11:05 -!- sugarjig [~sugarjig@c-73-152-17-189.hsd1.va.comcast.net] has quit [Quit: Connection closed]
11:06 -!- jiii [~jiii@6.69.broadband9.iol.cz] has left #bitcoin-core-pr-reviews []
11:06 < josibake> Talklass: interesting, can you try manually installing the udev file? there should be a link in the guide and you just copy and paste the contents, keep the same filename
11:06 < josibake> Talkless: ^
11:06 -!- Azorcode [~Azorcode@186-88-143-193.genericrev.cantv.net] has quit [Quit: Connection closed]
11:07 < Talkless> josibake: aren't udev rules for physical (like USB) devices?
11:07 < Talkless> enumerate does see it:
11:07 < Talkless> $ ./hwi.py enumerate
11:07 < Talkless> [{"type": "trezor", "path": "udp:127.0.0.1:21324", "model": "trezor_t_simulator", "needs_pin_sent": false, "needs_passphrase_sent": false, "fingerprint": "c664c2b7"}, {"type": "keepkey", "model": "keepkey", "path": "udp:127.0.0.1:21324", "error": "Could not open client or get fingerprint information: Unsupported device", "code": -13}]
11:08 -!- Guest3 [~Guest3@2607:fb90:12c4:b241:65b4:67c1:2fc4:eb58] has joined #bitcoin-core-pr-reviews
11:08 < Talkless> It seems that HWI asks emulator for features:
11:08 < Talkless> 7120702618 trezor.wire DEBUG received message contents:                                                                                                                                                                                     
11:08 < Talkless> GetFeatures {}
11:09 < larryruane> #endmeeting
11:09 < Talkless> and something is returned from emulator:
11:09 < Talkless> 7120705867 trezor.wire DEBUG 0:0 write: Features
11:09 < Talkless> 7120709642 trezor.loop DEBUG finish: <generator object 'handle_session' at 7f062fcc74c0>
11:10 -!- Guest3 [~Guest3@2607:fb90:12c4:b241:65b4:67c1:2fc4:eb58] has quit [Client Quit]
11:11 < josibake> larryruane: whoops, wrong command. thanks
11:11 -!- Guest96 [~Guest96@2607:fb90:12c4:b241:65b4:67c1:2fc4:eb58] has joined #bitcoin-core-pr-reviews
11:11 < larryruane> :)
11:12 -!- Guest96 [~Guest96@2607:fb90:12c4:b241:65b4:67c1:2fc4:eb58] has quit [Client Quit]
11:13 < josibake> Talkless: gotta run, but ill mess around with it a bit more tomorrow. i do know when i first setup the emulator i was getting a device unsupported error. i _think_ i solved it by installing udev, but that might only be relevant if it is a physical device. 
11:17 < darius27> is there a way i can check tor is running correctly? My RC node isn't doing IBD when I only have Tor v2 addresses in the config file 
11:18 < Talkless> darius27: you could add debug=tor 
11:18 < darius27> I think the version of tor I'm using doesn't support v2? I get this output in the terminal running tor:
11:18 < darius27> Aug 18 11:18:18.000 [warn] Tried to connect to a v2 onion address, but this version of Tor no longer supports them. Please encourage the site operator to upgrade. For more information see https://blog.torproject.org/v2-deprecation-timeline.
11:21 -!- sriramdvt [~sriramdvt@183.83.132.111] has quit [Quit: Connection closed]
11:21 < darius27> Talkless thanks, i'm getting this when i added debug=tor
11:21 < darius27> 2021-08-18T18:21:14Z Socks5() connect to z5nt64xh4d3vnll2.onion:8333 failed: general failure
11:25 < Talkless> darius27: well v2 is no longer supported as per release notes?
11:26 < darius27> i can connect to the v3 nodes, so I think it's just my version of tor that doesn't support v2 addresses
11:27 < michaelfolkson> That is good darius27. v2 addresses are deprecated
11:27 < darius27> Talkless i was expecting to be able to do IBD with tor v2 nodes based on this part of the testing guide  "You should get a json response about your connected peers and you will see onion v2 addresses, matching the list you specified in bitcoin.conf. This is because we can still connect to peers for initial block download, but will ignore them
11:27 < darius27> otherwise."
11:27 < Talkless> darius27: oh you can't do even IBD?
11:28 < sipa> darius27: which tor version do you have?
11:28 < sipa> tor --version
11:28 < darius27> yeah, but i think that's because the latest version of tor i downloaded doesn't let me connect to them
11:28 -!- naiza [~naiza@180.188.251.67] has quit [Quit: Connection closed]
11:28 < darius27> $ tor --version
11:28 < darius27> Tor version 0.4.6.7.
11:28 < darius27> Tor is running on Darwin with Libevent 2.1.12-stable, OpenSSL 1.1.1k, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
11:28 < darius27> Tor compiled with clang version 12.0.5
11:28 < sipa> darius27: 0.4.6 doesn't support v2 anymore
11:29 < darius27> ah okay, thanks sipa! 
11:29 < sipa> https://blog.torproject.org/v2-deprecation-timeline
11:33 -!- b10c [uid500648@id-500648.charlton.irccloud.com] has quit [Quit: Connection closed for inactivity]
11:35 -!- svav [~svav@82-69-86-143.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 240 seconds]
11:36 -!- hello35 [~hello@66.135.147.73] has quit [Quit: Connection closed]
11:38 -!- chunkblob [~chunkblob@cpe-184-153-97-30.nyc.res.rr.com] has quit [Quit: Connection closed]
11:42 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Quit: ZNC - http://znc.sourceforge.net]
11:43 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
12:15 -!- Blue_Moon [~Blue_Moon@189.149.186.140] has quit [Quit: Connection closed]
12:26 -!- darius27 [~darius27@c-73-252-226-175.hsd1.ca.comcast.net] has quit [Quit: Ping timeout (120 seconds)]
12:36 -!- muhblockchain [~muhblockc@user/muhblockchain] has joined #bitcoin-core-pr-reviews
12:49 -!- shaman [~shaman@61.0.94.146] has quit [Quit: Leaving]
14:13 -!- hernanmarino [~hernanmar@OL121-235.fibertel.com.ar] has quit [Quit: Leaving]
14:40 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
17:12 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
17:14 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 252 seconds]
17:16 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
17:19 -!- lukedashjr [~luke-jr@user/luke-jr] has quit [Ping timeout: 268 seconds]
17:22 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 240 seconds]
17:27 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
17:29 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
17:32 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 252 seconds]
17:34 -!- lukedashjr [~luke-jr@user/luke-jr] has quit [Ping timeout: 240 seconds]
17:35 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
17:42 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 240 seconds]
17:57 -!- tecnecio [~tecnecio_@214.red-2-139-121.dynamicip.rima-tde.net] has joined #bitcoin-core-pr-reviews
18:05 -!- tecnecio [~tecnecio_@214.red-2-139-121.dynamicip.rima-tde.net] has quit [Quit: Leaving]
18:05 -!- davterra [~davterra@143.198.56.186] has quit [Quit: Leaving]
18:18 -!- belcher_ [~belcher@user/belcher] has joined #bitcoin-core-pr-reviews
18:22 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 268 seconds]
18:25 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
20:33 -!- davterra [~davterra@143.198.56.186] has joined #bitcoin-core-pr-reviews
23:09 -!- tralfaz [~davterra@143.198.56.186] has joined #bitcoin-core-pr-reviews
23:10 -!- davterra [~davterra@143.198.56.186] has quit [Read error: Connection reset by peer]
23:21 -!- belcher_ is now known as belcher
--- Log closed Thu Aug 19 00:00:43 2021