--- Log opened Fri Dec 17 00:00:03 2021
00:02 -!- zonemix [~zonemix@216.16.35.204] has quit [Ping timeout: 245 seconds]
00:07 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
00:10 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
00:12 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
00:19 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
00:24 < vasild> ACK achow101 wallet maintainer
00:35 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 240 seconds]
00:44 -!- zonemix [~zonemix@216.16.35.204] has joined #bitcoin-core-dev
00:44 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
00:46 -!- earnestly [~earnest@user/earnestly] has joined #bitcoin-core-dev
00:48 -!- zonemix [~zonemix@216.16.35.204] has quit [Ping timeout: 240 seconds]
00:49 -!- gleb74 [~gleb@178.150.137.228] has quit [Ping timeout: 268 seconds]
00:50 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
00:51 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
00:52 -!- Guest7824 [~Guest78@183.233.81.228] has joined #bitcoin-core-dev
00:52 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
00:53 -!- Guest7824 [~Guest78@183.233.81.228] has quit [Client Quit]
01:06 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
01:15 -!- zonemix [~zonemix@216.16.35.204] has joined #bitcoin-core-dev
01:20 -!- zonemix [~zonemix@216.16.35.204] has quit [Ping timeout: 260 seconds]
01:25 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 256 seconds]
01:27 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
01:31 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 240 seconds]
01:32 < darosior> ACK achow101 maintainer
01:37 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
01:39 -!- zonemix [~zonemix@216.16.35.204] has joined #bitcoin-core-dev
01:41 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 268 seconds]
01:44 -!- zonemix [~zonemix@216.16.35.204] has quit [Ping timeout: 240 seconds]
01:49 -!- gnaf [~pi@86-91-224-60.opennet.kpn.net] has joined #bitcoin-core-dev
01:56 -!- jtrag_ is now known as jtrag
02:03 -!- kexkey [~kexkey@static-198-54-132-121.cust.tzulo.com] has quit [Ping timeout: 252 seconds]
02:04 -!- kexkey [~kexkey@static-198-54-132-105.cust.tzulo.com] has joined #bitcoin-core-dev
02:11 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
02:20 -!- zonemix [~zonemix@216.16.35.204] has joined #bitcoin-core-dev
02:24 -!- zonemix [~zonemix@216.16.35.204] has quit [Ping timeout: 240 seconds]
02:30 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 256 seconds]
02:34 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
02:38 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 268 seconds]
02:38 -!- jtrag__ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
02:38 -!- jtrag__ is now known as jtrag
02:39 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Ping timeout: 276 seconds]
02:42 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 260 seconds]
02:47 -!- jtrag [~jtrag@user/jtrag] has quit [Read error: Connection reset by peer]
02:47 -!- zonemix [~zonemix@216.16.35.204] has joined #bitcoin-core-dev
02:48 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
02:52 -!- zonemix [~zonemix@216.16.35.204] has quit [Ping timeout: 256 seconds]
02:52 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
02:53 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
02:56 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 256 seconds]
02:57 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has quit [Quit: ZzzZ]
02:59 < glozow> ACK giving fanquake permission to block accounts posting spam. Framing it as a "power" is a misrepresentation; it's always just cleaning up meaningless gibberish afaict. Requiring him to ask someone else does nothing but slow progress on the repo.
02:59 -!- jtrag_ is now known as jtrag
03:02 -!- jtrag [~jtrag@user/jtrag] has quit [Read error: Connection reset by peer]
03:02 < glozow> ACK achow101 wallet maintainer, imo it's very appropriate for someone with extensive knowledge+authorship of the wallet codebase to maintain it
03:03 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
03:04 < earnestly> glozow: ('accounts posting spam' don't exist as a category external to 'accounts posting not-spam' and so the power to block accounts encompasses both)
03:06 < glozow> earnestly: it would be extremely obvious if an account posting not-spam was blocked, so I see no risk of anybody abusing the privilege.
03:06 < earnestly> Yeah I don't disagree, but the framing isn't wrong
03:07 < earnestly> (More a limitation of github really)
03:07 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
03:13 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
03:14 -!- jtrag [~jtrag@user/jtrag] has quit [Read error: Connection reset by peer]
03:14 -!- jtrag_ [~jtrag@user/jtrag] has quit [Read error: Connection reset by peer]
03:15 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
03:17 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Ping timeout: 276 seconds]
03:21 -!- zonemix [~zonemix@216.16.35.204] has joined #bitcoin-core-dev
03:22 < glozow> earnestly: yeah it'd be nice if github could automatically block when obvious spam is obvious
03:25 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 268 seconds]
03:26 < earnestly> glozow: Hm, I was thinking more about multiple confirmations needed for an action
03:26 -!- mikehu44 [~quassel@gateway/vpn/pia/mikehu44-jc] has joined #bitcoin-core-dev
03:27 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
03:27 -!- jtrag is now known as Guest9045
03:27 -!- zonemix [~zonemix@216.16.35.204] has quit [Ping timeout: 240 seconds]
03:28 < laanwj> the goal was be to speed things up, not slow them down even further
03:28 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
03:29 < glozow> laanwj: +1
03:30 -!- Guest9045 [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
03:30 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
03:30 < laanwj> i'm not sure what the fear here is, it seems to me the community around bitcoin dev is sufficiently diffuse and loosely organized that there's ton of ways for someone who is banned in error to have recourse
03:31 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
03:32 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 256 seconds]
03:33 < laanwj> like just that fanquake has disagreed with you on an issue once or refused to merge it doesn't mean he'll just ban you now instead, that was definitely not the idea, there's quite some arguing in bad faith going on
03:37 < fanquake> i guess people are concerned that after 8-9 years of reputation building and project contributions, for some reason I'm going to undermine it all by abusing the ability to block people on GitHub
03:37 < laanwj> yessss
03:37 < laanwj> block block block you're all blocked
03:37 < fanquake> At this point I really don't care, this discussion has already wasted too much bandwidth.
03:37 < fanquake> I'd much prefer it if people spent that time scrutinising the code I write, and merge. The build system & related code is an area that could always use more eyes over it.
03:37 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Ping timeout: 276 seconds]
03:38 < laanwj> agree
03:38 < earnestly> fanquake: If it matters, I already trust your pgp for signed commits
03:38 < laanwj> it's really a distortion of what matters
03:38 < earnestly> So the ability to block accounts is pretty minor compared to that
03:40 < laanwj> and what the risks are
03:46 < michaelfolkson> Sorry, unrelated question. Where's the dev wiki gone in the Core repo?
03:46 < laanwj> thanks for the easy question. it's at https://github.com/bitcoin-core/bitcoin-devwiki/wiki
03:47 < michaelfolkson> Thanks, the tab has disappeared :)
03:48 < laanwj> i haven't noticed anything different in that regard
03:48 < michaelfolkson> I thought it was this new Projects thing moving the tab
03:49 < laanwj> the new projects thing did make me worry yesterday, it looked like all the projects were gone
03:49 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
03:49 < laanwj> i don't understand why there's Projects [beta] and Projects now it confuses me but i'm sure it will seem normal soon enough
03:51 < michaelfolkson> On the permissions thing, it is more than just blocking right? An owner could say remove you as a co-owner right laanwj?
03:51 < michaelfolkson> I'm using "owner" as the GitHub definition
03:52 < laanwj> michaelfolkson: yes. sometimes i wish they did
03:53 < michaelfolkson> I don't think there's an argument against fanquake whatsoever but I think we generally all trust laanwj's stewardship after all these years and so adding someone new makes some people uncomfortable
03:54 < michaelfolkson> But if someone is to be added fanquake ticks all the boxes imo
03:54 -!- Guest52 [~Guest52@188.134.84.205] has joined #bitcoin-core-dev
03:55 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Ping timeout: 276 seconds]
03:57 -!- Guest52 [~Guest52@188.134.84.205] has quit [Client Quit]
03:58 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
03:58 < bitcoin-git> [bitcoin] shaavan opened pull request #23801: Refactor: Change time variable type from int64_t to std::chrono::seconds in net_processing.cpp (master...time_in_seconds_refactor) https://github.com/bitcoin/bitcoin/pull/23801
03:58 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
03:58 < laanwj> michaelfolkson: agree
03:59 -!- jtrag_ is now known as jtrag
03:59 < glozow> laanwj: do you have any objections to it? you're the person who would grant permissions right?
03:59 < michaelfolkson> But yeah it is a credit to yourself laanwj that we generally all trust your stewardship :)
04:00 < michaelfolkson> (I guess I shouldn't project my views on others without confirming but I'm sure that's the case)
04:00 -!- zonemix [~zonemix@216.16.35.204] has joined #bitcoin-core-dev
04:03 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
04:07 < laanwj> glozow: no objections myself, but i do think it's important that people developing bitcoin core widely agree on it (which seems to be the case)
04:08 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 256 seconds]
04:08 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
04:14 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Ping timeout: 276 seconds]
04:15 < michaelfolkson> In normal times I'm sure it will be an irrelevance. It is just those stressful, strained times when under pressure someone could do something they later regret
04:17 < michaelfolkson> But thankfully/hopefully they seem to occur very rarely
04:19 < MarcoFalke> I don't think fanquake has ever done something they regretted later. I also hope no one is stressed. Taking time off might fix stress.
04:22 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 276 seconds]
04:22 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
04:23 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
04:24 < glozow> laanwj: indeed!
04:25 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
04:26 -!- bomb-on [~bomb-on@213.220.127.153] has joined #bitcoin-core-dev
04:27 -!- jtrag_ is now known as jtrag
04:28 < michaelfolkson> There's no rush, take some time off and hopefully come back refreshed in the new year laanwj :)
04:29 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
04:30 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
04:31 -!- jtrag__ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
04:33 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 256 seconds]
04:34 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
04:36 -!- jtrag__ is now known as jtrag
04:39 -!- bomb-on [~bomb-on@213.220.127.153] has quit [Read error: Connection reset by peer]
04:43 < provoostenator> ack en congrats achow101 wallet maintainer
04:44 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
04:45 < michaelfolkson> +1
04:46 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 240 seconds]
04:46 -!- jtrag_ [~jtrag@user/jtrag] has quit [Client Quit]
04:46 -!- jtrag [~jtrag@user/jtrag] has quit [Read error: Connection reset by peer]
04:51 < provoostenator> fanquake: carefully building a reputation over many years and then suddenly destroying it, is a common theme in this industry.  But usually not by blocking spammers on Github :-)
05:01 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
05:05 -!- zonemix [~zonemix@216.16.35.204] has quit [Ping timeout: 245 seconds]
05:08 < meshcollider> Why block spammers, they're some of our most active PR and issue reviewers :)
05:10 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
05:14 < meshcollider> Also I have no idea why Luke's lone objection is still holding things up re: fanquake. Just ignore him and do it, his opinion should not outweigh literally every other dev here...
05:15 < meshcollider> Consensus does not mean absolute agreement
05:19 -!- zonemix [~zonemix@216.16.35.204] has joined #bitcoin-core-dev
05:19 < michaelfolkson> I don't think it would just be Luke with concerns on granting co-owner privileges on the repo to an additional person(s) ignoring who that person is
05:20 < michaelfolkson> GitHub causes all sorts of unnecessary aggro
05:21 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
05:22 -!- masta`` [~oyster@user/masta/x-2645138] has joined #bitcoin-core-dev
05:23 < meshcollider> I thought those same people argue against putting any trust into GitHub and this specific repo anyway ...
05:24 < meshcollider> michaelfolkson: it is very clear that everyone speaking out is in favour except Luke and prayank, both for unrelated personal reasons
05:24 < michaelfolkson> You minimize trust in GitHub but it can't go to zero during high pressure scenarios
05:25 < meshcollider> ...
05:25 < michaelfolkson> And similarly with the Core repo I guess
05:25 -!- gleb74 [~gleb@178.150.137.228] has joined #bitcoin-core-dev
05:26 < laanwj> i mean in the end the github structure is contingent, it's not a representation of any formal power structure within bitcoin, if someone would really mess up the onus of development would simply move somewhere else
05:26 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 240 seconds]
05:27 < meshcollider> Exactly, and that's a negligible chance anyway when the only people in question are some of the longest-standing and trusted contributors...
05:27 < michaelfolkson> Right but it would be messy
05:27 < meshcollider> michaelfolkson: stop fearmongering
05:27 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has quit [Ping timeout: 276 seconds]
05:28 < michaelfolkson> I guess the elephant in the room is that some people wanted to remove Luke as a BIP editor earlier in the year. And rightly in my view laanwj didn't succumb to that pressure as there should be separation between Core and BIPs
05:28 < michaelfolkson> So I'm not deliberately fearmongering
05:29 < laanwj> it would but the same has to happen if we can't function efficiently and all project-level decisions are delayed or postponed indefinitely of course
05:29 < meshcollider> But along the same lines, kalle was added despite Luke's objections there. Luke is almost always the only one objecting to these things
05:29 < michaelfolkson> Maybe an additional owner of the repo would have acted differently in that scenario
05:30 < michaelfolkson> A BIP editor who had been performing that role on his own for what 5+ years?
05:32 < laanwj> that the bips repository is in the same organization is somewhat questionable in any case
05:33 < meshcollider> A single BIP editor is also not very decentralised so that's not a good thing.
05:33 < michaelfolkson> Right, we've got an additional one now which is great. But still people wanted to remove Luke
05:34 < michaelfolkson> [12:15:03]  <michaelfolkson> In normal times I'm sure it will be an irrelevance. It is just those stressful, strained times when under pressure someone could do something they later regret
05:35 < meshcollider> Also, admin perms on bitcoin/bitcoin doesn't require admin on bitcoin/BIPs
05:35 < MarcoFalke> I don't think anyone wanted to *remove* luke? I understood it as *adding* kalle, but I am not interested in rehashing the discussion here, so I probably shouldn't comment.
05:36 < meshcollider> michaelfolkson: anyway, please don't perpetuate this discussion when apparently you're not actually objecting, and please leave it to dev consensus
05:36 < laanwj> i'm not aware of anying asking to remove Luke either-just to add kallewoof
05:38 < earnestly> (In disagreements focus hard on creating a set of measurable steps to solve whatever problem is causing it, sideline much of the purposeless discussion)
05:40 < earnestly> From my lurking here I've not really seen anyone lay out a clear rationale for disagrement, usually because the other side refuses to acknowledge any aspect of it (and is quickly derailed into useless details), or because they don't have one.
05:40 < michaelfolkson> meshcollider: I'm not objecting to fanquake as an additional owner of the repo if we get an additional owner of the repo. Just thinking through long term implications and being told that is fearmongering
05:41 < michaelfolkson> But I'm repeating myself so I'll leave
05:41 < meshcollider> There is no problem. fanquake should be given permissions because the supermajority of devs agree and those against have no valid objections. That's it.
05:41 < jnewbery> meshcollider: +1
05:41 < earnestly> > there is no problem if we redefine the problem to exclude the problem
05:42 < earnestly> redefine the solution*
05:42 < michaelfolkson> Happy to provide links to attempts to remove Luke as a BIP editor if they are needed though
05:42 < earnestly> (Tbh, I've never seen a clear rationale given as to why fanquake shouldn't have permission to block accounts, usually because those against it don't explain themselves and there is no dialog with those who disagree.  But I could easily have missed it too)
05:44 < laanwj> so about reviewing PRs...
05:49 < _aj_> laanwj: awww, mum, do we have to?
05:50 < MarcoFalke> (Ok, some people might have asked for luke to be removed, but I hope my memory doesn't fail me telling me I was not one of them)
05:51 < laanwj> _aj_: hehehe yess u should all review a PR and then if you still have energy to argue u can get back to discussion here
05:54 -!- littlesh [~Username@bras-base-clwdon2201w-grc-49-174-89-151-72.dsl.bell.ca] has joined #bitcoin-core-dev
05:56 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
06:01 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 256 seconds]
06:05 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
06:14 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:91ca:42ff:4987:327] has quit [Remote host closed the connection]
06:14 -!- sirdigby727 [uid523338@id-523338.lymington.irccloud.com] has joined #bitcoin-core-dev
06:16 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
06:16 -!- rex4539 [~rex4539@gateway/tor-sasl/rex4539] has joined #bitcoin-core-dev
06:18 -!- littlesh [~Username@bras-base-clwdon2201w-grc-49-174-89-151-72.dsl.bell.ca] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
06:19 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has quit [Read error: Connection reset by peer]
06:21 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
06:28 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
06:31 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 268 seconds]
06:47 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has quit [Quit: ZzzZ]
06:50 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
06:50 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
06:53 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
06:54 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
06:55 -!- jtrag__ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
06:57 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 268 seconds]
06:59 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 256 seconds]
07:00 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
07:03 -!- roconnor [~roconnor@coq/roconnor] has quit [Quit: Konversation terminated!]
07:04 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 256 seconds]
07:14 -!- evbo [~bosats@2601:47:4383:560:c4f4:19bb:83c5:f3a3] has joined #bitcoin-core-dev
07:14 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:281c:2687:8a9e:e263] has joined #bitcoin-core-dev
07:18 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:281c:2687:8a9e:e263] has quit [Ping timeout: 240 seconds]
07:19 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
07:21 -!- zonemix [~zonemix@216.16.35.204] has quit [Remote host closed the connection]
07:21 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
07:21 -!- zonemix [~zonemix@216.16.35.204] has joined #bitcoin-core-dev
07:22 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
07:22 -!- jtrag__ is now known as jtrag
07:26 -!- zonemix [~zonemix@216.16.35.204] has quit [Ping timeout: 268 seconds]
07:30 -!- zonemix [~zonemix@216.16.35.204] has joined #bitcoin-core-dev
07:34 -!- zonemix [~zonemix@216.16.35.204] has quit [Ping timeout: 240 seconds]
07:35 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 268 seconds]
07:38 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
07:41 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
07:47 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
07:47 < bitcoin-git> [bitcoin] laanwj closed pull request #22786: Fix ScriptNum Tests (master...fix_scriptnum_test) https://github.com/bitcoin/bitcoin/pull/22786
07:47 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
07:48 -!- zonemix [~zonemix@216.16.35.204] has joined #bitcoin-core-dev
07:49 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
07:52 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
07:53 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
07:56 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
07:56 < bitcoin-git> [bitcoin] laanwj pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/8c0bd871fcf6...4ad59042b359
07:56 < bitcoin-git> bitcoin/master 65ef932 stratospher: [fuzz] Add D. J. Bernstein's implementation of ChaCha20
07:56 < bitcoin-git> bitcoin/master 4d0ac72 stratospher: [fuzz] Add fuzzing harness to compare both implementations of ChaCha20
07:56 < bitcoin-git> bitcoin/master 4ad5904 W. J. van der Laan: Merge bitcoin/bitcoin#22704: fuzz: Differential fuzzing to compare Bitcoin...
07:56 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
07:56 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
07:57 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
07:57 < bitcoin-git> [bitcoin] laanwj merged pull request #22704: fuzz: Differential fuzzing to compare Bitcoin Core's and D. J. Bernstein's implementation of ChaCha20 (master...diff-fuzz-chacha20) https://github.com/bitcoin/bitcoin/pull/22704
07:57 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
08:05 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:281c:2687:8a9e:e263] has joined #bitcoin-core-dev
08:08 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
08:08 -!- mikehu44 [~quassel@gateway/vpn/pia/mikehu44-jc] has quit [Ping timeout: 256 seconds]
08:09 -!- nanotube [~nanotube@user/nanotube] has quit [Ping timeout: 250 seconds]
08:09 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:281c:2687:8a9e:e263] has quit [Ping timeout: 240 seconds]
08:10 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
08:10 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #23803: ci: Disable s390x gui tests for now (master...2112-ciGUIs390x) https://github.com/bitcoin/bitcoin/pull/23803
08:10 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
08:11 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 245 seconds]
08:13 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:281c:2687:8a9e:e263] has joined #bitcoin-core-dev
08:16 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
08:16 < bitcoin-git> [bitcoin] glozow opened pull request #23804: validation: followups for de-duplication of packages (master...2021-12-dedup-packages) https://github.com/bitcoin/bitcoin/pull/23804
08:16 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
08:16 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:281c:2687:8a9e:e263] has quit [Remote host closed the connection]
08:18 -!- gnaf [~pi@86-91-224-60.opennet.kpn.net] has quit [Quit: Konversation terminated!]
08:18 -!- Guyver2_ [~Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
08:19 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Ping timeout: 240 seconds]
08:19 -!- Guyver2_ is now known as Guyver2
08:20 -!- saranshsharma [~saranshsh@59.93.229.54] has joined #bitcoin-core-dev
08:21 -!- noonien [~noonien@user/noonien] has quit [Quit: The Lounge - https://thelounge.chat]
08:22 -!- noonien [~noonien@user/noonien] has joined #bitcoin-core-dev
08:24 -!- sirdigby727 [uid523338@id-523338.lymington.irccloud.com] has quit [Quit: Connection closed for inactivity]
08:26 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:281c:2687:8a9e:e263] has joined #bitcoin-core-dev
08:28 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:281c:2687:8a9e:e263] has quit [Remote host closed the connection]
08:31 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:281c:2687:8a9e:e263] has joined #bitcoin-core-dev
08:35 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:281c:2687:8a9e:e263] has quit [Remote host closed the connection]
08:35 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:281c:2687:8a9e:e263] has joined #bitcoin-core-dev
08:37 -!- saranshsharma [~saranshsh@59.93.229.54] has quit [Ping timeout: 240 seconds]
08:43 < jeremyrubin> my bad on pushing if_unset_then_unset, can someone delete that branch from core? on a new laptop forgot to make my origin remote https
08:44 -!- noonien [~noonien@user/noonien] has quit [Quit: The Lounge - https://thelounge.chat]
08:44 -!- noonien [~noonien@user/noonien] has joined #bitcoin-core-dev
08:44 < jeremyrubin> `git remote set-url --push origin no_push` won't happen again :p
08:51 -!- zonemix [~zonemix@216.16.35.204] has quit [Ping timeout: 240 seconds]
08:51 -!- secondl1ght[m] [~secondl1g@2001:470:69fc:105::1:4fee] has joined #bitcoin-core-dev
08:59 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
09:02 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 252 seconds]
09:04 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:04 < bitcoin-git> [gui] hebasto opened pull request #509: Respect dialog modality and fix a regression in wallet unlock (master...211217-unlock) https://github.com/bitcoin-core/gui/pull/509
09:04 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
09:05 -!- zxrqmz88 [~private@2603-7000-1302-b6f3-99b9-c40f-27d9-40cb.res6.spectrum.com] has joined #bitcoin-core-dev
09:13 -!- jtrag_ is now known as jtrag
09:13 -!- jtrag is now known as methhead
09:13 -!- methhead is now known as Anubishit
09:13 -!- Anubishit is now known as trag
09:13 -!- trag is now known as jtrag
09:20 -!- gnaf [~pi@86-91-224-60.opennet.kpn.net] has joined #bitcoin-core-dev
09:40 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #bitcoin-core-dev
09:55 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
09:55 < bitcoin-git> [bitcoin] stratospher opened pull request #23806: fuzz: follow up for #22704 (master...follow-up-diff-fuzz-chacha20) https://github.com/bitcoin/bitcoin/pull/23806
09:55 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
10:00 < laanwj> jeremyrubin: done
10:06 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
10:08 -!- jtrag__ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
10:08 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
10:10 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
10:11 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
10:13 -!- jtrag__ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
10:16 -!- ZeroMaster [~webirc@95-42-105-42.ip.btc-net.bg] has joined #bitcoin-core-dev
10:17 -!- ZeroMaster [~webirc@95-42-105-42.ip.btc-net.bg] has quit [Client Quit]
10:17 -!- ZeroMaster [~webirc@95-42-105-42.ip.btc-net.bg] has joined #bitcoin-core-dev
10:21 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Changing host]
10:21 -!- jb55 [~jb55@user/jb55] has joined #bitcoin-core-dev
10:21 -!- jb55 [~jb55@user/jb55] has quit [Quit: jb55]
10:22 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #bitcoin-core-dev
10:22 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Changing host]
10:22 -!- jb55 [~jb55@user/jb55] has joined #bitcoin-core-dev
10:33 -!- Alexander10 [~Alexander@76-233-25-130.lightspeed.snantx.sbcglobal.net] has joined #bitcoin-core-dev
10:39 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
10:39 < bitcoin-git> [bitcoin] w0xlt opened pull request #23807: Remove GetAdjustedTime() from AddrMan (master...remove_adjusted_time_addrman) https://github.com/bitcoin/bitcoin/pull/23807
10:39 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
10:42 -!- Alexander10 [~Alexander@76-233-25-130.lightspeed.snantx.sbcglobal.net] has quit [Quit: Client closed]
10:46 -!- alexander97 [~alexander@2600:1700:6a00:2ea0:3590:45c0:876a:bb8c] has joined #bitcoin-core-dev
10:46 -!- alexander97 [~alexander@2600:1700:6a00:2ea0:3590:45c0:876a:bb8c] has quit [Quit: Leaving]
10:49 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has joined #bitcoin-core-dev
10:50 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
10:53 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
11:00 < achow101> #startmeeting
11:00 < core-meetingbot> Meeting started Fri Dec 17 19:00:18 2021 UTC.  The chair is achow101. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings.
11:00 < core-meetingbot> Available commands: action commands idea info link nick
11:00 < achow101> #bitcoin-core-dev Wallet Meeting: achow101 _aj_ amiti ariard BlueMatt cfields Chris_Stewart_5 darosior digi_james dongcarl elichai2 emilengler fanquake fjahr gleb glozow gmaxwell gwillen hebasto instagibbs jamesob jarolrod jb55 jeremyrubin jl2012 jnewbery jonasschnelli jonatack jtimon kallewoof kanzure kvaciral laanwj larryruane lightlike luke-jr maaku marcofalke meshcollider michagogo moneyball morcos nehan NicolasDorier paveljanik petertodd 
11:00 < achow101> phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild S3RK
11:00 < S3RK> hi
11:00 < sipa> hi
11:00 < achow101> any topics?
11:01 < sipa> none from me
11:01 < S3RK> bnb upper limit?
11:01 < achow101> #topic bnb upper limit (S3RK)
11:01 < core-meetingbot> topic: bnb upper limit (S3RK)
11:01 < sipa> i invoke murch
11:01 < Murch[m]> Hi
11:01 < S3RK> oh nice
11:01 < S3RK> so the current upper limit for bnb is not optimal
11:02 -!- ZeroMaster_ [~webirc@95-42-105-42.ip.btc-net.bg] has joined #bitcoin-core-dev
11:02 < S3RK> it's economically better to drop more than the current upper limit for fees rather than add an extra input and create change output
11:02 < S3RK> we can either 1) increase the limit or 2) drop the limit
11:02 < Murch[m]> Yeah, we ran some experiments removing the upper bound for the exact match window and that resulted in an overall lower cost
11:02 < michaelfolkson> hi
11:03 -!- ZeroMaster_ [~webirc@95-42-105-42.ip.btc-net.bg] has quit [Client Quit]
11:03 -!- prayank [~Prayank@103.211.191.71] has joined #bitcoin-core-dev
11:03 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Quit: Leaving]
11:03 < Murch[m]> S3RK: My current position would be that I'd be apprehensive about dropping the limit altogether.
11:03 -!- ZeroMaster [~webirc@95-42-105-42.ip.btc-net.bg] has quit [Quit: излезна от чата]
11:03 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
11:03 < achow101> if our calculation for the upper bound is incorrect, I would prefer to fix it rather than drop the limit entirely
11:03 < Murch[m]> If both Knapsack and SRD find very bad solutions, we may drop a ton of money to fees.
11:03 -!- ZeroMaster [~webirc@95-42-105-42.ip.btc-net.bg] has joined #bitcoin-core-dev
11:03 < S3RK> it's a bit tricky to calculate exact upper limit
11:03 < achow101> but IIRC part of the issue is that our drop to fees handling is independent of the selection algorithm
11:04 < Murch[m]> Right, but without an upper bound, BnB may end up returning a result that has a larger remainder than what's dropped and our transaction building ends up building a tx with a minuscule change
11:04 < S3RK> hm... I'd say that's a related but separate issue. Would love to discuss it as well, but let's talk about the bnb limit first
11:05 < Murch[m]> So, we could just post-filter BnB solutions to not use such a solution
11:05 < S3RK> Murch, why do you think knapsack wouldn't find the same solution but with change?
11:05 < achow101> the min change target
11:05 < Murch[m]> Because Knapsack minimizes the overshoot past minChange
11:05 < S3RK> hm...
11:06 < Murch[m]> It doesn't prefer input sets with lower waste
11:06 < S3RK> what about SRD?
11:06 < S3RK> ah.. also min change
11:07 < Murch[m]> SRD only runs once and also aims to create at least minChange
11:07 < S3RK> yes, that's a bit of problem
11:07 < Murch[m]> So you could have solutions on Knapsack and SRD that each have 10+ inputs
11:07 < Murch[m]> and BnB finds a solution with a single input that ends up dropping 20k sats
11:07 < Murch[m]> Or let's say 1k sats
11:08 < Murch[m]> and we end up creating a transaction with a 750 sat output
11:09 < S3RK> doesn't mean that right now we would say "insufficient funds" for such a tx?
11:09 < S3RK> sorry
11:09 < S3RK> does it mean taht ...
11:09 < Murch[m]> So, right now, BnB would not find that solution, and it wuold use one of the Knapsack or SRD
11:09 < achow101> actually knapsack should find the solution but with change
11:10 < achow101> even if min change is not met
11:10 < achow101> srd wouldn't
11:10 < S3RK> I have to confess I don't know the details how knapsack works right now
11:10 < Murch[m]> Right, but the scenario wasn't that we didn't have enough funds, but just that the solutions that Knapsack and SRD propose have huge input sets
11:10 < Murch[m]> achow101: Do I misremember that Knapsack prefers the solution that overshoots the minchange the least?
11:11 < achow101> that sounds right
11:12 < achow101> it also prefers the solution that meets min change, but will produce a solution that does not if min change cannot be met
11:12 < Murch[m]> Right
11:13 < S3RK> It seems we should codify this scenarious in tests
11:13 < Murch[m]> I guess we could amend Knapsack to compare the 1,000 trials via the waste metric instead of minimizing the excess, and then I'd agree.
11:13 < achow101> so if bnb without limit found a solution that throws away lots to fees, knapsack should find the same thing but with change
11:13 < achow101> the excess should dominate the waste calculation
11:13 < Murch[m]> Yes
11:13 < S3RK> achow101 +1 that was my understanding as well
11:13 < Murch[m]> Correct
11:14 < Murch[m]> That's why I painted a scenario in which they find different solutions because they optimize for different metrics in their selection ;)
11:14 < Murch[m]> But yeah, if we use the waste metric internally to compare input sets on Knapsack as well, it would be pretty safe to drop the limit on BnB
11:15 < achow101> however knapsack may also find a different solution that spends more inputs as it tries to meet min change. this would still be less waste on the knapsack side since excess dominates the bnb solution's waste
11:15 < Murch[m]> But it would also kinda be pointless, because then Knapsack is very similar to BnB just for a solution that targets a +minchange larger target
11:15 < Murch[m]> Yes
11:15 < achow101> even if the knapsack fees are higher
11:16 < Murch[m]> Knapsack and BnB are very similar in approach, except that Knapsack quasirandomly explores the binary UTXO tree, while BnB does it deterministically.
11:16 < achow101> I think we need to change how we drop things to fees, and then run simulations
11:17 < achow101> and see if bnb without limit causes some scenarios where we drop ridiculous amounts to fees
11:17 < S3RK> you can test on #23367 i guess
11:17 <@gribble> https://github.com/bitcoin/bitcoin/issues/23367 | Optimize coin selection by dropping BnB upper limit by S3RK · Pull Request #23367 · bitcoin/bitcoin · GitHub
11:17 < Murch[m]> Well, in the experiment you ran for us, the numbers showed that we had more BnB solutions used than changeless transactions.
11:17 < Murch[m]> So, essentially, you've shown that already.
11:18 < S3RK> it doesn't mean we drop ridiculous amounts to fees
11:18 < S3RK> just more than we currently drop
11:18 < S3RK> which I argue could still be more economical 
11:18 < Murch[m]> Yes, agreed
11:19 < S3RK> what if we introduce a safeguard?
11:19 < S3RK> put a limit on what is "ridiculous" to drop to fees?
11:19 < Murch[m]> But it also breaks a lot of assumptions about BnB, because previously we assumed that BnB never creates change, and when we find a really large excess, the transaction we build actually does result in a change output
11:19 < achow101> time for "absurdly-high-fee" errors again :p
11:19 < Murch[m]> Isn't that equivalent to just updating our upper bound for the exact match window? ;)
11:19 < S3RK> my PR does exactly this. BnB never creates change
11:20 < achow101> yes, we do need to look at 23367 and also run simulations on it
11:20 < S3RK> hm... yes we can also extend upper bound by the "absurdly-high-fee"
11:21 < achow101> (there used to be a mempool policy reject error named absurdly-high-fee)
11:21 < achow101> I think the fee had to be 0.1 or thereabouts
11:22 < S3RK> there is still some limit. 0.1 sounds about right
11:23 < S3RK> if you can write in plain english scenarios that concerns you, I can codify them as tests
11:23 < prayank> AI
11:23 < S3RK> I take it as a compliment :) 
11:24 < achow101> one thing that concerns me is that it's probably going to hit the iteration limit very quickly
11:24 < S3RK> constexpr CAmount DEFAULT_TRANSACTION_MAXFEE{COIN / 10};
11:24 < S3RK> BnB iter limit?
11:24 < achow101> since we are removing one of the bounds that allow BnB to be called Branch and _Bound_
11:25 < S3RK> it shouldn't because there will be no branching
11:25 -!- MattCorallo[m] is now known as BlueMatt[m]
11:25 < S3RK> so it's linear to the amount of coins higher than the target
11:25 < Murch[m]> achow101: No, finding a valid solution backtracks just like overshooting the window does
11:26 < Murch[m]> Once you find a solution, it next explores the omission branch of the last included UTXO, the same as when it overshoots and stops searching the subtree because it already has too much
11:27 < achow101> oh right
11:27 < achow101> overshoot == finding a solution without limit, and both backtrack
11:30 < achow101> anything else to discuss?
11:30 < Murch[m]> It would be great if we had a test that does produce selections for which BnB without an upper bound on the exact match window breaks down
11:30 < S3RK> what do you mean by breaks down
11:32 < S3RK> I have a crazy idea. What if we create a test that iterates sending value from 1sat to 10^8sat and verifies fees
11:32 < Murch[m]> Well, something were SRD and BnB would be highly likely to produce an input set with a large count of inputs, while BnB finds one that overshoots the exact match window severely and the BnB input set scores best according to the waste metric
11:33 < Murch[m]> S3RK: I think that would be interesting, but probably the source of the issue would probably be found in the UTXO pool rather than the target amount
11:33 < Murch[m]> E.g. a wallet that has 1,000 UTXOs that have the same size, and one that is larger
11:34 < S3RK> true
11:34 < Murch[m]> And 100 UTXOs match the target plus minChange plus fees by the satoshi, but the one large input is just enough for the target without change but has a large excess
11:34 < S3RK> if we agreed that the waste metric is a good metric, than there is no problem with dropping more to fees no?
11:35 < S3RK> I'll try to create some interesting test scenarios. Including one where current coin selectio fails
11:35 < Murch[m]> Mh, I guess the fees would still be lower overall on the BnB solution in what I describe, but you'd not get the benefit of consolidating 100 UTXOs, so it feels like you paid more for less
11:36 < S3RK> the benefit of consolidating only works if the fees are lower than "long term fee"
11:36 < S3RK> if that's the case that would lower the waste
11:36 < S3RK> i.e. consolidating value is counted in waste
11:37 < S3RK> achow101 Murch what would be a good place for such tests?
11:37 < achow101> if fees are high, the 100 utxos might have a larger fee than the bnb excess
11:38 < S3RK> coinselection_test or some new/existing functional test?
11:38 < Murch[m]> yes, to both
11:38 < Murch[m]> but it still feels a bit icky, if you know what I mean
11:38 < S3RK> yes :) 
11:38 < achow101> S3RK: usually rpc_fundrawtransaction
11:38 < achow101> and coinselection_tests
11:40 < S3RK> so in conclusion 1) I work on the tests
11:40 < S3RK> achow101 could run simulations
11:40 < S3RK> and you can also take a look at the PR
11:40 < achow101> yes
11:41 < Murch[m]> Yes
11:41 < S3RK> thanks
11:42 < achow101> any other topics?
11:42 < S3RK> congrats, it looks like you'll be wallet maintainer soon :) 
11:42 < prayank> achow101: yes
11:44 < achow101> prayank: you have a topic?
11:45 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
11:45 < prayank> Not sure if this can be discussed. Wanted to understand why isnt this better approach? https://github.com/bitcoin/bitcoin/pull/22776
11:45 < prayank> RPC would respond with balance and getbalances already does that but we add a condition so parameter
11:45 < achow101> #topic add optional transaction(s) to getbalances (prayank)
11:45 < core-meetingbot> topic: add optional transaction(s) to getbalances (prayank)
11:46 < achow101> prayank: because such an RPC can be expanded to be much more than just balance fetching
11:46 < prayank> like?
11:47 < achow101> the reason I asked for simulaterawtransaction is because we can do things like seeing if a transaction has conflicts with the wallet, and if it does, what gets replaced
11:47 < prayank> hmm
11:47 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
11:48 < prayank> I liked the idea of having such params in few other RPC to simulate things
11:48 < prayank> You don't like the idea to add similar parameter in getmempool and see how mempool looks if some txs get added?
11:48 < achow101> IMO it's better to have simulating things in one spot, rather than spread in many different places
11:48 < prayank> yes its one param
11:49 < achow101> prayank: no, I think that should be its own RPC
11:49 < achow101> I don't think it makes sense to have a fetching function do simulation things
11:49 < prayank> ah okay then I guess we have different opinion. No problem. But the wallet conflicts thing makes sense.
11:51 < achow101> anything else?
11:51 < prayank> No. Thanks for sharing your opinion.
11:52 < achow101> #endmeeting
11:52 < core-meetingbot> topic: Bitcoin Core development discussion and commit log | Feel free to watch, but please take commentary and usage questions to #bitcoin | Channel logs: http://www.erisian.com.au/bitcoin-core-dev/, http://gnusha.org/bitcoin-core-dev/ | Meeting topics http://gnusha.org/bitcoin-core-dev/proposedmeetingtopics.txt / http://gnusha.org/bitcoin-core-dev/proposedwalletmeetingtopics.txt
11:52 < core-meetingbot> Meeting ended Fri Dec 17 19:52:02 2021 UTC.  
11:52 < core-meetingbot> Minutes:        https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2021/bitcoin-core-dev.2021-12-17-19.00.moin.txt
11:53 -!- vasild [~vd@user/vasild] has quit [Ping timeout: 276 seconds]
11:59 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
12:00 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:281c:2687:8a9e:e263] has quit [Remote host closed the connection]
12:00 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
12:08 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
12:12 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 268 seconds]
12:18 -!- arythmetic [~arythmeti@2605:8d80:682:9829:2966:13f4:b430:ab9] has joined #bitcoin-core-dev
12:33 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
12:35 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
12:35 < bitcoin-git> [bitcoin] laanwj pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/4ad59042b359...784a21d35466
12:35 < bitcoin-git> bitcoin/master 8494dca Dmitry Goncharov: Replace $(AT) with .SILENCE.
12:35 < bitcoin-git> bitcoin/master 784a21d W. J. van der Laan: Merge bitcoin/bitcoin#22283: build: Replace $(AT) with .SILENT
12:35 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
12:35 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
12:35 < bitcoin-git> [bitcoin] laanwj merged pull request #22283: build: Replace $(AT) with .SILENT (master...replace_AT_with_dotsilence) https://github.com/bitcoin/bitcoin/pull/22283
12:35 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
12:36 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
12:45 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
12:45 < bitcoin-git> [bitcoin] laanwj pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/784a21d35466...14ba286556fa
12:45 < bitcoin-git> bitcoin/master fa1dc9b MarcoFalke: p2p: Always serialize local timestamp for version msg
12:45 < bitcoin-git> bitcoin/master 14ba286 W. J. van der Laan: Merge bitcoin/bitcoin#23695: p2p: Always serialize local timestamp for ver...
12:45 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
12:45 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
12:45 < bitcoin-git> [bitcoin] laanwj merged pull request #23695: p2p: Always serialize local timestamp for version msg (master...2112-p2pTime) https://github.com/bitcoin/bitcoin/pull/23695
12:45 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
13:30 < prayank> Any thoughts on this? especially people who understand p2p, tor etc. https://github.com/bitcoin/bitcoin/pull/18988#issuecomment-646564853
13:31 < prayank> ryanofsky: had asked to create an issue which was never created
13:31 < prayank> I was thinking to create one
13:32 < sipa> I don't understanding anything about node-tor, or why you'd want to use a separate tor network for just bitcoin traffic. That completely defeats the purpose.
13:34 < sipa> I conceptually like having more mechanisms for connecting bitcoin nodes though, so if there were a viable network like that to use as an additional one - sure why not.
13:35 < sipa> But it feels to me like the discussion there is too far removed from anything concrete.
13:35 < prayank> hmm tbh I am not the best person to comment anything on this. I liked the idea and his follow up on mailing list. What I understand is: we do bitcoin nodes from browsers similar to one PoC by bcoin but its not safe for production. And this guy wants to make it interesting by using tor protocol for everything. I have issues with JS and WebRTC but if it can help bitcoin nodes usage I dont mind and maybe not full nodes or somethin
13:35 < prayank> g like neurino idk
13:36 < sipa> I don't understand what you're talking about.
13:37 < prayank> wait
13:37 < prayank> https://bcoin.io/browser/
13:37 < prayank> This is PoC
13:38 < prayank> He wants to do something similar but use different ways to achieve it
13:38 < prayank> and tor 'protocol' will be used not browser
13:39 < prayank> or their network
13:41 < sipa> I don't think that's at all what he's talking about. He's saying that the communication between bitcoin core and node-tor (if it were to use node-tor rather than actual tor) would not use SOCKS.
13:42 -!- masta`` [~oyster@user/masta/x-2645138] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
13:42 < sipa> But again, while I conceptually agree with making it easier to connect bitcoin nodes in more different ways with eachother, I don't understand the point of node-tor.
13:47 < prayank> sipa: what I understood based on his emails. he likes browsers, js and world around it. so webtorrents kind of things for bitcoin nodes. He is from france, he is good with his project but unable to express or get funding. IDK just wanted to share it here once so that people like you who know better would be able to see if it helps bitcoin at some point. Everything is moving to browsers tbh and this is not about altcoins. I work
13:47 < prayank> ed at microsoft when I was in college and even that had started moving from desktop applications to web apps. Core can remain same but we need a world around it.
13:49 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
13:52 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
13:53 -!- roconnor [~roconnor@coq/roconnor] has joined #bitcoin-core-dev
13:55 -!- prayank [~Prayank@103.211.191.71] has left #bitcoin-core-dev []
13:57 < jb55> so basically a way to feed network messages in and out as plaintext, turn bitcoin into a pure function?
13:58 < sipa> prayank: I conceptually agree with that, but it seems all unrelated to this discussion. He wants to build his own network that uses the tor protocol, but separate from the real one. I don't understand the reasons for that, or what there is to be gained, as directly shrinking the anonimity set for no reason as far as I can tell.
13:59 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
13:59 -!- prayank [~Prayank@103.211.191.71] has joined #bitcoin-core-dev
14:00 < roconnor> reducing the anonymity set seems pretty bad.
14:00 < prayank> sipa: Reason IIUC he doesn't like the way Tor project uses Tor protocol and its flaws etc. but wants to make a better to for different projects and bitcoin is one of them
14:01 < sipa> jb55 The P2P protocol is stateful, so it's not that easy. Just having ways of routing messages over some other links has some limited use (e.g. it's done by Blockstream satellite), but really supporting many networks in a full way is a lot harder, as you need the ability to discover connections and automatically create them etc.
14:02 < prayank> roconnor: Tor is anyways centralized directory servers so i2p is better even if less nodes
14:04 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
14:04 -!- arythmetic [~arythmeti@2605:8d80:682:9829:2966:13f4:b430:ab9] has quit [Remote host closed the connection]
14:06 < prayank> The part I am interested in this project actually was not Tor. It was browser. Because I want to see people running pruned nodes or at least some neturino type nodes running from mobile and browser.
14:06 < sipa> That's all very reasonable, but I don't think that has much to do with Bitcoin Core.
14:07 < prayank> Hmm but he commented in that PR so I thought some changes are required or that PR is related
14:10 < sipa> Yes, he needs a way to communicate with Bitcoin Core. The altnet stuff goes in the direction of providing that functionality. As I said, I conceptually agree with that. I still don't see the point of node-tor, but if there is more functionality for interacting with separate networks, and someone makes it work with node-tor, sure...
14:11 < sipa> But Bitcoin Core works fine with tor itself, and tor itself also works with browsers.
14:11 < jb55> btw satellite doesn't need to be a bitcoin fork right? couldn't it just be a block-from-space decoder + call submitblock? or is there more to it? 
14:11 < sipa> I don't know.
14:12 < sipa> I think it may rely on the node's mempool to do fast reconstruction.
14:12 < jb55> hmm
14:13 -!- prayank [~Prayank@103.211.191.71] has left #bitcoin-core-dev []
14:30 -!- ZeroMaster [~webirc@95-42-105-42.ip.btc-net.bg] has quit [Remote host closed the connection]
14:39 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
14:42 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
14:56 -!- arythmetic [~arythmeti@2605:8d80:680:d8c0:d55d:fe52:b1de:e1c3] has joined #bitcoin-core-dev
14:57 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 276 seconds]
14:59 -!- arythmetic [~arythmeti@2605:8d80:680:d8c0:d55d:fe52:b1de:e1c3] has quit [Remote host closed the connection]
15:01 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
15:02 -!- zxrqmz88 [~private@2603-7000-1302-b6f3-99b9-c40f-27d9-40cb.res6.spectrum.com] has quit [Quit: Quit]
15:10 -!- masta`` [~oyster@user/masta/x-2645138] has joined #bitcoin-core-dev
15:12 -!- masta`` [~oyster@user/masta/x-2645138] has quit [Client Quit]
15:26 -!- Guyver2_ [Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
15:27 -!- baldur [~baldur@71.183.150.231] has joined #bitcoin-core-dev
15:28 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has quit [Quit: ZzzZ]
15:29 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has quit [Ping timeout: 256 seconds]
15:29 -!- Guyver2_ is now known as Guyver2
15:34 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has quit [Quit: ZNC 1.8.1 - https://znc.in]
15:39 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has joined #bitcoin-core-dev
15:43 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has quit [Client Quit]
15:45 -!- arythmetic [~arythmeti@cpe08a7c0990817-cm08a7c0990815.cpe.net.cable.rogers.com] has joined #bitcoin-core-dev
15:46 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has joined #bitcoin-core-dev
15:54 -!- gnaf [~pi@86-91-224-60.opennet.kpn.net] has quit [Quit: Konversation terminated!]
15:54 -!- ZeroMaster [~webirc@95-42-105-42.ip.btc-net.bg] has joined #bitcoin-core-dev
15:59 -!- arythmetic [~arythmeti@cpe08a7c0990817-cm08a7c0990815.cpe.net.cable.rogers.com] has quit [Remote host closed the connection]
16:03 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:64be:1fa9:368a:6a7d] has joined #bitcoin-core-dev
16:03 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:64be:1fa9:368a:6a7d] has quit [Remote host closed the connection]
16:12 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:64be:1fa9:368a:6a7d] has joined #bitcoin-core-dev
16:19 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:64be:1fa9:368a:6a7d] has quit [Remote host closed the connection]
16:19 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:64be:1fa9:368a:6a7d] has joined #bitcoin-core-dev
16:23 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
16:25 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:64be:1fa9:368a:6a7d] has quit [Remote host closed the connection]
16:27 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
16:28 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
16:28 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:64be:1fa9:368a:6a7d] has joined #bitcoin-core-dev
16:29 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:64be:1fa9:368a:6a7d] has quit [Remote host closed the connection]
16:31 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
16:32 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
16:44 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:64be:1fa9:368a:6a7d] has joined #bitcoin-core-dev
16:48 -!- arythmetic [~arythmeti@2607:fea8:85c1:db00:64be:1fa9:368a:6a7d] has quit [Ping timeout: 240 seconds]
16:57 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
17:01 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
17:05 < jb55> b10c: btw I have a PR in the works that updates the net:inbound_message tracepoint, just a heads up
17:08 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
17:11 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
17:20 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
17:23 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 260 seconds]
17:30 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
17:30 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
17:30 < bitcoin-git> [bitcoin] jb55 opened pull request #23809: tracing: reduce instructions generated by net:inbound_message tracepoint (master...conntype-enum-usdt) https://github.com/bitcoin/bitcoin/pull/23809
17:30 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
17:33 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
17:53 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
17:56 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
18:29 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
18:32 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 276 seconds]
18:32 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
18:33 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
18:33 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/14ba286556fa...97b2fc03f666
18:33 < bitcoin-git> bitcoin/master fa6a548 MarcoFalke: ci: Disable s390x gui tests for now
18:33 < bitcoin-git> bitcoin/master 97b2fc0 fanquake: Merge bitcoin/bitcoin#23803: ci: Disable s390x gui tests for now
18:33 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
18:34 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
18:34 < bitcoin-git> [bitcoin] fanquake merged pull request #23803: ci: Disable s390x gui tests for now (master...2112-ciGUIs390x) https://github.com/bitcoin/bitcoin/pull/23803
18:34 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
18:50 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
18:53 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
18:57 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
19:22 -!- earnestly [~earnest@user/earnestly] has quit [Ping timeout: 240 seconds]
19:38 -!- mikehu44 [~quassel@206.189.41.250] has joined #bitcoin-core-dev
19:39 -!- mikehu44 [~quassel@206.189.41.250] has quit [Client Quit]
19:39 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #bitcoin-core-dev
19:41 -!- andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
19:43 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
19:46 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
19:51 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 276 seconds]
20:02 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
20:05 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has quit [Quit: ZzzZ]
20:05 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
20:18 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
20:20 -!- jtrag_ is now known as jtrag
20:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
20:41 < bitcoin-git> [bitcoin] PastaPastaPasta opened pull request #23810: refactor: destroy all C-style casts; use modern C++ casts, enforce via `-Wold-style-cast` (master...c-style-cast) https://github.com/bitcoin/bitcoin/pull/23810
20:41 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
20:49 -!- saranshsharma [~saranshsh@117.196.145.238] has joined #bitcoin-core-dev
20:50 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
20:53 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
20:55 -!- saranshsharma [~saranshsh@117.196.145.238] has quit [Remote host closed the connection]
20:55 -!- saranshsharma [~saranshsh@117.196.145.238] has joined #bitcoin-core-dev
20:58 -!- saranshsharma [~saranshsh@117.196.145.238] has quit [Remote host closed the connection]
21:01 -!- cmirror [~cmirror@4.53.92.114] has quit [Remote host closed the connection]
21:01 -!- cmirror [~cmirror@4.53.92.114] has joined #bitcoin-core-dev
21:20 -!- saranshsharma [~saranshsh@117.196.145.238] has joined #bitcoin-core-dev
21:23 -!- saranshsharma [~saranshsh@117.196.145.238] has quit [Remote host closed the connection]
21:25 -!- evbo [~bosats@2601:47:4383:560:c4f4:19bb:83c5:f3a3] has quit [Ping timeout: 240 seconds]
21:32 -!- saranshsharma [~saranshsh@117.196.145.238] has joined #bitcoin-core-dev
21:35 -!- saranshsharma [~saranshsh@117.196.145.238] has quit [Remote host closed the connection]
21:37 -!- saranshsharma [~saranshsh@117.196.145.238] has joined #bitcoin-core-dev
21:39 -!- saranshsharma [~saranshsh@117.196.145.238] has quit [Remote host closed the connection]
21:45 -!- saranshsharma [~saranshsh@117.196.145.238] has joined #bitcoin-core-dev
21:46 -!- saranshsharma [~saranshsh@117.196.145.238] has quit [Remote host closed the connection]
21:46 -!- jtrag_ is now known as jtrag
22:10 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
22:13 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
22:33 -!- nanotube [~nanotube@user/nanotube] has joined #bitcoin-core-dev
22:43 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-dev
22:46 -!- jtrag_ [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
22:48 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
22:48 < bitcoin-git> [bitcoin] fanquake pushed 5 commits to master: https://github.com/bitcoin/bitcoin/compare/97b2fc03f666...c06cda3e48e9
22:48 < bitcoin-git> bitcoin/master 86dbc4d Pieter Wuille: Squashed 'src/secp256k1/' changes from be8d9c262f..0559fc6e41
22:48 < bitcoin-git> bitcoin/master dff0596 Pieter Wuille: Update secp256k1 subtree to latest upstream master
22:48 < bitcoin-git> bitcoin/master a1f76cd Pieter Wuille: Remove --disable-openssl-tests for libsecp256k1 configure
22:48 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
22:48 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
22:48 < bitcoin-git> [bitcoin] fanquake merged pull request #23383: Update libsecp256k1 subtree to current master (master...202110_secp256k1) https://github.com/bitcoin/bitcoin/pull/23383
22:49 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
22:58 -!- jesseposner [~jesse@c-24-5-105-39.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
23:00 -!- jtrag_ [~jtrag@user/jtrag] has joined #bitcoin-core-dev
23:03 -!- jtrag [~jtrag@user/jtrag] has quit [Ping timeout: 240 seconds]
23:07 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
23:07 -!- grettke [~grettke@cpe-65-29-228-30.wi.res.rr.com] has joined #bitcoin-core-dev
23:08 -!- SpellChecker [~SpellChec@user/SpellChecker] has quit [Remote host closed the connection]
23:13 -!- sdfgsdfg [~sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
23:29 -!- jtrag_ is now known as jtrag
--- Log closed Sat Dec 18 00:00:04 2021