--- Log opened Wed Mar 27 00:00:09 2024
01:25 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has joined #bitcoin-core-pr-reviews
01:29 -!- jamesob4 [~jamesob@108.44.248.162] has joined #bitcoin-core-pr-reviews
01:30 -!- jamesob [~jamesob@108.44.248.162] has quit [Ping timeout: 252 seconds]
01:30 -!- jamesob443688173 [~jamesob@108.44.248.162] has quit [Ping timeout: 252 seconds]
01:30 -!- jamesob4 is now known as jamesob
02:01 -!- Guest36 [~Guest36@90-178-102-136.rcl.o2.cz] has joined #bitcoin-core-pr-reviews
02:23 -!- cbergqvist [~chris@84-216-185-21.customers.ownit.se] has joined #bitcoin-core-pr-reviews
02:32 < cbergqvist> Hi! In case this is a useful reminder for anyone - if you plan to attend the PR review club later today and want to prepare, it would be good to go through that section before the meeting: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/27.0-Release-Candidate-Testing-Guide#preparation
03:34 < glozow> cbergqvist: 👍
04:12 -!- Guest36 [~Guest36@90-178-102-136.rcl.o2.cz] has quit [Quit: Client closed]
04:26 -!- Jamal [~Jamal@105.67.4.24] has joined #bitcoin-core-pr-reviews
04:27 -!- Jamal [~Jamal@105.67.4.24] has quit [Client Quit]
05:16 -!- the_mariner [~Thunderbi@2804:29b8:518d:a89:595d:881c:a194:1f9a] has quit [Ping timeout: 240 seconds]
05:39 -!- pablomartin [~pablomart@217.146.93.18] has joined #bitcoin-core-pr-reviews
06:16 -!- kozo [~kozo@90-178-102-136.rcl.o2.cz] has joined #bitcoin-core-pr-reviews
06:34 -!- the_mariner [~Thunderbi@177.37.233.227] has joined #bitcoin-core-pr-reviews
06:36 -!- kozo [~kozo@90-178-102-136.rcl.o2.cz] has quit [Ping timeout: 250 seconds]
06:57 -!- what123 [~what123@169.150.198.70] has joined #bitcoin-core-pr-reviews
07:01 -!- kozo [~kozo@90-178-102-136.rcl.o2.cz] has joined #bitcoin-core-pr-reviews
07:01 -!- what123 [~what123@169.150.198.70] has quit [Remote host closed the connection]
07:31 -!- cbergqvist [~chris@84-216-185-21.customers.ownit.se] has quit [Quit: WeeChat 4.1.1]
07:31 -!- cbergqvist [~chris@84-216-185-21.customers.ownit.se] has joined #bitcoin-core-pr-reviews
07:40 -!- sr [~sr@154.61.62.194] has joined #bitcoin-core-pr-reviews
07:59 -!- kozo [~kozo@90-178-102-136.rcl.o2.cz] has quit [Quit: Client closed]
08:24 -!- kozo [~kozo@90-178-102-136.rcl.o2.cz] has joined #bitcoin-core-pr-reviews
08:51 -!- puchka [~puchka@185.203.122.199] has quit [Ping timeout: 255 seconds]
08:53 -!- puchka [~puchka@185.203.122.201] has joined #bitcoin-core-pr-reviews
08:59 -!- puchka [~puchka@185.203.122.201] has quit [Ping timeout: 256 seconds]
08:59 -!- puchka [~puchka@185.203.122.201] has joined #bitcoin-core-pr-reviews
09:12 -!- puchka [~puchka@185.203.122.201] has quit [Ping timeout: 268 seconds]
09:14 -!- puchka [~puchka@185.203.122.201] has joined #bitcoin-core-pr-reviews
09:19 -!- Guest32 [~Guest12@cust-west-par-46-193-0-235.cust.wifirst.net] has joined #bitcoin-core-pr-reviews
09:33 -!- Guest24 [~Guest70@2001:4898:e008:1:62a9:c579:dfd3:c27e] has joined #bitcoin-core-pr-reviews
09:44 -!- Guest24 [~Guest70@2001:4898:e008:1:62a9:c579:dfd3:c27e] has quit [Ping timeout: 250 seconds]
09:45 -!- vostrnad [~vostrnad@ip-62-245-75-70.bb.vodafone.cz] has joined #bitcoin-core-pr-reviews
09:49 -!- abcde [~abcde@169.150.198.70] has joined #bitcoin-core-pr-reviews
09:50 -!- vostrnad [~vostrnad@ip-62-245-75-70.bb.vodafone.cz] has quit [Ping timeout: 250 seconds]
09:50 -!- kozo [~kozo@90-178-102-136.rcl.o2.cz] has quit [Ping timeout: 250 seconds]
09:51 -!- angusp90 [~angusp@189.165.185.81.rev.sfr.net] has joined #bitcoin-core-pr-reviews
09:52 -!- angusp90 is now known as anangusp
09:54 -!- Guest86 [~Guest86@99.255.159.147] has joined #bitcoin-core-pr-reviews
09:55 -!- dzxzg [~dzxzg___@2601:14d:4f01:fe00::4d47] has joined #bitcoin-core-pr-reviews
09:55 -!- vostrnad [~vostrnad@ip-62-245-75-70.bb.vodafone.cz] has joined #bitcoin-core-pr-reviews
09:56 -!- ion- [~ion-@ppp-94-66-136-59.home.otenet.gr] has joined #bitcoin-core-pr-reviews
09:57 -!- marcofleon [~marcofleo@89-39-107-157.hosted-by-worldstream.net] has joined #bitcoin-core-pr-reviews
09:57 -!- kozo [~kozo@90-178-102-136.rcl.o2.cz] has joined #bitcoin-core-pr-reviews
09:59 -!- mayrf [~mayrf@41.66.99.4] has joined #bitcoin-core-pr-reviews
09:59 -!- Guest70 [~Guest70@2001:4898:e008:1:4a62:f22e:3037:a757] has joined #bitcoin-core-pr-reviews
09:59 -!- Jamal [~Jamal@196.112.239.208] has joined #bitcoin-core-pr-reviews
10:00 < cbergqvist> #startmeeting
10:00 < stickies-v> hi
10:00 < tdb3> hi
10:00 < dzxzg> hi
10:00 < marcofleon> Hi
10:00 < ion-> hi!
10:00 < vostrnad> hi
10:00 < glozow> hi
10:00 < Jamal> hi
10:00 < cbergqvist> Hello everyone! Welcome to another Bitcoin Core PR Review Club session.
10:00 < mayrf> hi
10:00 < cbergqvist> Today we are going to be testing the upcoming 27.0 release, following this guide:
10:00 < abubakarsadiq> hello
10:00 < cbergqvist> https://github.com/bitcoin-core/bitcoin-devwiki/wiki/27.0-Release-Candidate-Testing-Guide
10:01 -!- edilmedeiros [~user@2804:14c:658b:61c7:b52e:2bdc:3c8e:1439] has joined #bitcoin-core-pr-reviews
10:01 < marcofleon> woo!
10:01 < cbergqvist> For 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:01 -!- Guest79 [~Guest42@212.129.83.198] has joined #bitcoin-core-pr-reviews
10:01 < Guest79> hi
10:01 < cbergqvist> Please open the testing guide linked above and prepare for an hour of testing, education, and attempts at breaking ₿itcoin! 💥😄
10:01 < edilmedeiros> hi
10:01 -!- Guest24 [~Guest79@166.199.148.10] has joined #bitcoin-core-pr-reviews
10:01 < Guest70> hey all!
10:02 < cbergqvist> It was suggested to go through the “Preparation” section ahead of the meeting.
10:02 < cbergqvist> If you haven't, this is the time to download/compile the binaries, as per https://github.com/bitcoin-core/bitcoin-devwiki/wiki/27.0-Release-Candidate-Testing-Guide#preparation
10:02 -!- Guest63 [~Guest63@166.199.148.10] has joined #bitcoin-core-pr-reviews
10:02 -!- Guest24 [~Guest79@166.199.148.10] has quit [Client Quit]
10:03 < cbergqvist> If you are set up already, please continue through the guide and report back if you run into weird results/stumbling blocks.
10:03 -!- mayrf_ [~mayrf@80-108-88-245.cable.dynamic.surfer.at] has joined #bitcoin-core-pr-reviews
10:03 < cbergqvist> First though, could you please share which OS you're using and whether you have/are compiling from source using tags/v27.0rc1 or only using pre-compiled binaries?
10:03 < cbergqvist> NixOS v23.11 / Bitcoin Core v27.0rc1 from source, v25.1 and v26.0 pre-compiled.
10:03 < b10c> hi
10:04 < dzxzg> Fedora 39, I've built v27 from source, and I'm using release binaries for versions 25 and 26
10:04 < ion-> macos 14.3.1 (23D60) / Bitcoin Core v27.0rc1 from source, v25.1 and v26.0 pre-compiled.
10:04 < edilmedeiros> MacOS Sonoma 14.4 (dependencies installed with MacPorts instead of Brew) / Bitcoin Core v27.0rc1 from source, v25.1 and v26.0 pre-compiled.
10:04 < stickies-v> MacOS 14.3.1, gonna test precompiled bins today
10:04 < Jamal> macos 12.6.7 pre-compiled binaries too
10:04 < Guest63> PopOS 22.04 all precompiled
10:05 < mayrf_> nixos precompiled
10:05 < marcofleon> macOS 14.2 v27.0rc1 from source, 25.1 and 26.0 pre compiled
10:05 < abubakarsadiq> macOS 14.1.1/  built from source/ will test the v27r1 new features
10:05 < glozow> Ubuntu jammy, from source
10:05 -!- mayrf [~mayrf@41.66.99.4] has quit [Ping timeout: 260 seconds]
10:06 < cbergqvist> Remember that the testing guides are meant to be a *starting point* to get you started with testing.
10:06 < cbergqvist> Most of the individual changes are well tested during the review phase, when the code is introduced to the codebase. What's more complicated to test is how changes behave together on different configurations and user patterns. Therefore it's encouraged to do your own testing and experiments. Testing on Mainnet is encouraged when possible.
10:07 -!- dtapa [~dtapa@multiplan-G0-0-0-13-206-uacc01.spoph.embratel.net.br] has joined #bitcoin-core-pr-reviews
10:07 < cbergqvist> Please report your test findings under this issue: https://github.com/bitcoin/bitcoin/issues/29697
10:07 < cbergqvist> For feedback on the content of the guide itself please use: https://github.com/bitcoin/bitcoin/issues/29685
10:08 < cbergqvist> (But of course you can/should take the opportunity to report stuff you encounter here in the chat too).
10:09 < cbergqvist> If you are encountering issues getting set up, please let us know here and we'll try to help.
10:11 -!- Guest63 [~Guest63@166.199.148.10] has quit [Quit: Client closed]
10:12 -!- Naiyoma [~Naiyoma@196.207.134.149] has joined #bitcoin-core-pr-reviews
10:12 < edilmedeiros> I just stumbled on v27 asking for credentials to use the CLI that was not happening in the morning. I'll check if I missed something.
10:13 < stickies-v> cbergqvist: should we ask conceptual questions about the changes tested here too, if any?
10:13 < tdb3> edilmedeiros, it would be good to check the DATA_DIR_x env vars
10:13 < dzxzg> @edilmedeiros Did you bcli stop at the end of your previous session
10:13 < tdb3> Was it complaining about the cookie not being available?
10:14 -!- Jamal [~Jamal@196.112.239.208] has quit [Quit: Client closed]
10:14 < cbergqvist> stickies-v: yeah, let's try that
10:14 < edilmedeiros> Yes, cookie not available
10:14 < edilmedeiros> For the v2 transport section
10:14 -!- Jamal [~Jamal@196.112.239.208] has joined #bitcoin-core-pr-reviews
10:14 < edilmedeiros> datadirs were clean
10:14 < dzxzg> your bitcoind is probably still running and you'll have to kill it from your process manager
10:15 -!- Novo [uid605808@id-605808.lymington.irccloud.com] has joined #bitcoin-core-pr-reviews
10:15 < ion-> "mempool.dat v1/v2 compatibility" re-tested ok
10:15 -!- abcde [~abcde@169.150.198.70] has quit [Remote host closed the connection]
10:15 < dzxzg> SIGINT causes bitcoind to shut down gracefully afaik
10:16 < dzxzg> https://github.com/bitcoin/bitcoin/issues/11586#issuecomment-341737656
10:17 < edilmedeiros> Yes, killing it manually solved
10:17 < cbergqvist> If people have prepared and are waiting for a goahead to start running tests, this is it. :)
10:17 < cbergqvist> First test is the aforementioned mempool format change.
10:18 < cbergqvist> https://github.com/bitcoin-core/bitcoin-devwiki/wiki/27.0-Release-Candidate-Testing-Guide#mempooldat-v1v2-compatibility
10:18 < cbergqvist> This change makes it less likely for antivirus software to quarantine your mempool.dat file if a malicious transaction containing byte patterns classified as a virus enters your mempool.
10:19 < Guest86> wow cool
10:19 < Jamal> Finished testing mempool.dat v1/v2 compatibility
10:19 < Jamal> Test Ok
10:19 -!- grettke [~grettke@184-055-133-000.res.spectrum.com] has joined #bitcoin-core-pr-reviews
10:21 < ion-> "v2 Transport on by Default" re-tested ok
10:21 < mayrf_> Why would this quarantining happen? If an antivirus intentionally wants wants to mess with your node? 
10:21 -!- Guest32 [~Guest12@cust-west-par-46-193-0-235.cust.wifirst.net] has quit [Quit: Client closed]
10:22 < tdb3> Antivirus software detects patterns associated with malicious code/files.  It then can automatically quarantine files that match these patterns.
10:22 < edilmedeiros> retested mempool v1/v2 comp and v2 transport on by default
10:22 < dzxzg> Some types of scripts, including OP_RETURN outputs, allow including arbitrary data in transactions
10:22 -!- anangusp [~angusp@189.165.185.81.rev.sfr.net] has quit [Quit: Client closed]
10:22 < tdb3> This disrupts Bitcoin Core's usage of the mempool.dat
10:22 < dzxzg> Including data that matches signatures in antivirus DB's, creates a DOS vector
10:23 < mayrf_> I see, thanks for explaining
10:23 < stickies-v> FYI when chaining commands after starting bitcoind, you can use `-daemonwait` instead of `-daemon` so the command doesn't return until the node is ready to be used, which is useful e.g. in the mempool v1/v2 tests
10:23 < tdb3> Previously, Bitcoin Core would store this data directly from transactions (which as dzxzg said, can contain arbitrary data from others).
10:23 < stickies-v> `bitcoind-test -daemonwait` instead of `bitcoind-test -daemon`
10:23 < tdb3> excellent idea
10:24 < tdb3> I'll make that change in the repo
10:24 < abubakarsadiq> https://www.irccloud.com/pastebin/pI03cpR1/
10:24 < Guest86> is this XORing logically happening after datacarrier=0 / permitbaremultisig=0 work to remove stuff from the mempool, or after ?
10:24 < mayrf_> Test ok
10:24 < ion-> "netinfo backward compatibility with pre-v26 nodes" re-tested ok
10:25 < Guest86> *sorry meant to say "... , or before" *
10:25 < abubakarsadiq> v2 Transport is working by default.
10:25 < abubakarsadiq>  ```./src/bitcoin-cli getnetworkinfo
10:25 < abubakarsadiq> {
10:25 < abubakarsadiq>   "version": 270000,
10:25 < abubakarsadiq>   "subversion": "/Satoshi:27.0.0/",
10:25 < abubakarsadiq>   "protocolversion": 70016,
10:25 < abubakarsadiq>   "localservices": "0000000000000c09",
10:25 < abubakarsadiq>   "localservicesnames": [
10:25 < abubakarsadiq>     "NETWORK",
10:25 < abubakarsadiq>     "WITNESS",
10:25 < abubakarsadiq>     "NETWORK_LIMITED",
10:25 < abubakarsadiq>     "P2P_V2"
10:25 < abubakarsadiq>   ],
10:25 < abubakarsadiq>   ```
10:26 < dzxzg> @abubakarsadiq is that after you've connected to the seed node or after you've made the manual `addnode` connection to the v2 peer
10:26 < edilmedeiros> "netinfo backward compatibility with pre-v26 nodes" went ok
10:26 < abubakarsadiq> Normal startup, So far I am not connected to any v2 peer, after I did `getpeerinfo`.
10:26 < abubakarsadiq> Any v2 peer I can connect with manually :)
10:27 < stickies-v> Guest86: this is about dumping your mempool to disk, so it would only affect stuff that's in your mempool, and not the stuff you're filtering out through policy, because it doesn't get into your mempool
10:27 < cbergqvist> Guest86: if you reject OP_RETURN data it will probably not get into your mempool.dat to be XORed, no. But there may be other ways of inscribing data..
10:27 < dzxzg> The v2 seednode won't necessarily gossip v2 peers to you, but you can inspect debug.log to see that the `addrfetch` connection was made over v2
10:27 -!- dtapa [~dtapa@multiplan-G0-0-0-13-206-uacc01.spoph.embratel.net.br] has quit [Quit: Client closed]
10:27 < Naiyoma> "mempool.dat v1/v2 compatibility" Test Ok
10:27 < stickies-v> mempool.dat v1/v2 test successful 👍
10:29 < glozow> abubakarsadiq: I'll dm you an address
10:29 < dzxzg> mempool.dat v1/v2 test worked
10:29 < abubakarsadiq> Thanks, so far from debug.log
10:29 < abubakarsadiq> ```
10:29 < abubakarsadiq>  [net] start sending v2 handshake to peer=11
10:29 < abubakarsadiq>  [net] socket closed for peer=11
10:29 < abubakarsadiq>  [net] disconnecting peer=11
10:29 < abubakarsadiq> [net] retrying with v1 transport protocol for peer=11
10:29 < abubakarsadiq> ```
10:30 -!- Guest5 [~Guest5@2607:fb90:2db5:20ed:3914:33d5:880c:de8a] has joined #bitcoin-core-pr-reviews
10:32 < cbergqvist> The second test which some are already running is "v2 Transport on by Default" - https://github.com/bitcoin-core/bitcoin-devwiki/wiki/27.0-Release-Candidate-Testing-Guide#v2-transport-on-by-default
10:32 < cbergqvist> This enables encrypted communication by default, even on IPv4/IPv6.
10:33 < cbergqvist> Problem is just finding nodes supporting it. :)
10:33 < dzxzg> @abubakarsadiq, do you have anything like: 
10:33 < dzxzg> 2024-03-16T17:15:05Z New addr-fetch v2 peer connected: version: 70016, blocks=187042, peer=0
10:33 < dzxzg> in your debug.log? AFAIK it is expected that we attempt a v2 connection to peers first before reattempting as v1
10:34 < glozow> oh, are you on signet?
10:35 < dzxzg> Yes
10:35 < abubakarsadiq> No am on mainnet 
10:35 < dzxzg> Oh
10:35 < stickies-v> cbergqvist: hopefully, after releasing v27 automatically peering with v2 nodes should be more frequent 🤞
10:36 < abubakarsadiq> dzxzg: nothing like that
10:36 < cbergqvist> v26 nodes do support v2, but it's not enabled by default as I understand it. Will they reject v2 attempt by default, or is it just that they will try v1 first when initiating?
10:38 < Jamal> "v2 Transport on by Default" test successful
10:38 < mayrf_> "v2 Transport on by Default" test ok
10:39 < ion-> "v3 Transaction Policy" re-tested ok
10:39 < lightlike> cbergqvist: v26 nodes only support v2 connections if they are started with the  -v2transport option. If that option isn't used, they will reject v2 connections.
10:40 < dzxzg> @abubakarsadiq I have not verified if achow's mainnet node is v2, but the signet node is
10:41 < cbergqvist> lightlike: thanks, will be hard to find random peers on mainnet with it enabled then.
10:42 -!- Guest5 [~Guest5@2607:fb90:2db5:20ed:3914:33d5:880c:de8a] has quit [Quit: Client closed]
10:42 < cbergqvist> Next test: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/27.0-Release-Candidate-Testing-Guide#netinfo-backward-compatibility-with-pre-v26-nodes
10:43 < cbergqvist> Slightly more minor change, client/server version compatibility fix.
10:44 < mayrf_> "netinfo backward compatibility with pre-v26 nodes" test successful
10:44 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-pr-reviews
10:45 < achow101> dzxzg: all of my nodes have v2 enabled
10:47 < edilmedeiros> "v3 Transaction Policy" ok
10:47 < ion-> "CoinGrinder coin selection algorithm" re-tested ok
10:48 < Naiyoma> "v2 Transport on by Default" Test Ok
10:49 < dzxzg> abubakarsadiq: did you run your mainnet node with `dnsseed=0` and `fixedseeds=0`
10:51 < dzxzg> for the v2 test (if you're still on that test, if not no worries )
10:51 < cbergqvist> just tested with what dzxzg suggested + rm ~/.bitcoin/peers.dat + anchors.dat, started bitcoind, then used bitcoin-cli addnode bitcoin.achow101.com add
10:51 < abubakarsadiq> no I did normal ./configure and ./src/bitcoind to see if I will get a V2 peer in the wild.
10:52 < abubakarsadiq> But I connected successfully to a V2 peer from glozow 
10:53 < dzxzg> oh I see, my mistake
10:53 < Jamal> "v3 Transaction Policy" test Ok
10:54 < edilmedeiros> coingrinder test ok. Quite impressive to see such a big transaction, it was never a use case for me.
10:56 < mayrf_> "v3 Transaction Policy" test successful
10:57 < ion-> "migratewallet RPC is no longer experimental" re-tested ok
10:57 < ion-> Completed all tests - ok
10:58 < marcofleon> edilmedeiros Agreed, it was cool for me to see too. Having something like coingrinder in core just makes sense with fees getting higher
10:59 < cbergqvist> Thanks everyone for joining and testing! Please continue to see if you can break the release. :)
10:59 < edilmedeiros> " migratewallet RPC is no longer experimental" ok
10:59 < edilmedeiros> Completed all tests
10:59 < tdb3> Thanks everyone
10:59 < edilmedeiros> Thanks everyone
11:00 < ion-> That was fun again!
11:00 < edilmedeiros> I'll put some more time trying to break things.
11:00 < Naiyoma> "v3 Transaction Policy" Test Ok
11:00 < cbergqvist> (Meeting format inspired by kouloumos (https://bitcoincore.reviews/v24-rc-testing))
11:00 < cbergqvist> #endmeeting
11:00 -!- kozo [~kozo@90-178-102-136.rcl.o2.cz] has quit [Quit: Client closed]
11:00 < mayrf_> Cool Stuff, thank you guys!
11:03 < stickies-v> thanks for putting this wonderful guide together tdb3 dzxzg cbergqvist marcofleon !
11:03 -!- Guest79 [~Guest42@212.129.83.198] has quit [Quit: Client closed]
11:07 -!- vostrnad [~vostrnad@ip-62-245-75-70.bb.vodafone.cz] has quit [Quit: Client closed]
11:09 -!- mayrf [~mayrf@80-108-88-245.cable.dynamic.surfer.at] has joined #bitcoin-core-pr-reviews
11:11 -!- mayrf_ [~mayrf@80-108-88-245.cable.dynamic.surfer.at] has quit [Ping timeout: 268 seconds]
11:12 -!- marcofleon [~marcofleo@89-39-107-157.hosted-by-worldstream.net] has quit [Quit: Client closed]
11:13 -!- Guest12 [~Guest12@cust-west-par-46-193-0-235.cust.wifirst.net] has joined #bitcoin-core-pr-reviews
11:13 -!- Guest86 [~Guest86@99.255.159.147] has quit [Quit: Client closed]
11:15 -!- Guest12 [~Guest12@cust-west-par-46-193-0-235.cust.wifirst.net] has quit [Client Quit]
11:15 -!- mayrf [~mayrf@80-108-88-245.cable.dynamic.surfer.at] has quit [Quit: Leaving]
11:15 -!- Talkless [~Talkless@mail.dargis.net] has quit [Ping timeout: 255 seconds]
11:16 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-pr-reviews
11:17 -!- ottosch [~otto@185.195.232.135] has joined #bitcoin-core-pr-reviews
11:18 -!- Talkless [~Talkless@mail.dargis.net] has quit [Client Quit]
11:21 -!- edilmedeiros [~user@2804:14c:658b:61c7:b52e:2bdc:3c8e:1439] has quit [Quit: ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.1)]
11:23 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-pr-reviews
11:30 -!- ion- [~ion-@ppp-94-66-136-59.home.otenet.gr] has quit [Quit: Client closed]
11:31 -!- Guest70 [~Guest70@2001:4898:e008:1:4a62:f22e:3037:a757] has quit [Quit: Client closed]
11:32 -!- Naiyoma [~Naiyoma@196.207.134.149] has quit [Quit: Client closed]
11:38 -!- Jamal [~Jamal@196.112.239.208] has quit [Quit: Client closed]
11:49 -!- sr [~sr@154.61.62.194] has quit [Quit: Client closed]
11:52 -!- Talkless [~Talkless@mail.dargis.net] has quit [Ping timeout: 264 seconds]
12:06 -!- ottosch [~otto@185.195.232.135] has quit [Quit: Konversation terminated!]
12:44 -!- dzxzg [~dzxzg___@2601:14d:4f01:fe00::4d47] has quit [Remote host closed the connection]
12:44 -!- dzxzg [~dzxzg___@2601:14d:4f01:fe00::4d47] has joined #bitcoin-core-pr-reviews
13:04 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-pr-reviews
13:06 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds]
13:09 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-pr-reviews
13:10 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 256 seconds]
13:11 -!- dzxzg [~dzxzg___@2601:14d:4f01:fe00::4d47] has quit [Ping timeout: 260 seconds]
13:11 -!- dzxzg [~dzxzg___@2601:14d:4f01:fe00::4d47] has joined #bitcoin-core-pr-reviews
13:16 -!- dzxzg [~dzxzg___@2601:14d:4f01:fe00::4d47] has quit [Ping timeout: 260 seconds]
14:28 -!- Jamal [~Jamal@41.140.78.251] has joined #bitcoin-core-pr-reviews
14:58 -!- Jamal [~Jamal@41.140.78.251] has quit [Quit: Client closed]
16:12 -!- the_mariner [~Thunderbi@177.37.233.227] has quit [Ping timeout: 252 seconds]
16:34 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has quit [Quit: Connection closed for inactivity]
18:22 -!- pablomartin [~pablomart@217.146.93.18] has quit [Remote host closed the connection]
18:22 -!- pablomartin [~pablomart@217.146.93.18] has joined #bitcoin-core-pr-reviews
20:14 -!- pablomartin [~pablomart@217.146.93.18] has quit [Remote host closed the connection]
20:14 -!- pablomartin [~pablomart@217.146.93.18] has joined #bitcoin-core-pr-reviews
20:36 -!- pablomartin [~pablomart@217.146.93.18] has quit [Ping timeout: 264 seconds]
21:24 -!- Guest43 [~Guest43@c188-151-237-158.bredband.tele2.se] has joined #bitcoin-core-pr-reviews
21:25 -!- Guest43 [~Guest43@c188-151-237-158.bredband.tele2.se] has quit [Client Quit]
23:37 -!- grettke [~grettke@184-055-133-000.res.spectrum.com] has quit [Quit: grettke]
--- Log closed Thu Mar 28 00:00:10 2024