15:03:43 Community meeting in 56 mins: https://github.com/monero-project/meta/issues/1429 16:00:21 Meeting time. https://github.com/monero-project/meta/issues/1429 16:04:18 hello 16:04:56 hi 16:05:15 👀 16:07:40 meow 16:08:52 Just a few of us here today, so lets just have a short meeting, since the last one was 2.5hrs 16:08:57 We can come back next week 16:09:28 3. Community highlights 16:09:54 Let’s wait like 5-10 more mins if that’s ok 16:09:54 maybe more people will join 16:10:43 After a 3 months break, https://revuo-xmr.com/ posted a new issue 16:11:30 https://magicgrants.org/2026/07/20/Skylight-Wallet-in-F-Droid 16:11:30 Skylight Wallet is now on the official F-Droid store, with reproducible builds (including for monero_c) 16:12:10 BasicSwapDEX was hit with an exploit on the refund path. Known loss = 0.66 BTC (total known 0.661 BTC total losses across 2 exploits) 16:12:42 DataHoarders transaction scanning suite propels a closed source 7 second full chain scanner which sech1 has seen first hand working 16:12:49 Zero “anti features.” The option for local scanning with a node (like other Monero wallets) is coming soon^tm 16:13:17 plowsof: I pointed out from there, it's different codebases :D 16:13:34 Does skylight plan to contribute changes back? 16:13:38 I can confirm skylight is a reproducible build, as fdroid happily updated my local skylight (same signing key) 16:13:41 again I did not develop that other one besides making that Tari bruteforcer :) 16:13:55 bootstraps, inspires? :D 16:14:05 @mrcyjanek0:matrix.org: It’s all MIT so take what you want 16:14:39 codeberg says no to cryptocurrency projects - not sure where this leaves wownero cc jwinterm 16:14:52 LGPL* 16:15:08 Hello 16:15:17 Wownero ia movonf to git.suchwow (or whatever the address is) with an already existing github mirror 16:16:07 monfluo and moneroswap are looking for new homes as well 16:16:24 I have moved my Monero-related project(s) off of Codeberg for the time being. Also investigating self-hosting Forgejo 16:17:04 remember you can always have your own forge that auto-pushes/syncs onto github/codeberg/whatever else you have out there (I do this myself with a bunch of my projects that I run on my gitea/forgejo instance) 16:17:16 @mrcyjanek0:matrix.org https://github.com/MAGICGrants/skylight-wallet/blob/main/scripts/reproducible.patch 16:17:33 I'd recommend self-hosting forgejo. Self-contained and quite compatible API 16:17:46 Otherwise it just pulls from vtnerd’s fork 16:18:25 ah okay, thanks! 16:19:02 If anything is unclear of how you can use it, let me know and I’d be happy to help 16:19:47 Appreciate it! Looks straightforward ^^ 16:22:54 If that's all for news, we can move on to the CCS proposals 16:23:28 a. jeffro256 - 2026 q2, full time development https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/688 16:24:06 merge please 16:24:14 +1 16:24:16 +1 16:24:25 +1 16:24:49 a great mixture of talent and motivation 16:25:48 b. [MRL] Dennis Trautwein - ProbeLab P2P Network Metrics Proposal https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/667 16:26:14 -1 16:26:46 this still has unaddressed comments, not sure if they maybe just havent seen them and need a ping? 16:26:59 I am clueless and will leave this to MRL 16:27:32 No opinion on this one 16:27:52 MRL helped shape the new proposal scope, which is why it is still open. but pending comments being addressed 16:28:19 c. jpk68 - full-time work (3 months) https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/689 16:29:03 +1 16:29:27 i havent yet commented on the proposal, only read through it once, and my first takeaway is that, if merged, it should not be funded using i2p bounty 16:30:14 +1 love the i2p stuff! 16:30:27 @mrcyjanek0:matrix.org: right???? 16:30:34 i2p was a different ccs @mrcyjanek0:matrix.org 16:30:42 @ofrnxmr:xmr.mx: Fair point. It's just a preference, however :) 16:30:47 if the work was specifically to add torcontrol support, you could argue for the funding from the bounty 16:31:36 @ofrnxmr:xmr.mx: I know, just mentioning that I like it 16:32:00 If the work was just for Tor Control, I would be sitting around like 70% of the time 16:32:07 Might as well make myself useful in the meantime ;) 16:32:42 bounty money is already supposed to be for a specific purpose. putting it towards misc tasks would be misappropriation 16:33:36 Since Gingeropolous is/was the creator of that bounty, I would like to hear what he thinks about this. If he or the majority of people don't like it, I'll remove it 16:33:37 if there was a specific milestone for torcontol, you could argue for that amount etc. this is just my opinion, particularly because we are already outside of the norm by using bounty money for ccs proposals 16:33:50 its not gingers money. 16:34:25 i think the proper path to requesting those funds, would be a specific torcontrol milestone and that amount to be requested 16:36:21 Fair. I will consider removing the bounty-related paragraph in that case, as another milestone-based proposal would not be convenient 16:37:46 imo, i dont think specific feature add (torcontrol) in the ccs would be accepted unless it is milestoned 16:38:35 @jpk68:matrix.org: your CCS idea has been shared via @MoneroSpace on X. https://x.com/MoneroSpace/status/2081056411925225587 // nitter: https://xcancel.com/MoneroSpace/status/2081056411925225587 16:38:56 are we talking about adding a tor control milestone into the proposal ? 16:39:10 yes, nioc 16:39:28 its mentioned in the proposal, but there are no milestones 16:39:51 I don't see how that would make any difference. The proposal is to work 40 hours per week on things, including Tor Control 16:40:08 rules :D 16:40:10 and if you dont finish torcontrol? 16:40:27 "For this CCS, I plan to work on the following areas: 16:40:27 Begin work on support for the Tor Control protocol in monerod, specifically for automatically configuring onion services 16:40:27 Look into integrating the existing I2P SAM implementation into 'core' wallet code for use with remote nodes 16:40:27 Continue to improve the usability, scope, and feature parity of the Monero GUI[... more lines follow, see https://mrelay.p2pool.observer/e/3pyWnZoLZnRackRN ] 16:41:31 I believe I have had quite a good track record in terms of being productive, and making good use of time. It's not like I'm going to purposely drag my feet and be lazy just to get funding without doing anything 16:41:55 thats not the point. you requested bounty funds for a feature that you may or may not complete 16:42:03 @ofrnxmr:xmr.mx: Maybe defining this properly in the ccs? 16:42:15 @ofrnxmr:xmr.mx: As I said, that can be removed. 16:42:16 @slowbeardigger:matrix.org: thats the request for milestones 16:42:27 All of my contributions so far, excluding I2P SAM work, have been unpaid 16:42:49 that has nothing to do with anything? 16:43:43 @ofrnxmr:xmr.mx: My point is that I don't understand the concern of not making good use of time, and therefore I don't agree with the milestone proposal except from the standpoint of receiving bounty funding. 16:43:52 its not a concern of making good use of time 16:44:12 right. if you arent requesting bounty funds, then the milestones arent as important 16:44:20 I understand, and have said I will consider removing the bounty note. 16:44:34 I appreciate your concern /srs 16:45:15 but deliverables do matter, and if torcontrol is one of them, then then it would be nice to see it completed instead of rolled into 9 months of proposals (not saying tha tyou will, but look at current funding efforts) 16:46:37 bounty funds = milestone = no issue getting funding. no bounty funds = it might not be funded if vaguely written with no promises or guarantees 16:47:08 synthethic has been a largely unpaid contributor for like, 3 years now 16:47:31 its not just about getting it merged, its about giving it the best chance of being funded 16:50:11 need to think about it from the perspective of donors. you have a "hack" where you can bypass the trouble and potentially get the money directly from the bounty. but that requires a torcontrol milestone. essentially a tor version of your last proposal. otherwise, you need to do some marketing etc to try to gather donors, since its appears to be a drought 16:50:18 "dont set yourself up for failure" 16:52:10 just something to think about. also, we will be branching soomTM, and getting i2p merged before that should be a priority, otherwise none of your i2p prs will hit release until fcmp 16:53:00 we can come back to this, i'll leave comment on proposal if necessary 16:53:15 (8 mins left) 16:53:30 d. panagot12 Monero LWS Observatory — Public LWS Health https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/686 16:53:51 ofrnxmr: https://github.com/panagot/Monero-LWS-Observatory not working, or down. 16:53:51 maybe ping the person? 16:54:25 probably banned for being bot-like 16:54:41 tons of AI sounding text too 16:54:46 https://github.com/panagot 16:55:12 @slowbeardigger:matrix.org: not a bad thing, but the repo is down 16:55:35 i looked at the vercel deployment of this, and while it looks like a typical slop website, but does seem like a viable idea. similat to monero.fail and ditatompel, but yeah. idk if i like it. 16:55:52 will need to find out what happened to the repo before moving forward, in ant case 16:55:53 any* 16:56:00 agreed 16:56:12 not foss = instaclose 16:56:46 e. v1docq47 - monero konferenco 2026 voice-over and working on xmr.ru https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/683 16:56:55 ofrnxmr: +1 16:57:21 i think id like to ask him if he's in a rush. if not, id like to wait to merge until the more urgent proposals are funded 16:57:54 he had trouble getting funded once before, and it doesnt look great to have multiple proposals awaiting funding for extended periods of time 16:59:02 otherwise, im a +1 since he's been doing this for years and all-but-1 times, hes been funded 16:59:16 f. r4v3r23 - ANONERO Continued development https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/671 17:00:31 -1 17:01:08 ofrnxmr agree re v1docq47 17:01:55 *agree with your thoughts 17:02:06 i have not checked to see if the repo is accepting registrations, issues, or prs. i think it would be a lot more approachable if it was available for community members to contribute to 17:02:45 in the last meeting there was an issue i believe, that there wasn’t all the code or some code open sourced? 17:02:50 Correct me if i am wrong 17:03:12 the code is open source, but the repo registrations were closed, so users like plowsof could not open issues 17:03:21 which lead to an anonero-fork that had the issues fixed 17:03:35 @ofrnxmr:xmr.mx: Thanks for the correction, this is a big turn off for me 17:03:44 (and also implemented the majority, or all, of the proposed featured from the ccs, and then added a few on top) 17:04:38 the repo is on a tor-only self-hosted forgejo http://git.anonero5wmhraxqsvzq2ncgptq6gq45qoto6fnkfwughfl4gbt44swad.onion/ANONERO/ANONERO 17:05:58 id like to see: plowsof register on the instance, open issues, submit pr fixes, and those fixes be reviewed and merged (if valid) 17:06:51 the issues found on anonero are being raised upstream + getting fixed e.g. https://github.com/monero-project/monero/pull/10937/changes 17:09:34 they have since opened registration on their git but you reap what you sow , years being closed off - dev(s) who have issues with the project lead have come forward - compare to another monerujo fork, monfluo - even the name was community voted on and has surpassed anonero in features - and contributors, just missing the bc-ur cold signing 17:10:23 and background sync* 17:10:36 apparently the features of anonero have been planned / decided already, i dont know where that took place 17:12:59 ofrnxmr: -1, but feels like there is no people commenting here, or at least enough 17:13:14 Should we leave the CCS for next week? idk 17:13:25 yeah, just looking for something quickly 17:15:11 cant find it. next time 17:15:45 we can end the meeting here. thanks everyone for attending. Next meeting August 8 2026, same place 17:15:55 👋 thanks 17:15:58 ty 17:16:04 take care yall 17:17:38 better highlight tbh plowsof, I used the Go scanning/code suite to find, get secret scalars, then make, prove, sign, and send a 1-in-2-out (not using wallet rpc, just the monerod decoys endpoint + send raw tx) a CLSAG + BP+ transaction spending from the zero-key wallet and got some "free range" XMR :) 17:17:43 (this is what triggered sech1 to build the efficient scanner) 17:18:38 what i s"free range xmr" 17:19:07 XMR that appeared on known public seeds 17:19:25 the abb(ey)? wallet 17:19:36 yep, the zero-scalar secret spend key 17:19:52 Left a comment regarding bounty funding: 17:19:52 https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/689#note_36994 17:52:42 The scanner is not 7 second, it's 8 seconds on RTX 5070 :D And I did it just to see how fast can it go, and to maybe implement GPU-accelerated wallet scanning for mobile GPUs (smartphones) - where it's needed the most. 17:54:16 Everyday I wake up and pray our god Khronos for giving us this miracle that is Vulkan compute shaders 17:54:56 CUDA, Metal, ROCm, OpenCL, etc can all go to hell 20:52:35 <321bob321> Cuda shoulda woulda