06:08:50 Hey everyone, I’d like to gather your opinions on the content-creation-plans at https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/655#content-creation-plans in advance. 06:08:50 There are two options: 06:08:50 1. Automated Generation via AIGC Tools[... more lines follow, see https://mrelay.p2pool.observer/e/7q2h7fEKMWJOX3Rm ] 06:10:55 Also, I hope this proposal is not just a temporary replacement for Observer, but can also serve as a reference for 3RA to upgrade Observer. After all, he mentioned that he plans to:I will likely implement some changes to the project: migrate away from Jekyll due to its excessively long local build times, redesign the website, and potentially expand the overall journalistic approach. 14:36:14 25 minutes till the meeting, right? 14:36:44 4 pm UTC 14:36:51 nope 1h24 14:51:47 i have one server with 8 e7-8880 v4 and another one with 8 e7-8880 v3 .i have 480 gb ram .which is the best way to mine?better to insert all ram in one server and to use only one server for mining or to use both servers inserting half of memory in each one. 14:56:17 trevor: Of course, mine with both servers at the same time. 14:56:17 Theoretically, as long as your RAM is larger than 2GB, you can mine with high efficiency. 14:56:17 and this problem you could go to #xmrmine:matrix.org 14:57:12 thank you. 14:57:13 #monero-mining (theyre on irc) 15:40:11 nope 20min! 15:44:59 Lol msg didnt send 15:45:32 https://mrelay.p2pool.observer/m/xmr.mx/dvHvtvfNfobxHtpiVuVahWKP.png (share_8575133963605237553.png) 15:46:55 Meeting in 13mins 15:50:02 selsta part-time monero development (3 months) (20) is now fully funded! https://ccs.getmonero.org/proposals/selsta-20p.html @luigi1111 15:50:17 tyy 15:59:16 Meeting time. 15:59:16 Agenda: https://github.com/monero-project/meta/issues/1356 15:59:16 We have 11 proposals to introduce & discuss within the hour. Aiming to budget average 5 mins per item.[... more lines follow, see https://mrelay.p2pool.observer/e/kNmT_vEKRTBzX3g4 ] 16:00:23 Hello 16:00:27 hi 16:00:45 hi 16:00:52 We have 11 proposals to introduce & discuss within the hour. Aiming to budget average 5 mins per item. 16:00:52 Greetings! 16:01:01 Hello 16:01:07 (Reposting from irc since the message was truncated) 16:01:58 g'day 16:02:00 Hi 16:02:28 Any community highlights anyone would like to share over the past month or so? 16:03:00 hey 16:03:40 Well, the new beta version of getmonero.org is definitely a highlight. 16:04:13 Yea. Its been migrated to github.com/monero-project/monero-site on the "beta" branch 16:04:41 hello 16:04:42 Monero core/gui release(s) , be sure to update https://www.getmonero.org/downloads/ 16:04:50 Dont update :O 16:04:53 Hello 16:04:54 can't see meeting messages from this account, if others have the same problem join on irc 16:04:55 hello 16:04:57 :P. There is a bug 16:04:57 Hi there 16:05:09 sneedlewoods_xmr: Same here 16:05:29 Dont update 16:05:32 ofrnxmr: I think I could try to contribute. The beta design is really good, but it’s missing some animations, isn’t it? 16:05:36 Stick with v0.18.4.5 for now. Wait for v0.18.4.8 16:06:15 @pyxmr2025:mozilla.org: Sorry @pyxmr2025:mozilla.org I cover that already 16:06:38 @syntheticbird: emm,I see.ok 16:06:42 News: [Monero Observer](https://www.monero.observer/) - [Revuo Monero](https://revuo-xmr.com/) - [This week in Monero TWIM](https://cyphergoat.com/this-week-in-monero) -- observer is still on break 16:07:28 Forget about Monero Observer. Can anyone of you get in touch with 3RA? I don’t have XMPP anyway. 16:07:37 There is a proposal to discuss today from jackie wrt a news aggregator 16:07:55 yeah 16:08:14 If nothing else, lets get into the proposals? 16:08:22 monero moon 89 was the most recent newsletter, or? (mar 11) https://www.themoneromoon.com/p/the-monero-moon-issue-89 16:09:57 parasew_II: yeah 16:10:17 ok proposal time 16:10:33 i. VTNerd - [2026 Q2 Proposal](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/654) -- core monero work + continued lws development. Plenty of lws updates and is nearing a stable release 16:10:43 merge 16:10:44 no doubt 16:10:51 +1 16:10:59 +1 16:11:11 I have to admit its frustrating to see so many improvements from vtnerd not merge 16:11:29 +1 16:11:29 vtnerd has been doing an absolutely fantastic job all along. 16:11:31 but hey he is engaged on it 16:11:36 +1 16:12:22 yeah, a problem is a lack of thorough reviews 16:12:48 But after 2years the socks5 pr was finally merged into master 16:13:13 ofrnxmr: 2years 16:13:45 e. DangerousFreedom - [Integrate FCMP++ into monero-inflation-checker](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/645) 16:13:50 ofrnxmr: We might run into the same issue once Weblate goes live. 16:14:32 some might remember dangerousfreedom from creating the inflation checker website. He has funds remaining from his prior ccs that will be used to fund this proposal. As such, i agree with plowsof that we dont need to merge right away 16:15:05 Was brought up in NWLB meeting(s), rbrunner has approved the recent changes 16:15:35 +1 16:15:47 +1 16:15:54 its a merge imo, but is essentially a retroactive proposal, so can be merged anytime w/o issue since the funds are already earmarked 16:16:23 !nick jpk68 16:16:31 oops 16:16:52 +1 16:17:19 k. plowsof - [CCS Coordinator + QATS](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/656) 16:17:52 merge+1 16:18:45 There have been some changes, but plowsof has been doing a great job. Besides, he’s familiar with the processes and relationships between CCS and core, even as a collaborator. 16:18:49 ngl i had trouble to follow the changes but he had explain enough so that's a merge +1 16:19:55 You might remember plowsof from being everywhere, all the time. Keeping an eye on everything that happens behind the scenes. Helping with releases and all that good stuff. Changes to recent ccs is a shift of tone / focus to ack his other contributions instead if just "ccs coordinator" 16:20:57 ofrnxmr: yeah.I swear he’s online 24/7. My classmates and I were even joking about whether he ever sleeps, lol. 16:21:14 its a +1 from me with adding ccs coordinator back to the list. It would be hard to have ccs function without his time spent helping proposers and dealing with luigi 16:22:00 @ofrnxmr: Someone else will take over eventually, but the process still needs Plowsof to mentor and guide them through it. 16:22:55 I dont think core is going to listen to many people or allow write access to the gitlab 16:23:45 Trust, the ever long-standing issue in human history. 16:23:58 ofrnxmr: Doesn’t the C in CCS stand for community? 16:24:19 Core runs the infra, the wallets, and merges all proposals. 16:24:25 @pyxmr2025:mozilla.org: Don't forget the other C 16:24:28 CC 16:24:32 Community Crowdfunding 16:24:34 The Crowdfunding is the community part 16:24:39 Community crowsfunds. We dont run the platform 16:24:44 Exactly what synthetic said 16:24:55 g. CJ - [Grease Payment Channels -- production implementation and SDK](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/651) 16:25:35 For sure remove the asci at the top 16:26:07 is this a retroactive proposal ? 16:26:11 ofrnxmr: Thus is a very complicated proposal. @hbs:matrix.org had some comments on it 16:26:15 @syntheticbird: No 16:26:16 > Overall, the project is around 60% of the way towards a production-ready beta. Total development time for a production-ready beta is 16:26:17 > estimated at 3,500 hours, of which around 1,975 hours have been completed 16:26:43 I'm here, if you have any specific quesiotns 16:26:47 yeah my bad there is the total below 16:27:20 The Grease proposal is unsatisfactory in my view since it only produces a system with a centralized entity as the Key Escrow Service. 16:28:08 Well, this proposal does. The goal is 100% to move to a decentralised KES. But better to take smaller steps than try and do everything at once 16:28:10 But its also not a complete proposal. Mentions a follow up proposal and, again, is quite complicated. I think this one should also require approval from MRL 16:28:21 But we’ve already paid the price in time. 16:28:53 We havent funded anything on grease. It was funded by the Power Up Privacy group 16:28:58 Could benefit from MRL(?) commenting on the MoNet paper - its been linked there previously im half certain, not sure what they think 16:29:19 CjS77: Is AI being used to write some of the code for this project? CodeRabbit is listed as a contributor on GitHub 16:30:44 AI can impact project maintainability, but I think it’s fine as long as we control how much we use it. 16:31:04 my only concern is that this should be disclosed to donors explicitly 16:31:06 CodeRabbit does reviews in Github. 16:31:06 I use AI for boilerplate code. But core stuff (crypto /signature schemes / ZK code) is still faster to do it at "human speed". In any case, I never commit any code written by an agent without reviewing it, like I would with any contributor submitting code to an OSS project 16:31:38 note: I think there may be some crossover with Baltsar's proposal wrt ai agents 16:31:49 "Agentic AI payments - This emerging use-case may become the most important. As AI agents become more capable and autonomous, they 16:31:49 will need to make a huge number of on-demand payments for various services, such as API calls, data access, compute resources, and 16:31:49 more. Grease channels can be thought of as disposable wallets for these agents. Users can fund a channel with a predetermined budget 16:31:49 for a specific purpose, and the agent can only use it for that purpose and nothing else until the budget runs out. This provides a 16:31:49 secure and private way for agents to make payments without their owners risking overspending or having to share seed phrases." 16:32:00 My concern is mostly with crypto implementations, which this project involves 16:32:03 Please precise it in your proposal because if you don't say it people are gonna lose their mind thinking you are vibecoding it entirely 16:32:09 Using agents for this seems to be a recipe for disaster 16:32:12 Yeah, that I do myself 16:32:52 But I find it handy to have agents review the code. They do find little issues. 16:33:12 i dont see any issue with running the code through AI for reviews 16:33:22 Me neither :) 16:33:29 One issue with external projects to core, which itself struggles for reviewers 16:33:29 CjS77: I agree with that. 16:33:59 Defer to MRL and revisit? 16:34:04 As long as the maintainer is competent enough to filter false positives that's fine 16:34:18 ofrnxmr: ofrnxmr: definitely 16:34:43 +1 16:34:50 h. Baltsar - [monero-mcp Maintenance, Guides, and Demos (2026 Q2)](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/652) 16:34:52 And confirm sentiment on funding layer2 as the time/funding is significant 16:35:20 CjS77 do you have any comments on this proposal? 16:35:40 On Grease, or monero-mcp Maintenance? 16:35:55 Baltsar is pasting output of gpt in his replies to me , emdash and all. 16:36:08 Monero-mcp 16:36:15 Ah, nope. Have not read it 16:36:58 Can you take a peek. Its seems mostly AI generated (even the proposal), but seems there js some overlap with your proposal 16:37:08 A quick scan suggests it might be complementary rather than competing with Grease 16:37:51 I have nothing against, I see a use case, pricing is high tho 16:37:54 What do you mean by competing? It's not even for the same sort of thing 16:38:32 A benefit of payments channels is that they're basically like a covenant. No prompt injection or anything similar can redirect payments -- a payment channel can *only* route payments to its intended recipient, which feels to me like a huge plus for AI agents 16:38:37 no offense but $135/hr for a project that will be vibecoded is unreasonable. 16:38:40 jpk, there is a part of grease proposal that mentions ai payments 16:38:49 Ah, my bad 16:38:50 ^ > "Agentic AI payments - This emerging use-case may become the most important. As AI agents become more capable and autonomous, they 16:39:04 yeah i agree with jpk68 here 16:39:10 jpk68 - like I said -- I just had a quick scan 16:39:13 grease proposal mentions AI as a use case 16:39:19 this proposal is talking about MCP 16:40:09 Yeah. Im leaning nack on mcp, but can wait for more comments on it 16:40:20 No offense, but I really fail to see the use case for this 16:40:36 same stance as ofrn 16:40:46 wait for me a moment(about my ccs) 16:40:55 jpk68: LLM controlled wallet 16:41:03 Yes :) 16:41:05 Ok, will save jackie for last 16:41:11 2 other sinilar mcp ish repos exist. Also sech1 described a way you'd get rekt using an older version of this in a reddit comment lol 16:41:16 so you can imagine gadget assistant sending payments on your behalf 16:41:30 moving on 16:41:35 c. Strawberry ChocolateFudge - [Homomorphic Dex infrastructure to increase privacy against cross-domain metadata-correlation attacks](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/642) 16:42:14 ofrnxmr: I think this needs comments from woodser, binarybaron etc. I dont think it makes sense 16:42:31 I have not understood a single fucking paragraph of this proposal 16:42:41 might be my tiktok attention span but i couldnt understand what problem this solves and where it could be applied 16:42:47 It sounds like an AI generated idea 16:43:03 A solution in search of a problem 16:43:07 That's mine. It's a proposal to write a DEX infra with an order book first approach. 16:43:53 Basicswap is an orderbook-first approach to an atomic swap dex 16:44:16 back now 16:44:20 you could argue that haveno also is 16:44:26 It's a privacy focused orderbook system that mitigates chainalysis on Dex that happens via public order tracking 16:45:05 A dark pool basically 16:45:08 Would it not be possible to perform the improvements on haveno itself? Why something new rather than improving/maintaining an existing dex? 16:45:15 hopefully we can get comments from ecosystem participants such as haveno, eigenwallet, basicswap, and serai 16:45:17 You are stretching on the benefits but fail to explain simply what your solution is and how it solves the problem you are mentioning 16:45:29 imo 16:46:23 @ofrnxmr: Since it appears that is supposed to "add privacy"(?) to existing dexs? 16:46:29 cc monerobull 16:46:54 what 16:47:04 Hello 16:47:14 ofrnxmr: this is bullshit 16:47:15 close 16:47:24 It's in the spec on how it works. The proposal is to reuse existing developed atomic swap with a privacy focused order book. 16:47:47 So why not work with eigenwallet? 16:47:57 i've heard enough 16:47:59 Have you spoken to them? 16:48:02 -1 16:48:04 So instead of adding the improvement, you just fork/rewrite an existing DEX and add a feature? 16:48:23 *adding to Haveno, etc. 16:48:25 Moving on (running out of time) 16:48:34 f. jpk68 - [I2P SAMv3 support](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/650) 16:48:51 Happy to answer any questions about this one :) 16:49:10 @syntheticbird: -1 16:49:30 jpk68: How does it feel to be the third person to attempt at integrating I2P into monerod 16:49:53 I feel like it's worth a shot :) 16:50:18 Plus it's something that just needs to get done 16:50:19 Sorry jpk, i meant to comment on the proposal a while ago. 16:50:19 i think i have to nack the proposal for just 1 reason. There have been like 5 attempts to add i2p to monero gui, and all of them have been ai slop garbage. Your proposal is much less than the bounty available and includes the bounty deliverable. Why not just do the work and claim the bounty? 16:50:34 One point that inerest me is : 16:50:34 > Contributing to and improving upon existing documentation for anonymity networks in Monero 16:50:41 where is this documentation going to be ? 16:51:12 I'm proposing to work with the I2P devs on migration/setup guides. 16:51:29 The current I2P setup docs (in monero-docs) are unclear and horrendously outdated 16:51:34 I just think native I2P support would be more convenient for new users. 16:51:49 Also, you cant replace the socks support. Monero has a policy of not breaking things, so sam would have to be in addition to / an an option to socks 16:52:07 with the I2P devs? what? 16:52:23 jpk68: They arent outdated at all. 16:52:40 (i wrote them) 16:52:41 > Pass code review requirements 16:52:41 can't be a milestone objective 16:52:44 ofrnxmr: Yes, the plan is to add it, keep SOCKS5 in for now (backwards compatibility), and later deprecate it after migration is given some time 16:52:44 Recently 16:52:47 Also, just to add, this proposal has received endorsement from the I2P team, vtnerd, and StormyCloud (a nonprofit that sponsors I2P) 16:53:12 syntheticbird: Yes 16:53:21 vtnerd is part of the i2p team? 16:53:28 jpk68: ? 16:53:34 No, I mean him as well as the I2P devs 16:53:38 It has 0 upvoted - vtnerd hasnt endorsed it 16:53:45 He said "I am in support" 16:53:49 Let me find the chatlog 16:54:01 I saw it. He's in support of i2p sam 16:54:13 Not necessarily of the proposal 16:54:15 https://nitter.net/MoneroResearchL/status/2034456294799585357#m 16:54:23 My bad, was unclear 16:54:27 ^ > <@ofrnxmr> Sorry jpk, i meant to comment on the proposal a while ago. 16:54:33 They can thumb the proposal up to confirm or not 16:54:52 Im still of the party of "claim the 100+xmr bounty" 16:54:54 Yes, I asked them to but I think they forgot 16:54:59 https://nitter.net/i2p/status/2034416908334743810#m 16:55:14 The proposal is fine, but code (especially code like this) shouldn’t be handed over to AI. 16:55:23 Yes, of course, I don't use AI for anything 16:55:53 jpk68: Joke:Maybe they were just humoring you. 16:55:58 3.5 more proposals to go 16:56:00 Use case is clear. Some objectives under milestone is bugging me out. Endorsement needs to be ironed out. I'm against a nack but I stand for a revisit. 16:56:08 ofrnxmr: The bounty seems a bit ambiguous 16:56:34 https://bounties.monero.social/posts/32/140-204m-i2p-baked-into-the-monero-gui bounty in question. That will most likely be changed to fit the spec of this proposal should devs deem it the correct way to integrate it. Would also be good to hear cuprates way of doing this 16:56:43 @syntheticbird: +1 16:56:49 +1 to what plowsof just said 16:56:56 Any submission that includes integrated i2pd binaries ("similar to how Bisq offers Tor support") could ostensibly be accepted, which is completely against what devs reccomend 16:57:24 I2P devs, I mean. I really want to make sure this is done the right way, which is with I2P SAM support in the daemon and a GUI interface later 16:57:30 Plus full migration guides 16:57:49 We'll revisit in a couple weeks 16:57:58 j. JackieXMR - [Set up a temporary news aggregation website](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/655) 16:57:59 Sounds good to me :) 16:58:03 hopefully coupe < 4 16:58:14 ?? 16:58:15 s/coupe/couple 16:58:28 hopefully you don't have to wait 4 weeks 16:58:32 Jackie can you explain your proposal quickly 16:59:11 yeah 16:59:37 2-3min need 16:59:56 Ok, we'll come back 17:00:10