<r​brunner7:monero.social> Meeting in 1 hour

<r​brunner7:monero.social> Meeting time. Hello! monero-project/meta #1322

<j​effro256:monero.social> Howdy

<j​berman:monero.social> *waves*

<s​needlewoods_xmr:matrix.org> Hello

<r​brunner7:monero.social> Alright, let's start with the reports from last week

<v​tnerd:monero.social> Hi

<s​needlewoods_xmr:matrix.org> mainly worked on vtnerds review comments [here](monero-project/monero #10232#pullrequestreview-3623648856)

<s​needlewoods_xmr:matrix.org> also updated #9464 and left a comment monero-project/monero #9464#issuecomment-3724414260

<v​tnerd:monero.social> Me: no tangible updates on lws/lwsf, working on something unrelated

<s​needlewoods_xmr:matrix.org> and created a new branch for "replace wallet2 with Wallet API in `monero-wallet-rpc`" (but not much happened on it)

<r​brunner7:monero.social> That work just got financed, right? Nice.

<s​needlewoods_xmr:matrix.org> Yes, huge thanks to all supporters and donors

<j​berman:monero.social> me: we released v1.5 of the alpha stressnet (seems to be holding up reasonably well), completed a solution for the xmrig segfault (upstream PR incoming), 0xfffc merged my tx relay v2 changes into his branch (thank you!), we may be in solid shape for beta soon

<r​brunner7:monero.social> Any news about any ongoing Carrot related reviews, jeffro256 ?

<j​effro256:monero.social> Me: I'm working on implementing the scaling changes for beta stressnet

<j​effro256:monero.social> On of the firms reached out to maybe perform a partial or full audit of carrot_core, which would be awesome. I won't mention it more until they commit

<r​brunner7:monero.social> Changes designed to trigger effects earlier, as discussed recently? Different from the "real" Mainnet scaling parameters

<r​brunner7:monero.social> Anyway. I have something that may make sense to discuss in this round, maybe enough "brains" currently present to make sense

<r​brunner7:monero.social> Recently I glanced over vtnerd 's review of the expanded Wallet API, as an API, where some mention of `monero_c` got me thinking

<j​berman:monero.social> ( believe the latter, the "real" mainnet scaling params)

<r​brunner7:monero.social> If I am not mistaken, it's about this one: github.com/MrCyjaneK/monero_c

<r​brunner7:monero.social> I think it was some question about compatibility of the new Wallet API release with a "C only" wrapper, regarding callbacks?

<j​effro256:monero.social> For free btw

<r​brunner7:monero.social> Which leads me to the question: Is it our responsibility, while modifying and expanding the Wallet API, to make such C based wrappers not unnecessarily hard and complicated, or is this out of scope, so to say?

<s​needlewoods_xmr:matrix.org> the comment for reference monero-project/monero #10232#discussion_r2658678511

<r​brunner7:monero.social> Thanks, sneedlewoods, exactly that :)

<r​brunner7:monero.social> But there may be other possible pain points

<s​needlewoods_xmr:matrix.org> I don't know much about monero_c, but AFAIK it's important enough that we should not break it

<v​tnerd:monero.social> Yes the monero_c code doesn't support listeners as it's a bit messy to support. So the password change for listeners hopefully won't be required for API users or monero _c has a bunch of work (and so does dart bindings et al)

<r​brunner7:monero.social> I was mistaken, I first thought it is still based directly on wallet2 ...

<v​tnerd:monero.social> Monero_c is used by cake afaik

<j​berman:monero.social> +1 to keeping the C wrapper in mind

<j​berman:monero.social> and therefore +1 to avoid required callbacks

<v​tnerd:monero.social> Skylight definitely is too

<r​brunner7:monero.social> Ah, so you can get everything running with ignoring callbacks entirely?

<s​needlewoods_xmr:matrix.org> That's all related to `unattended` setting, iamamyth also left a comment I need to dig into monero-project/monero #10232#discussion_r2674328535

<r​brunner7:monero.social> Was wondering about that "unattended"

<v​tnerd:monero.social> Currently, yes. But needed SNeedlewoods @sneedlewoods_xmr:matrix.org: to respond about newer changes as I haven't gone through the implementation, primarily just went through the API which is still pretty lengthy

<v​tnerd:monero.social> Currently yes -> listeners are not required

<s​needlewoods_xmr:matrix.org> AFAICT they're still not required if you keep `unattended = true` as it was the default before, but have to double check

<v​tnerd:monero.social> Ah ok, will have to go back through and verify all of this then

<r​brunner7:monero.social> By the way, is the author "MrCyjaneK" active around here, in the Matrix rooms and/or on IRC? Maybe it would be good for them to have a look what we are up to here ...

<r​brunner7:monero.social> Easier to correct / adjust things now than later

<v​tnerd:monero.social> I would tag them on GitHub, they've commented on something I've done before

<r​brunner7:monero.social> Maybe even ready to help reviewing, who knows

<r​brunner7:monero.social> So things are probably safe. Good to hear.

<r​brunner7:monero.social> Anything else to discuss today?

<s​needlewoods_xmr:matrix.org> Not from me, will post updates on the PRs or in here during the week when I figured things out+

<r​brunner7:monero.social> Well then. Thanks everybody for attending, read you again next week!

<j​berman:monero.social> thanks!

<s​needlewoods_xmr:matrix.org> thanks everyone, see ya