01:01:46 ssl would be awesome 03:45:47 [CCS Proposals] Yijia Zhang opened merge request #575: Add new file OPENENET-MS01-MoneroSpace-Decentralized-Satellite-Network-for-monero https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/575 04:46:03 <3​21bob321:monero.social> Starlink ? 05:49:28 Largest-sum CCS ever? 05:55:57 None of the links given in the CCS work for me right now. Maybe the censor has already attacked, and "censorship-resistant" has to wait a little longer :) 06:02:26 The git link works 06:02:26 https://git.openenet.cn/MoneroSpace 06:03:33 Website copyright `© 2024-2026 openENet` 06:03:55 living in the future 06:08:45 <3​21bob321:monero.social> Layout must be wrong 06:16:54 0.1 XMR PER LINE OF CODE???? lmao 07:57:23 <3​21bob321:monero.social> Coke is cheaper 14:00:25 Community meeting here in 2 hrs https://github.com/monero-project/meta/issues/1180 16:00:52 meeting time https://github.com/monero-project/meta/issues/1180 16:00:58 greetings hi 16:01:26 👋 16:01:56 Hello. 16:02:59 hi 16:03:30 recommended update [v0.18.4.0](https://www.getmonero.org/2025/04/05/monero-0.18.4.0-released.html) released , Kevin McSheehan reported a p2p crash vulnerability, which sadly made the release notes after site was deployed https://github.com/monero-project/monero-site/commit/3d6ac52ef83d7063d771bd21250dda3f913ca863 16:04:05 We'll get site redeployed shortly 16:05:21 tobtoht is sadly unable to make this meeting today. i hear he was building transactions on fcmp++ testnet in featherwallet :-o 16:05:24 Was not added to release notes because the vulnerability was a nasty one. Had to notify mining pools etc before it was disclosed 16:06:17 👍 i did personally send a support email to all the pools who had not yet updates after ofrnxmr requested. not sure if they have updated though 16:06:17 anyway, if you havent updated to 18.4.0, do so. 16:06:32 At least 1 of the top 3 pools have updates 16:08:51 Hi 16:09:03 j-berman and jeffro256 have announced the competition entry date https://www.getmonero.org/2025/04/05/fcmp++-contest.html this will ideally reduce transaction creation from several minutes to not several minutes :D 16:09:50 I read somewhere that it should be ~3seconds pre-competition 16:09:53 should be from <3 seconds to half of that 16:10:20 ok that is a relief 16:10:22 from MRL meeting 16:11:24 back links https://github.com/monero-project/meta/issues/1186#issuecomment-2798092566 , thank you 16:11:43 https://github.com/monero-project/meta/issues/1184 looking to add an "official" / reference for sharing node credentials via qr code 16:12:39 Currently, i think nodo and cake are the only parties using qrs to share nodes (maybe umbrel), but i want to standarize it with similar syntax to existing uris 16:12:52 👍 nice idea , instead o filling in several boxes like a peasant 16:13:25 We've had the ability to share wifi via qr/nfc for like 10yrs 16:14:37 perhaps monerokon attendees can use the node qr to connect their wallets to the kon's node(s) [Monerokon Tickets](https://www.monerokon.org/) for sale! 16:15:04 [Monero Observer](https://www.monero.observer/) - [Revuo Monero](https://revuo-xmr.com/) 16:15:05 4. [CCS updates](https://ccs.getmonero.org/) 16:15:18 oops, any other highlights people want to bring up* 16:16:05 Coin which added 'Exchange addresses' de-listed from Binance [Xcancel](https://x.com/monerobull/status/1909517550020370711) via monerobull 16:17:00 Yeah, thats what monerotopia did 16:17:27 (used nodo to allow merchants to scan the qr) 16:17:35 Merchants and attendees 16:17:41 👍 16:17:57 "coin" are we referring to firo? 16:18:02 correct 16:18:21 also to note that they have fully transparent addresses 16:18:56 Following the completion of the standard delisting due diligence process, Binance will delist BADGER, BAL, BETA, CREAM, CTXC, ELF, FIRO, HARD, NULS, PROS, SNT, TROY, UFT and VIDT on 2025-04-16. 16:19:22 They rolled over, played dead, and did what they were told. and then got discarded like they were garbage. Tldr: lol 16:19:51 ok lets move on to ccs ideas 16:20:03 its 420. Good idea 16:20:10 [Monfluo new tag](https://www.reddit.com/r/Monero/comments/1ju68ry/monfluo_v070/) via Revuo 16:20:16 a. [Btcpayserver plugin](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/538) 16:20:35 https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/538#note_29498 16:20:51 plugin migration complete ^ 16:21:26 i thought monero-lws milestones where highly contested , i was wrong on that 16:21:32 I feel like they dont intend to address any comments. 16:21:59 wasnt the consensus the last time to make some changes and then merge? 16:22:04 but the changes didnt happen? 16:22:04 You werent "wrong". More that nobody outright said to remove them 16:22:11 Yeah, changes didnt happen 16:22:43 Their lws plans conflict with other oarts of the ccs 16:25:07 What changes? 16:25:11 M1 is good 16:25:24 Each of those deliverables should remain 16:25:29 ofrnxmr made some suggestions 16:25:42 Sure - let’s be clear what change. 16:26:36 Each of those deliverables represents work we’re doing at this time and should continue. Which deliverable should not stay 16:26:47 Migrating the plugin takes all of 120 seconds 16:27:01 ofrnxmrs suggestion https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/538#note_29353 (not sure if changed) 16:27:18 Quite literally like 5 clicks in web browser, and 3 command in git 16:28:39 It clearly hasn’t. This proposal has been open 3 months. It took 2 months for you to even process BTCPay wasn’t continuing to host. 16:28:54 Hasnt what? Taken 120 seconds? 16:29:09 i could do it in 5s fyi 16:29:20 will monero-plugin need their own build server? 16:29:20 right 16:29:33 No 16:29:44 We are using GitHub actions and pushing to BTCPay 16:29:53 They have a build server 16:32:13 plowsof my suggestions havent changes. They dont cut much out of the deliverables either. Just reworded to be accurate (w/o duplication and non-work) 16:32:53 and that wouldnt require and change in total work per milestone? 16:33:22 i mean total effort would remain the same 16:33:33 yeah, less than advertised 16:34:04 As in, theres no work involved in forking a repo, dockerizing lws, or creating remote node support (that already exists) 16:35:01 Are we skipping unit test? That is a chunk of work that doesn’t exist 😂 16:35:26 so for example, funds have been set aside for dockerising monero-lws in milestone 3 https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/538#milestone-3-minimum-viable-product-mvp-for-multiwallet-support 16:35:52 this is done? and we're paying for duplicated effort. and there are other examples of this? why can;t this be fixed? 16:35:56 No - that says if not available 16:36:06 fix it? 16:36:12 Meaning we have been talking with vtnerd and intend to leverage what is available once we get there 16:36:19 If it’s not there, we contribute upstream 16:36:23 What’s wrong with this? 16:36:34 So are you sending the funds to vtnerd? 16:36:43 Magic has an lws docker as well 16:37:24 there has to be some adjustments for us.... 16:37:33 just one example of duplication at a glance. the docker lws issue was mentioned last meeting too but nothing changed reg that 16:37:43 1 small example :-S why cant ya just fix it D: 16:37:54 Again, leveraging what is available. It was added to ensure we addressed a gap in implementation if it exists 16:38:16 We sure can remove it 😂 what does it change? 16:38:22 its been 9 months since the proposal was opened please adjust for reality 16:38:23 "if not available" implies that youll create an unofficisl one if there isnt an official one. But there exists an unofficial one already (magics), and vtnerd has already expressed that he'd do an "official" one 16:39:08 ofrnxmr what does it change? are you requesting a reduction in advertised work and total funcing request? 16:39:42 or will monero-plugin team fill in the gaps elsewhere to keep effort the same 16:39:50 for real are you suggesting that we should use some magic container that is unofficial and can contain malicious parts?... 💀 16:40:09 are magic malicious 16:40:28 the ccs funnel tens of thousands of montero to them , this is a serious accusation we need to investigate 16:40:30 What "monero" docker are you using? 16:40:44 BTCpay until we shift 16:41:05 Do we need a separate meeting? We do this every two weeks 16:41:14 This is clown shit at this point 16:41:40 okay moving on 16:41:41 well, your roadmap conflicts with itself 16:41:47 almost 1 am here 16:41:48 Have we refined any other work like this 16:41:50 b. [Monero Browser Wallet](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/555) 16:42:01 woodser made some great comments since the last session. 16:42:33 Are you addong remote node support (exists already), are you reviewing remote node support (??), or are you running an lws server snd monerod locally 16:42:54 spirobel linked woodsers comments in this comment https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/555#note_29394 16:43:19 seems like people are seeing the value in this. would be grateful for a merge after this 4th session. 16:43:32 are you telling us the remote note wont need any more work?.. 💀 16:43:56 Are you telling me that lws is intended to use remote nodes? 16:44:28 i told u there will be 2 options 16:45:00 and the former already uses remote nodes, single wallet instance, and wallet-rpc. 16:45:41 Are we questioning the intention of a previous bounty here? 16:45:49 no? 16:45:50 spirobel is your plugin -optional- for tor browser? or specifically / only for the tor browser? 16:45:55 This wasn’t a feature Napoly submitted - it was one he implemented and has been waiting to merge. 16:46:21 What youre referring to is a gui to define the node 16:46:48 And is proposed is my suggested milestone 1 16:47:20 Thats not remote node support, thats a gui to set the variable (which was done incorrectly in the pr* 16:47:30 plowsof: it will work with all browsers 16:47:41 sprirobel i can better say is the browser wallet tied to any specific web browser? ok thank you for clarifying. 16:47:57 no its not tied to a specific browser 16:48:42 see.. so it still requires some work 16:48:51 this is also an example of suggestions being made and spirobel clarifying that they do not need to be made :D 16:49:17 I never implies that the gui should be dropped from milestones @napoly 16:49:43 tor suggesting no 3rd party plugins should be used is not a blocker though 16:50:07 "M1: Finish GUI for remote node configuration started here.. making sure to address this comment" napoly 16:50:31 sorry for interruptions, can come back after 16:52:20 plowsof: tor makes this suggestion because extensions could damage user privacy. In this case it will enhance user privacy and help people keep their identity separate. I can add documentation to this specific part if that can help alleviate concerns. 16:52:29 initially the total price of spirobels proposal raised some concerns but it was clarified as being a bargain. tor being against plugins is not a blocker as the browser wallet is universal. a suggestion to drop " - name: Multisig companion app + escrow library" as a milestone was made, but spirobel says it can not be. 16:52:33 the tor browser has noscript preinstalled as well. 16:53:00 so what is to be done (: 16:54:14 I'm not sure what u want from us.. I do value ur criticism.. Deverick did change the proposal to your liking.. but that wasn't enough. 16:54:58 plowsof why can't any of the milestones be dropped? 16:55:26 the multisig companion app is important because it will help people get over their concerns regarding browser wallet security. It makes sense to do this all in one package, because all of these pieces are related. 16:55:34 spirobel said milestone 3 is required and can not be dropped , none negotiable 16:56:06 am i foolish for thinking, well why not? and then a follow up proposal for this? likely 16:56:14 Probably an easier merge if its split up into separate ccs 16:57:01 imo milestone 2 is useful, could help with adoption. i don't believe the claims about increasing privacy or most of the other claims. 16:57:04 It is better this way. Because it should be tightly integrated into the experience of using the wallet from the beginning. 16:57:13 also this is the 4th session. 16:57:36 isn't multi-sig about to change significantly with fcmp++? 16:57:39 this was brought up so late 16:57:48 so work done there will not be useful for long? 16:57:53 no the underlying tech stays the same 16:58:04 we just paid for the audit 16:58:15 which will be finished soon 16:59:20 I don't want to split this up. seriously. It is tightly related. Also because it creates a forcing function for the library design 16:59:39 so what. youre not entitled to a merge, and there will be 1000 sessions if needed 16:59:45 J0J0XMR suggested removing milestones a month ago 17:00:15 why dont you guys focus on your stuff. I spent so much time on this. you voiced your concerns. You through mud 17:00:21 *threw 17:00:24 and now just leave 17:00:28 stop nitpicking 17:00:40 you gave your 3 downvotes 17:00:42 now leave 17:00:44 browser wallet ccs is an obvious cash grab 17:00:46 its enough 17:00:52 i vote close 17:00:56 anonero is an ovious cash grab 17:01:15 insanely priced and no clear objectives 17:01:32 next 17:01:35 I open sourced the mvp too btw. 17:01:48 crazy insulting to call this a cash grab 17:02:01 why do we allow this to be sabotaged by these people ? 17:02:21 haveno mobile app is a cash grab too 17:02:31 no, just browser wallet 17:04:05 moving on for now then 17:04:24 e. [ANONERO: remove self imposed deadline](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/569) 17:04:52 i think ive said everything i needed to say in here a few days ago 17:04:55 dont remove the deadline 17:05:09 ofrn made some changes to the erge request that ive accepted 17:05:17 didnt deliver 17:05:26 that would be [Remove deadline](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/573) 17:05:29 you are not entitled to a merge 17:05:43 +1 . That deadline is like 2 weeks from now. 17:05:44 yes 17:06:01 yeah the funds should be redistributed 17:06:05 merge 569 17:06:07 not entitled to a merge 17:06:43 idk what the merge ppeline issue is on 569 17:06:59 ignore pipeline for these edits 17:08:01 anyway, work on NERO has already started n new branch on git 17:08:10 as for 573 - adding the notice -before- completing the payout of milestone 2 was an oversight on my part, i apologise to the ANONERO team / r4v3r23 . payout for milestone 2 was expedited to reflect recent milestone completion. 17:09:06 thanks. i just wanna complete this without any needless red tape 17:10:11 moving on as we're over 17:10:14 f. [Haveno iOS and Android App](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/570) 17:10:55 ofrnxmr: I provided a decent reason for why this shouldnt be split up. JOJOXMR didnt even read the proposal properly when he left his downvote 17:11:01 splitting this up makes no sense 17:11:19 Theres another haveno app in the wild 17:11:22 and is just further obstruction by the 3 people that already gave their downvotes 17:11:45 At this point, i think _any_ claim for haveno ui/app shit should be retroactive 17:11:47 ofrnxmr: i went through that repo. i couldn't find any actual logic in that code 17:11:50 that .net project 17:12:36 what do you mean by "retroactive"? 17:12:37 I havent checked, but i stand by my statement about haveno ui/app stuff being retroactive 17:12:51 are you referring to the LootSpam bounty comment(s)? https://bounties.monero.social/posts/126/37-175m-building-an-open-source-android-app-for-haveno-dex 17:14:01 after the kewbit situation - finding a team that is qualified to do a paid / trusted review of the submitted work seems essential 17:14:30 monerobull, boldsuck, and woodser are capable 17:14:55 i worked with woodser to get going with the api 17:15:32 I can't really review code 17:15:46 I've been doing builds of all his haveno related repos, contributing to most of them, so he's aware that i know that codebase fairly well 17:15:46 do not down play your vibe skills 17:15:59 would have done the cloned offers feature but he beat me to it 17:16:01 I could review it. 17:16:12 Good meeting, thanks everyone. 17:16:22 thanks for attending msvb-lab 17:16:43 monerobull yeah i meant at the least, testing 17:18:34 we have a few more proposals to get to 17:18:41 this is the lootspam attempt : https://github.com/LootSpam/Building-an-Open-Source-Android-App-for-Haveno-Dex/ 17:19:15 (We should probably start with the easy /lowest discussion proposals) 17:19:22 is it garbage? AI slop? legit? i have no idea 17:19:25 g. [tobtoht full-time feather + core development (3 months)](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/571) 17:20:04 tobtoht can not make it today but sent his greetings , featherwallet 17:20:26 real quick, is the ability to use haveno on the go & still have offers live / available when a phone OS closes the app, is that useful for the community? 17:20:27 Merge 17:20:43 thanks for leaving feedback already everyone 17:20:45 h. [j-berman full-time development (4 months)](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/574) 17:21:00 Merge 17:21:01 auto merge last 2 17:24:51 thanks all for attending 17:54:01 ofrnxmr what do you mean by "retroactive"? 17:55:51 I mean, like a bounty. 17:56:04 Present finished product -> get paid 17:56:45 oh i agree, the proposal says that, each milestone is value for value 17:56:59 Unless your ccs is absolutely _not_ trying to claim the already-raised haveno funds 17:57:41 idc where the funds come from 17:58:10 there's no upfront payment anywhere in there 17:58:17 are you looking to raise funds from 0? 17:58:27 absolutely don't care lol 18:00:08 Example: kewbit raised 0xmr. The funds for his ccs were repurposed from existing pool of haveno funds. If your ccs is raising its own funds, then this doesnt add any risk to the leftover funds from prior haveno ccs 18:03:28 I didnt see when that happened. I don't know who makes that decision. 18:03:51 I'm not aware that it's me. 18:16:31 First people complain about the supposed insecurity of browser wallets. Then I come up with a plan to make everything multisig by default, so multiple devices have to be compromised. And people still complain and want to split it up. It is just annoying. 18:59:06 lmfao multisig browseer wallet for muh mass adaption 18:59:31 for a con thats essentally delisted 18:59:33 for a coin thats essentally delisted 18:59:51 i did some searching on browser wallet security and didn't find anything alarming, hence my change in stance. i'm ok with milestone 2. the others seem pointless. 18:59:56 so easy oppressed women in afghanistan can use it! 19:05:25 if these two have veto rights in this project I am just going to admit defeat and work on something else. 19:06:39 leads to burn out having to "debate" the same nonsense over and over every two weeks until 3 am in the morning 19:15:38 or maybe its just a retarded overengineered idea to solve.. checks notes.. copy/pasting an address