12:03:51 meeting in 4~ hours https://github.com/monero-project/meta/issues/1178 16:00:20 Meeting time https://github.com/monero-project/meta/issues/1178 16:00:25 greetings! 16:00:49 Hello. 16:00:56 hi 16:01:33 hello 16:01:47 latest version of Monero has been tagged 18.4.0 so expect a release in the coming days after contributors have submitted gitian builds . Featherwallet has also tagged release v 2.8.0 16:02:01 Oh is it that time 16:02:43 I was excited this nice tweet from @monero listing all the ccs proposals recently funded ❤️ https://xcancel.com/monero/status/1905346094306930772 16:02:50 hello 16:02:54 Plowsof, youre late. Rotten pinged every room before durong and after the tag 16:02:55 By the time the binaries go up, the novelty factor will have worn off 16:03:29 outreach 🚀 16:04:25 nice that @monero tweeted _after_ they were funded 16:05:35 some waaaay after 16:06:15 from the prev mrl meeting: optimized implementations of [helioselene](https://github.com/kayabaNerve/fcmp-plus-plus/tree/develop/crypto/helioselene) and [ec-divisors](https://github.com/kayabaNerve/fcmp-plus-plus/tree/develop/crypto/divisors) competition has submission date suggested in #1177 @ [excerpt](https://libera.monerologs.net/monero-research-lab/20250326#c513589) , and new 16:06:16 FCMP++ research approved from veridise @ https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/449#note_29339 16:08:20 any other highlights people want to mention? 16:08:44 https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/540#note_29336 16:08:44 jeffro256 "all there is to do before an alpha stagenet is to integrate the tx construction code into wallet2." 16:08:47 plowsof: that was only on SimpleX and Revuo' 16:09:00 s, matrix and IRC were unaware. Teamwork! 16:09:05 Regards to my fan! <3 16:09:06 anonero has claimed milestone 2 of CCS: <nioc> https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/447#note_29268 16:09:19 also removing self-imposed 1 year time limit on CCS. even with adding all the extra features into milestone 2, milestone 3 wont be ready by deadline 16:09:37 currently working on NERO/airgapped txs 16:09:49 (deadline is in like 1 week) 16:09:50 So obv not realistic 16:10:39 people are invited to test current build and report feedback/bugs in simplex chat 16:10:47 The first release of new build came out ~1week ago (and is good. Not vaporware) 16:12:10 nice 16:12:23 it took longer because of the added features ? 16:12:57 plowsof can we start opening meeting issues earlier than... the day before? Lol. 16:13:06 https://github.com/monero-project/meta/issues/1178 opened yesterday smh. 16:13:33 no problem 16:13:38 If they are bi-weekly they could at the very least be opened a week ahead, giving you a week to go to the nail salon and stuff... 16:14:56 last year ANONERO did not work in the summer, and are at risk of doing the same this year, this is why they remain in !537 but thats for later 16:15:21 there is no "risk", yo ucan stop being petty over a simple comment made months ago, kthx 16:15:37 and unless !537 was voted on and merged, it just remains your little list 16:16:18 id seriously like to see you impose a hard deadline on an active project that has contributed to monero ecosystem as a whole, while there have been dead CCSs open for YEARS 16:16:42 there are no deadlines 16:17:22 moving on 16:17:23 glad thats settled :) 16:17:44 Tssss. 16:18:28 just joined the anonnero simplex lol 16:18:31 [Monero Observer](https://www.monero.observer/) - [Revuo Monero](https://revuo-xmr.com/) 16:18:37 ok lets move on to ccs ideas 16:18:46 it exists! 16:18:52 a. [Btcpayserver plugin](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/538) 16:19:12 deverickapollo napoly sars. 16:19:22 I provided a update following community comments with a brief summary in the comments 16:20:40 Let me know if there are any questions 16:20:49 https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/538#note_29346 16:21:08 cc sgp_ 16:21:32 I briefly looked over the changes, but it just seems to be some shuffling around and potentially less deliverables for the same rates 16:21:49 is this settled? 16:21:52 I believe you asked to remove some duplicates. 16:22:06 This should more/less resemble the same 16:22:49 Like what is this? "Push review of remote node implementation" 16:23:16 "Deliverables: 16:23:18 Plugin repository established and accessible 16:23:20 " 16:23:28 Napoly has an open PR to merge the remote node implementation. We planned to include this earlier but discussed reviewing it following lws implementation 16:23:30 This is not a paid deliverable. Creating a git repo? Lol 16:23:50 "Operational CI/CD pipeline for plugin development and releases." This is already completed bt btcpayserver 16:23:52 why is it either/or? 16:23:57 CI/CD development/unit testing/code coverage all there in Milestone 1 16:23:59 I only have a technical question about if they've looked into subaddresses with lws specifically, since those are different 16:24:08 "Support for existing merchants and users" this is fluff, and at m1, is meaningless 16:24:17 Yes, we talked with Vtnerd about subaddressing with lws. No issues here 16:24:31 " Napoly has an open PR to merge the remote node implementation. We planned to include this earlier but discussed reviewing it following lws implementation" this doesnt even work 16:24:43 there is no release.. and was not done by btcpayserver 16:24:52 It can be a gui for editing the node, but you cant use "any" remote node 16:25:03 It has to be specially configured 16:25:39 we moved the remote node down the line.. as mutliwallet has higher importance 16:25:41 not for lws or rpc. Rpc requires block-noifity, and lws requires zmq-rpc 16:25:55 and once lws is in place the remote node needs to be re-thinked 16:26:13 it need to be rethought out for kws and rpc. 16:26:18 id think removing a full node sync req is much more useful that adding another wallet 16:26:38 both required a node that is configured with special flags 16:26:55 multiwallet exists elsewhere already if merchants need this (bitcart.ai) 16:27:02 The new plugin has XMR_DAEMON_URI env variabke 16:27:34 i'm just listening to what the creator of the biggest payment processor said https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/538#note_28197 16:27:36 meaning? 16:27:59 `UI improvements for Monero daemon configuration.` this is 100% of the remote node stuff 16:28:14 Meaning you can set a remote node by changing the env variable 16:28:39 so it already has remote node support? 16:28:47 Eh that's not a UI but it's also a small task not a major one 16:28:52 No - UI improvements for daemon/wallet refers to most of the work highlighted in the bounty https://bounties.monero.social/posts/88/15-008m-btcpay-server-additional-optimizations 16:29:01 no it's not.. there are other things..... 16:29:22 Yes. Milestone 2 looks reasonable 16:29:28 related: if MAGIC require a c# dev, may a recommend Henry who has PR's merged to btcpayserver and created the monero bounties bot https://github.com/monerobot/monerobot 16:29:35 And is covered by the bounty, it seems 16:29:56 that bounty is there for like 3 years now.. 16:29:59 "Dockerize monero-lws if not available" 100% out of scope 16:30:01 come on 16:30:09 So claim it 😭 16:30:14 Tf lmao 16:30:24 it's not... as there is no official lws docker image hosted anywhere 16:30:25 What ya waiting for? 16:30:34 u do 16:30:37 lmao 16:30:46 Plowsoff you literally told us to halt all development - wtf 16:30:49 [@vtnerd:monero.social](https://matrix.to/#/@vtnerd:monero.social) said he'd do docker if ppl needed it 16:30:51 MAGIC has done this: https://github.com/MAGICGrants/monero-lws-docker 16:30:52 I can easily put MIT on that 16:31:07 Nicolas reached out to us.. as no one cared.. i'm not gonna kill myself for 15xmr lol 16:31:25 that should be done by vtnerd 16:31:30 yep - we chatted with vtnerd about it a few days ago. It sounded like that part was something he could get done within the time we need 16:31:32 Sgp clearly died twice while making the lws docker 16:31:47 Duh. So remove it from your deliverables 16:32:04 If its not available, we will need it 16:32:09 There is a conditional 16:32:19 we had a chat with him 3 day ago 16:32:22 deverick: the bounties where made pre plugin so requires some adjustments 16:32:39 if thats what you mean by stop all work on completing a bounty for something obsolete 16:32:43 Correct - and those adjustments were made over the past week 16:33:08 no one was able to solve that bounty so there was a spin off bounty 16:33:47 perhaps henry can complete them 16:33:54 perhaps? 16:34:01 Oh "not killibg myself for 15xmr" was napoky saying he wants more $ for this 16:34:16 Are we actively discoraging developement for perhaps? 16:34:28 cant blame pkowsof when nap is the one who said that the bounty can't afford him 16:34:44 Go claim the bounty 16:34:45 dude i did a pr.. what u did? 16:34:50 nothin 16:34:57 Your pr is broken 16:35:06 Always was 16:35:09 at least i did smtng 16:35:15 Heckle, heckle and disrupt wherever he goes. That's all he does. 16:35:29 can some one explain why taking ownership of a btcpay plugin thats already been built for us is such a headache 16:35:50 15 minutes spent "discussing" this proposal and all I can see is a bunch of kids arguing in kindergarden. 16:35:56 there is a power grab 16:35:58 because they was $ to create a git repo and dockerise lws 16:36:05 we can clarify the bounty scope soon then as you say things have become clear the past week, i guess im running a bit behind 16:36:17 paid to who? 16:36:34 Its in the ccs milestones 16:36:50 lws should be a nice add on, not a show stopper 16:37:03 local node/remote node/lws 16:37:10 those should be the 3 options in UI 16:37:38 thats milestone 2 16:38:27 i depend on services that currently use btcpayserver, so there is no personal 'lets stop btcpayserver from existing' on my end 16:40:13 M1 mostly NACK 16:40:14 M2 ACK 16:40:16 M3 remove dockerize lws, ack the rest 16:40:18 M4 not complaining 16:40:20 changes where made recently with the summary even more recent so up for discussion still, lets move on to the other proposals? 16:40:28 i dont even think btcpay allows for a remote bitcoin node (maxis trying to enforce running a node) 16:40:47 so remote xmr node would make is 1000x more useable for new merchnats 16:41:02 they dont require you to accept btc to run it, so out of scope 16:41:13 what? 16:41:50 https://github.com/btcpayserver/btcpayserver-monero-plugin#configuration 16:41:58 Remote node stuff is right there 16:42:07 we are waiting 3 months for a green light.. these changes were made by deverickapollo as a response to complains from previous meetings 16:42:33 great, wrap it up in a simple UI on dashboard and happy days 16:42:49 Yeah, milestone 2.. ack'd 16:43:07 and the work was already started and covered bt the bounty 16:43:23 But napoly sayd he wont kill hinself for 15xmr, so he's NACKing the bounty 16:43:30 🙄🙄🙄 16:43:37 I need unit testing and code coverage. I can move those into mikestone 2 16:43:40 thats why we want to incorporate those bounties 16:43:46 Can we just completely close the bounties? 16:44:01 Take the money out and set aside 16:44:13 Use for this CCS, or anything else related 16:44:23 or just apply bounty XMR to ccs 16:44:29 In this CCS I recommended we move bounty funds into this broader developemnt and ensure alignment. IF we need a separate meeting for some of those involved, we can get that scheduled. I don't want refinement here to take the whole meeting time. 16:44:32 like this specific one 16:44:34 Probably the former 16:45:01 The bounties are just noise, they are too old at this point 16:45:35 I'd be OK with donating the relevant bounties to this CCS 16:45:52 bounties have been sent off site to external funding platforms already so entirely possible, noted 16:46:09 same, lets just get this done 16:46:24 approx 30 xmr 16:46:36 I'm till NACKing most of m1 and the lws docker stuff 16:46:52 like i said, lws should be an optinal addon 16:46:58 its not directly related to the plug in 16:47:11 so if thats in the CCS, i say remove it/separate it 16:47:13 Lws docker is not a part of this ccs 16:47:16 Personally I'm a fan of fewer milestones, making sure the remote mode stuff and other UI improvements are done first, then doing lws. Maybe 1 milestone for all stuff without lws and 1 for lws. Then find with bounties and call it a day. My 2c 16:47:16 M1 Operational CI/CD pipeline for plugin development and releases and Testing framework and code coverage are the only two real meat. 16:47:30 Its done by magic and will be done "officially" by vtnerd 16:47:53 Happy to remove LWS that if we can align on dates there 16:48:01 I already told vt they can steal the docker stuff, I don't care 16:48:07 holding this up over LWS is retarded 16:48:11 its not essential 16:48:25 Its probably 50% of the actual work in the ccs 16:48:27 lws-docker part will be removed from milestone 3 16:48:40 Should not* be a part of this cs 16:48:45 The LWS part opens a whole new ecosystem of self hosted trusted communities for ecommerce 16:48:58 then make a separate proposal 16:49:00 why confuse things, this is about btcpay plugin not lws 16:49:07 there were 2 proposal for lws docker 16:49:09 not directly related 16:49:10 "Personally I'm a fan of fewer milestones, making sure the remote mode stuff and other UI improvements are done first, then doing lws. Maybe 1 milestone for all stuff without lws and 1 for lws. Then find with bounties and call it a day. My 2c" and dropping LWS milestone +1 for me 16:49:13 focus on btcpay plugin first 16:49:15 then nice addons 16:49:21 prioritize 16:49:27 there were 2 proposals for lws docker 16:49:47 Integrating LWS is literally improving the plugin integration with btcpay. Its currently setup so if you install this plugin, the environment should not be shared with untrusted parties as the sigle wallet instance is exposed to multiple stores 16:49:54 R4v3r, because the plugin w/o docker is functional 16:49:55 this ccs basicallt just adds ui for configuring a remote node, and lws support to enable multi-wallet 16:50:02 youre not listening, were not against LWS 16:50:14 were against tying it into the CCS for btcpay server plugin 16:50:15 Most monero users have only seen the one store side of the experience - we want to open up https://docs.btcpayserver.org/Deployment/ThirdPartyHosting/ 16:50:22 maybe if those changes are made it can be directly merged? or is there another meeting necessary 16:50:24 you need to sepratate the 2 16:50:33 i think this is taking too much space and its time to make a decision 16:50:40 no one is denying that LWS is good 16:50:48 its not necessary for btcpay server monero plugin to run 16:50:55 and remote node is much easier that self hosted LWS 16:50:57 https://github.com/btcpayserver/btcpayserver-monero-plugin - Nicolas put a warning about it on the plugin and was part of the encouragement to ship this 16:51:14 and remote node is much easier than self hosted LWS 16:51:34 I don't pick problems because they are easy. I look to bring new value to our community 16:51:42 https://directory.btcpayserver.org/filter/hosts 16:52:01 wheres it hosted now? still on btcpay? 16:52:04 To repeat what i said but got buried "this ccs basicallt just adds ui for configuring a remote node, and lws support to enable multi-wallet " 16:52:36 actionable feedback has been provided here, i think we can move on 16:52:41 yes 16:52:46 b. [Monero Browser Wallet](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/555) 16:52:53 lol 16:52:55 https://github.com/btcpayserver/btcpayserver-monero-plugin 16:53:03 will cleanup and see you in 2 wks 16:53:14 could use chatgpt to sum it up and defluff 16:53:19