11:38:09 <br-m> <vikrants> Check out NanoGPT.  It’s in cake already > <@c99e:matrix.org> Oh I probably should've mention that the service does not require an account, and takes no logs. Just mint key -> pay -> use
14:43:02 <sech1> Reminder, P2Pool v4.16 critical security release in ~15 minutes https://www.reddit.com/r/Monero/comments/1u1tt1p/psa_critical_p2pool_security_update/
14:44:01 <br-m> <longtermwhale:matrix.org> do we have time to exploit it @sech1 
14:44:42 <sech1> If miners don't update and you figure it out... yes
14:45:05 <br-m> <longtermwhale:matrix.org> how much to gain?    
14:46:05 <sech1> ~0.5 XMR every 30-40 minutes on p2pool-main
14:46:41 <sech1> Which is why it's important to update
14:46:59 <br-m> <longtermwhale:matrix.org> good find 👍️
15:01:40 <br-m> <plowsof:matrix.org> and we're off https://github.com/SChernykh/p2pool/releases
15:05:36 <DataHoarder> pushed fixes plus others onto mine as well
15:06:16 <br-m> <ofrnxmr:xmr.mx> Community meeting in 54mins: https://github.com/monero-project/meta/issues/1404
15:59:04 <nioc> https://ccs.getmonero.org/funding-required/
16:00:09 <ofrnxmr> Meeting time: https://github.com/monero-project/meta/issues/1404
16:02:43 <br-m> <jpk68:matrix.org> Hello
16:02:45 <br-m> <redsh4de:matrix.org> Hello
16:02:46 <msvb-lab> Hello.
16:03:18 <br-m> <plowsof:matrix.org> hi
16:06:11 <ofrnxmr> Welcome
16:06:28 <ofrnxmr> 3. Community highlights
16:06:43 <br-m> <moneromavrick:matrix.org> Yo
16:07:23 <ofrnxmr> Monerokon was last weekend. I heard it went well
16:07:57 <ofrnxmr> This weekend we have a critical p2pool update https://github.com/SChernykh/p2pool/releases
16:08:57 <DataHoarder> I keep monitoring updated and non-updated nodes to find any incidence of exploitation. 
16:10:58 <br-m> <hbs:matrix.org> (late) hello
16:11:44 <ofrnxmr> An explot was found in BasicSwapDEX (unrelated to monero swaps) which also had a critical release: https://github.com/basicswap/basicswap/releases/tag/v0.16.4
16:12:18 <ofrnxmr> Any other business / community highlights?
16:13:19 <ofrnxmr> Plugging the newsletters: [Revuo Monero](https://revuo-xmr.com/) &  [This week in Monero TWIM](https://cyphergoat.com/this-week-in-monero)
16:13:55 <ofrnxmr> If nothing else, lets move on to the CCS proposals
16:13:58 <ofrnxmr> 4. CCS proposals
16:14:14 <br-m> <4rkal> CypherGoat’s MoneroKon scavenger hunt wrapped up successfully in Warsaw, with $800 in prizes distributed. Hunt details: https://cyphergoat.com/monerokon2026 > <ofrnxmr> Any other business / community highlights?
16:14:33 <ofrnxmr> Nice
16:15:54 <ofrnxmr> a. Koe - [Research and Development, hardfork](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/681)
16:16:09 <br-m> <jpk68:matrix.org> +1
16:16:14 <ofrnxmr> Koe came back a while ago and completed his prior ccs
16:16:40 <ofrnxmr> New one continues work on fcmp/carrot 
16:16:51 <br-m> <redsh4de:matrix.org> +1
16:16:54 <tobtoht> +1
16:17:30 <br-m> <ofrnxmr:xmr.mx> +1
16:20:10 <ofrnxmr> b. Dennis Trautwein - [ProbeLab P2P Network Metrics Proposal](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/667)
16:20:45 <plowsof> i left a comment regarding rates https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/667#note_36602
16:22:05 <ofrnxmr> Aside from that, i believe MRL has given their blessing on the deliverables
16:22:41 <ofrnxmr> c. Marko Pohlo - [Cuprate Consensus-Rule Differential Fuzzing](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/676)
16:24:23 <br-m> <jpk68:matrix.org> This proposal seems pretty interesting, however Cuprate devs have mentioned the timing isn't very opportune
16:24:25 <br-m> <ofrnxmr:xmr.mx> i tend to agree with boogs comment, along the lines of "its too early for this"
16:25:05 <br-m> <jpk68:matrix.org> IMO something like this would be really nice/useful eventually, for consensus and client diversity reasons
16:25:06 <br-m> <ofrnxmr:xmr.mx> imo should revisit once cuprate is feature complete etc
16:25:29 <plowsof> in the meantime, a 2nd round for fuzzing monero core / fcmp++ remains unfunded here https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/667#note_36602 
16:25:56 <plowsof> clipboard hijacked sorry
16:26:04 <plowsof> https://donate.magicgrants.org/monero/projects/fuzzing-monero-2
16:26:51 <br-m> <jpk68:matrix.org> 100% in favour of this one ^
16:26:57 <plowsof> note  the price, 3 months for 3 devs, 50k, probelabs 1.5 person months 40k 
16:27:13 <plowsof> unrelated but interesting none the less
16:27:20 <br-m> <ofrnxmr:xmr.mx> 1/3 of the devs is the top contributrow to oss-fuzz as well
16:27:55 <br-m> <ofrnxmr:xmr.mx> er. or "a" top, not "the"
16:28:34 <br-m> <ofrnxmr:xmr.mx> anyway, my vote is close &  revisit later
16:30:33 <br-m> <ofrnxmr:xmr.mx> anyone else? logs cant see emojis
16:32:23 <ofrnxmr> d. r4v3r23 - [ANONERO Continued development](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/671)
16:33:08 <br-m> <ofrnxmr:xmr.mx> I intended to comment on this proposal directly, but never got around to it. i was in favor of the 1st and 2nd revisions (which were 12 and 6 months, respectively)
16:33:56 <br-m> <ofrnxmr:xmr.mx> My concern is that the dev is not the proposer, and is a dev-for-hire, and limiting the timeframe leaves question about what happens after the 3 months?
16:35:53 <br-m> <ofrnxmr:xmr.mx> for the initial anonero, and the 1.0 release, they both had different devs, and this is a third. the rate difference from 1.0 to this proposal is essentially a 4x increase (if we assume that this only lasts 3 months) -- and even a potential 4x increase from the initial version of the proposal
16:37:46 <br-m> <ofrnxmr:xmr.mx> all things being equal (the same amount of hours on each revision, ie 40hrs/week for 3 months, 20hrs for 6 months, and 10hrs for 12 months) the dollar rate remains the same. but my main concern is "where will the dev be in 4-12 months?"
16:39:24 <br-m> <ofrnxmr:xmr.mx> i prefer revision 1 and 2 for that reason. id be more comfortable knowing  that the project still has a dev to solve issues 10 months from now
16:39:34 <br-m> <jpk68:matrix.org> I have the same concern, but I am tempted to be somewhat in support of this proposal overall. More development for Android wallets is good for the ecosystem
16:40:20 <br-m> <jpk68:matrix.org> To be honest, I am pretty skeptical that this dev will stay for long, based on what's happened previously
16:40:21 <br-m> <ofrnxmr:xmr.mx> @jpk68:matrix.org: to echo some of plowsofs initial feedback -- the wallet has undergone a major rewrite already, and is a different dev each time
16:41:06 <br-m> <ofrnxmr:xmr.mx> so paying the dev for 3 months doesnt seem ideal. yes, wallet dev is good for ecosystem. but not having a dev is not
16:42:22 <br-m> <ofrnxmr:xmr.mx> acx, for example, maintains monfluo for ~40xmr per year
16:42:45 <br-m> <ofrnxmr:xmr.mx> anoneros rev. 1  proposal was 66xmr for the year
16:43:15 <br-m> <ofrnxmr:xmr.mx> acx is available all year. anonero's dev is free to leave in 3 months
16:43:29 <br-m> <ofrnxmr:xmr.mx> (after collecting a years pay)
16:44:04 <br-m> <ofrnxmr:xmr.mx> anyway, thats the feedback that i planned to leave on the merge request. i'm in favor if its 6 or 12 months, but not 3 months
16:45:02 <plowsof> double the asking amount then? or are we literally forcing a dev to work less / week?
16:46:16 <plowsof> where will they be in 13 months 
16:46:30 <br-m> <ofrnxmr:xmr.mx> the initial revision was 66xmr per year
16:46:50 <br-m> <ofrnxmr:xmr.mx> then was 66 per 6 months, now is 109 for 3 months
16:47:13 <plowsof> priced in fiat and the $  value moved. iirc it was 69 xmr
16:47:19 <plowsof> +10% buffer
16:47:41 <br-m> <ofrnxmr:xmr.mx> yeah, i know fiat adjusted the number, but it still changed from 69 to 88 w/o fiat jump
16:47:47 <br-m> <ofrnxmr:xmr.mx> dev rates went from 45 to 60/hr
16:48:00 <plowsof> 69.9*
16:48:12 <br-m> <ofrnxmr:xmr.mx> :P mr specific
16:48:54 <br-m> <ofrnxmr:xmr.mx> if other have no issue, then thats fine. just leaving my feedback that id prefer the proposal undo the latest change
16:49:02 <plowsof> whats a +15$ an hour raise between friends
16:50:16 <br-m> <ofrnxmr:xmr.mx> it was said that the rate changed because the dev is working full time now and needs 33% more for that. 
16:50:37 <br-m> <ofrnxmr:xmr.mx> id prefer part time w/ longer availability, is my position
16:51:09 <br-m> <ofrnxmr:xmr.mx> im not counting the dollars, my main concern is that the wallet will be unmaintained in 3.1 months
16:52:25 <br-m> <ofrnxmr:xmr.mx> from the looks of the repo, after 1.0 release 9 months ago, there have only been 8 commits http://git.anonero5wmhraxqsvzq2ncgptq6gq45qoto6fnkfwughfl4gbt44swad.onion/ANONERO/ANONERO/compare/v1.0.0...v1.0.1
16:53:12 <plowsof> Monerujo feeling nervous rn
16:53:17 <br-m> <ofrnxmr:xmr.mx> (so the other dev worked out their contract and left, it seems). == i prefer longer part-time contract vs shorter full-time
16:53:41 <br-m> <ofrnxmr:xmr.mx> anyway, enough of my rambling
16:54:05 <br-m> <ofrnxmr:xmr.mx> thats the final CCS on the agenda today.
16:55:07 <br-m> <ofrnxmr:xmr.mx> again, big reminder to update your p2pool https://github.com/SChernykh/p2pool/releases, and to share with everybody cc @  @moneromavrick:matrix.org
16:56:18 <plowsof> the dev is sending patches to raver @ 40 hours a week (can you imagine?) - they should probably make pull requests instead. on that note , the codeberg for bridge that jpk68 was using, should be switched over to becoming a github app + webhooks to hopefully avoid being nuked 
16:57:12 <br-m> <ofrnxmr:xmr.mx> nuking seems related to sending PRs to p2pool
16:57:19 <plowsof> @tomdooley brainchainz !
16:58:37 <plowsof> lol yes, avoiding p2pool also
17:01:06 <br-m> <ofrnxmr:xmr.mx> Next meeting Sat June 27, 2026, 1600 UTC
17:01:14 <br-m> <ofrnxmr:xmr.mx> Thanks everyone for attending
17:01:16 <plowsof> thanks for hosting 👍
17:01:37 <br-m> <ofrnxmr:xmr.mx> please leave feedback on the open proposals, either thumbs up/down or comment
17:01:42 <br-m> <michael> Good meeting, dankon.
18:02:57 <br-m> <r4v3r23> you know how easy it is to apply patches? > <plowsof> the dev is sending patches to raver @ 40 hours a week (can you imagine?) - they should probably make pull requests instead. on that note , the codeberg for bridge that jpk68 was using, should be switched over to becoming a github app + webhooks to hopefully avoid being nuked 
18:03:43 <br-m> <r4v3r23> you guys are confusing being maintained/supported with the work thats being done > <@ofrnxmr:xmr.mx> im not counting the dollars, my main concern is that the wallet will be unmaintained in 3.1 months
18:04:00 <br-m> <r4v3r23> the wallet has always been maintained and supported from the very first release
18:04:14 <plowsof> would you not prefer him to make pull requests?
18:04:45 <br-m> <r4v3r23> plowsof: its a non issue. he could easily do that
18:05:05 <br-m> <r4v3r23> same as applying patches. the only difference is what account it would be under
18:07:52 <br-m> <r4v3r23> > <@ofrnxmr:xmr.mx> My concern is that the dev is not the proposer, and is a dev-for-hire, and limiting the timeframe leaves question about what happens after the 3 months?
18:07:52 <br-m> <r4v3r23> ill say this: ive never been more confident in the future of the project than now. this dev is reliable, professional, iterates fast and is always available. that said, this round of work is essentially to bring ANONERO to "feature complete/stable" status - this isnt a project that needs constant CCSs for low level maintence/dev work
18:08:31 <br-m> <r4v3r23> there is 0 risk of the wallet being unmaintained after 3 months, just like it was never unmaintained at any point in the wallets history
18:09:29 <br-m> <r4v3r23> since 3 months was brought up at first meeting, thats now the proposal, and literally the only thing holding up the work is the funding. all the features are designed and ready for implementation
18:11:06 <br-m> <r4v3r23> ANONERO will be maintained and supported indefinitely. this CCS is to finally bring advanced stealth features and give it the fresh UI it deserves
18:12:26 <plowsof> any design examples of the new ui? 
18:12:31 <br-m> <r4v3r23> "Any unclaimed milestones after 3 months can have funds allocated to FCMP++ work." - this alone should speak to how confident i am in this proposal
18:14:13 <plowsof> "CCS will expire one year from date of first payout and funds can be send to the General Fund." you are now 4x more confident, nice to see, promising 
18:14:32 <br-m> <r4v3r23> plowsof: correct
18:16:49 <br-m> <r4v3r23> this is an independent project that respect user privacy and has innovated more than any other mobile wallet. benefit of the doubt wouldnt hurt
18:16:52 <plowsof> do any other wallets in the ecosystem function on patches? it seems really unique, i would definitely consider moving to pull requests 
18:17:20 <br-m> <r4v3r23> plowsof: the patches was just so that the code is "owned" by the ANONERO user/project
18:17:43 <br-m> <r4v3r23> literally instead of dev doing git push, its git patch and send
18:17:49 <br-m> <r4v3r23> its the exact same thing
18:18:35 <br-m> <r4v3r23> if its a deal breaker, than dev can just push commits...
18:42:05 <br-m> <r4v3r23> the 3 month proposal is the best way to guarantee the delivery timing, and ensure future support. the "continued support" part of the CCS isnt limited to 3 months (it was there in the original proposal), the time line is strictly for the feature milestones
18:46:00 <br-m> <r4v3r23> a wallet needs constant commits to be maintained....? > <@ofrnxmr:xmr.mx> from the looks of the repo, after 1.0 release 9 months ago, there have only been 8 commits http://git.anonero5wmhraxqsvzq2ncgptq6gq45qoto6fnkfwughfl4gbt44swad.onion/ANONERO/ANONERO/compare/v1.0.0...v1.0.1
18:46:25 <br-m> <r4v3r23> you realize the entire point of the 1.0 rewrite is to be stable and NOT need so many updates?
18:47:27 <br-m> <r4v3r23> feathers last release was in April 2025 - are you gonna accuse feather also of being unmaintained?
18:47:51 <br-m> <r4v3r23> or would you rather ANONERO create busy work to justify constant 3 month proposals?
18:48:19 <br-m> <r4v3r23> the goal is a solid, stable, feature complete wallet that needs minimum maintanence
18:51:04 <br-m> <r4v3r23> btw, ANONERO (with new dev) was the first wallet to update to v0.18.5
18:51:30 <br-m> <r4v3r23> so unless there are any real objections, lets get this to funding
20:16:11 <br-m> <pw:xmr.mx> 18th April > <@r4v3r23> feathers last release was in April 2025 - are you gonna accuse feather also of being unmaintained?
20:16:11 <br-m> <pw:xmr.mx> rottenwheel - Damn, 2.8.1 goes back to April 14, 2025.
20:17:11 <br-m> <tobtoht> 2.9.0 soon (tm)
20:17:31 <br-m> <pw:xmr.mx> tobtoht - I will cut a Feather release after v0.18.5.0 is out.
20:17:31 <br-m> <pw:xmr.mx> recent monero point releases have been daemon fixes for the most part
20:17:50 <br-m> <pw:xmr.mx> that a why no feather release updates
20:20:14 <br-m> <pw:xmr.mx> @r4v3r23:monero.social I will give ANONERO a try and follow progress.
20:20:14 <br-m> <pw:xmr.mx> best of luck with it
21:12:38 <br-m> <r4v3r23> @tobtoht: my point wasnt a dig at feather, it was a dig that a project needs constant updates to be "maintained"
21:12:55 <br-m> <tobtoht> I got that
21:13:08 <br-m> <r4v3r23> just making it clear :)
21:15:10 <br-m> <r4v3r23> @pw:xmr.mx: feedback is always welcome. i like to see ANONERO as feather's mobile companion
21:16:56 <br-m> <4rkal> CypherGoat merch store is live! Selling conference edition t-shirts, caps and more https://merch.cyphergoat.com. You can pay by crypto by purchasing out giftcards
21:54:11 <br-m> <jpk68:matrix.org> Posted on Nostr, for all the 3 people that will see it :') > <@ofrnxmr:xmr.mx> again, big reminder to update your p2pool https://github.com/SChernykh/p2pool/releases, and to share with everybody cc @  @moneromavrick:matrix.org
22:05:46 <br-m> <pw:xmr.mx> @4rkal: Monerotopia T-shirt is cool.
22:05:46 <br-m> <pw:xmr.mx> not quite sure about the cap though haha