00:00:05 -xmr-pr- [css-proposals] rottenwheel opened pull request #559: Revuo Monero Maintenance (2025 Q2)
00:00:05 -xmr-pr- > https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/559
00:00:42 <plowsof> 2.5 + 2.5 + 2 = 8 
00:01:02 <dukenukem> forget that for a second.
00:01:07 <dukenukem> file "creation" looks fine?
00:02:42 <dukenukem> fixed, btw.
00:03:16 <plowsof> its going straight to work in progress without funding? 
00:04:20 <plowsof> https://ccs.getmonero.org/how-to-ccs/
00:04:58 <dukenukem> I believe I said fixed?
00:05:01 <dukenukem> lol
00:05:50 <dukenukem> would you look at that? https://ccs.getmonero.org/ideas/
00:06:36 <dukenukem> https://files.catbox.moe/4t32hc.png
01:51:38 <m-relay> <s​yntheticbird:monero.social> cuprated achieved fast-sync in 1h50m: https://matrix.to/#/!zPLCnZSsyeFFxUiqUZ:monero.social/$hvQ5GxwDWBZJKxjsPMzi2mVnqHoNlCKaXmVz38mzTIs?via=monero.social&via=matrix.org&via=unredacted.org
02:53:04 <plowsof> 👏
04:03:29 <m-relay> <s​pirobel:kernal.eu> sir, this is a community workgroup channel 🙂
12:57:32 <n1oc> [CCS Proposals] plowsoff opened merge request #560: plowsof CCS Coordinator https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/560
13:00:05 -xmr-pr- [css-proposals] plowsofff opened pull request #560: plowsof CCS Coordinator
13:00:05 -xmr-pr- > https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/560
15:58:15 <m-relay> <p​lowsof:matrix.org> meeting in 2 hours https://github.com/monero-project/meta/issues/1164
16:15:08 <m-relay> <a​remor:matrix.org> Oh nice. New time
16:20:31 <m-relay> <s​pirobel:kernal.eu> 2 am here 🌃
17:00:05 -xmr-pr- [meta] rbrunner7 opened issue #1165: Monero Tech Meeting #110 - Monday, 2025-03-03, 18:00 UTC
17:00:05 -xmr-pr- > https://github.com/monero-project/meta/issues/1165
17:34:09 <m-relay> <b​usyboredom:tchncs.de> I'm moving this weekend so won't make it to the meeting, but my update for AcceptXMR is:
17:34:10 <m-relay> <b​usyboredom:tchncs.de> Had a fun side quest packaging the WordPress plugin for nixos-based WordPress installations. Slow progress on the currency conversion work, should make faster progress next two weeks since I'll be done moving.
17:59:50 <plowsof> Thanks for the update busyboredom 💪
18:00:16 <m-relay> <o​frnxmr:xmr.mx> i prefer the old time (1600utc)
18:00:30 <m-relay> <o​frnxmr:xmr.mx> The later it gets, the more it lands in the middle of stuff
18:00:35 <plowsof> Meeting time https://github.com/monero-project/meta/issues/1164 
18:01:30 <plowsof> first time at 18:00 , maybe 20:00? or back to 16:00 we can play it by ear 
18:01:53 <m-relay> <s​pirobel:kernal.eu> 16 pls 20 would be 4am for me
18:03:12 <plowsof> right... ok lets get through the major  recent events 
18:03:41 <plowsof>  [OSPEAD](https://github.com/Rucknium/OSPEAD) "since the August 2022 hard fork [...] an effective ring size of 4.2" - Rucknium [related reddit thread](https://www.reddit.com/r/Monero/comments/1ivnef8/rucknium_has_published_ospead_findings_showing/) xenu 
18:04:10 <m-relay> <m​ichael:monero.social> Hello.
18:04:28 <plowsof> hello
18:05:14 <plowsof> im wondering if any chainalysis have been using this already, or, if they can show the effects on existing research , e.g. moonstoneresearch / sgp_ report on the CCS hack https://moonstoneresearch.com/2023/11/03/Postmortem-of-Monero-CCS-Hack.html 
18:06:12 <plowsof> cuprated fast sync entire blockchain in under 2 hours (fast sync is the default sync method of monerod*) [related tweet](https://nitter.net/KevinoTech/status/1895772875086520336) rottenwheel
18:06:36 <plowsof> 2.5x faster according to #cuprate syntheticbird 
18:06:58 <plowsof> https://ccs.getmonero.org/funding-required/ 🙏 
18:07:25 <ofrnxmr> Looks like cuprate optimized randomx syncing
18:07:52 <ofrnxmr> Previously it was seconds per batch, now it looks to be about as fast as pre-randomx 
18:08:09 <plowsof> ofrnxmr yo umentioned 're writing monerod in c++ would yield improvements also' which i found funny 
18:08:56 <ofrnxmr> 😆😆 yeah. Starting from scratch w/o all of the inherited deficiencies  
18:10:22 <plowsof> j-berman has developed / given presentation on faster syncing for clients IIRC wonder if cuprate could adopt this in the future (i assume this would be for a cli rather than the daemon, i could be wrong)
18:12:12 <m-relay> <s​pirobel:kernal.eu> link?
18:13:54 <ofrnxmr> -dev needs to not-ignore what cuprate is doing. Clearly the 2x*2 speedup should be possible to be duplicated on monerod
18:14:38 <plowsof> for berman? ill have to find it / confirm - i vividly remember a presentation perhaps at a cake sponsored event where the async style sync was mentioned 
18:15:21 <ofrnxmr> Cuprate was one-upon-a-time slower tobsync the first 100k blocks than monerod, and ~same speed to sync the full chain. I dont think the optimizations are voodoo
18:15:37 <ofrnxmr> One of them was simply the sync-mode 
18:16:10 <ofrnxmr> cc hinto boog900
18:17:42 <plowsof> can move on to ccs ideas in the mean time 
18:18:03 <plowsof> meantime* 
18:18:15 <m-relay> <o​frnxmr:xmr.mx> Yea
18:19:11 <plowsof> just to mention tat vtnerd was merged to funding , but feedback is welcome (what to focus his time on etc) https://ccs.getmonero.org/proposals/vtnerd-2025-q1.html 
18:19:52 <plowsof>   a. [Funding Proposal for Unstoppable Wallet: Enabling Native Monero Integration on iOS & Android](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/532)    
18:20:39 <plowsof> j0j0xmr had linked  a commit, removing something from their paid tier , however the concerns in the proposal comments remain unaddressed 
18:20:42 <ofrnxmr> Close / reopen if they ever feel like responding
18:21:27 <n1oc> [CCS Proposals] plowsoff closed merge request #532: Funding Proposal for Unstoppable Wallet: Enabling Native Monero Integration on iOS & Android https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/532
18:21:36 <plowsof> i agree, oops, moving on
18:22:18 <plowsof>   b. [Btcpayserver plugin](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/538)    
18:22:54 <plowsof> a new comment from Deverick https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/538#note_28917
18:23:25 <m-relay> <s​pirobel:kernal.eu> and this one https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/538#note_28920
18:24:00 <plowsof> also wondered what the emoji meant lol
18:24:40 <ofrnxmr> I dont understand deverick, napoly and skunkwheel thumb downing my comment that btcpayserver 2.1 will launch with monero support. The ccs proposal doesnt asknowledge that and needs to be redefined imo
18:25:45 <plowsof> sgp_ had intended for the btcpayserver plugin to be on the MAGIC repo but : https://libera.monerologs.net/monero-community/20250227#c502452
18:25:52 <m-relay> <r​ucknium:monero.social> A little relevant: Siren and Stnby  have submitted a funding proposal for further Metronero development to the MAGIC Monero Fund: https://github.com/MAGICGrants/Monero-Fund/issues/41
18:26:08 <m-relay> <r​ucknium:monero.social> Metronero is a "BTCPayServer alternative using MoneroPay."
18:26:17 <plowsof> thanks for sharing Rucknium , relevant 
18:26:28 <m-relay> <r​ucknium:monero.social> I'm not longer on the committee, so I don't know if it will get approved or not. But it probably will
18:26:56 <m-relay> <s​pirobel:kernal.eu> I want to mention, that the first milestone of my proposal is also relevant
18:27:16 <m-relay> <s​pirobel:kernal.eu> similar feature set, but different goals / target audiences
18:27:23 <ofrnxmr> "During our work on open bounties and 2 for the Monero community, we identified the need to realign our efforts on the plugin migration to ensure continued support for Monero within BTCPay Server."
18:27:45 <plowsof> i do not agree that "Multiwallet support: This is a critical feature that aligns monero with the rest of the BTCPay ecosystem." - FCMP++ .. quantum resistance.. would be critical.  don;t tell me that "merchants like Cake Pay, Concords, Shopinbit, and many more." will cease to exist if multi wallet support isn't added 
18:28:27 <plowsof> bitcart.io has multi wallet support / easier to setup imo than btcpayserver , where are the third party hosters pushing monero? (for free)? marketing issue? 
18:29:02 <plowsof> Metronero adds a (at least from what i remember) method of third party hosting with a fee model 
18:30:56 <plowsof> will the repo be on monero-project repo? Deverick should be drumming up support for his own proposal as per rules and pushing this along 
18:31:13 <plowsof> and napoly 
18:31:48 <ofrnxmr> theyre instead just playing the drum of "the world will end if we dont use lws with remote nodes oxymoron" 
18:32:27 <m-relay> <s​gp_:monero.social> I'm talking with deverick about options to maintain this going forward. I think this CCS can be tabled until further notice, imo
18:33:11 <plowsof> but 8 people thumbed it up and 1 down this is typical CCS conspiracy 
18:33:52 <m-relay> <s​gp_:monero.social> LWS support will mostly benefit btcpayserver hosting companies, so I want to work with deverick/napoly to reach out to these companies with a proposal and have them cover the majority/all of the costs. At least as Plan A
18:34:47 <m-relay> <s​pirobel:kernal.eu> plan B is normal CCS?
18:35:05 <plowsof> sgp_ thank you for drumming up support for their proposal 
18:35:09 <m-relay> <s​gp_:monero.social> No, that's probably plan F
18:35:20 <m-relay> <s​gp_:monero.social> Again, just my opinion
18:35:48 <plowsof> i agree with it 
18:36:24 <m-relay> <s​pirobel:kernal.eu> we all agree nice
18:36:29 <plowsof> +1 for Metronero Siren Stnby 
18:36:34 <m-relay> <r​ucknium:monero.social> Did they say how exactly they intend to enable multi-wallet support?
18:36:44 <m-relay> <s​pirobel:kernal.eu> also +1
18:36:52 <m-relay> <s​pirobel:kernal.eu> by using lws
18:37:37 <m-relay> <s​gp_:monero.social> Metronero proposal for MAGIC Grants uses one wallet seed only for their multiple stores feature
18:37:40 <m-relay> <s​gp_:monero.social> It's shared
18:38:03 <plowsof> benefit being a fee model for the hosting company , or, open source self host right?
18:39:06 <plowsof> bitcart.ai / mrnaif uses some Rust magic for third party hosting of multiple monero wallets 
18:39:06 <ofrnxmr> +1 for metronero
18:40:11 <plowsof> we can move on i thinks? thanks for the feedback
18:40:33 <ofrnxmr> Yes, but also on metronero, it uses moneropay 
18:40:51 <ofrnxmr> And includes further development on moneropay
18:41:12 <m-relay> <r​ucknium:monero.social> It makes sense to me that this proposal should revise its scope and cost once NicolasDorier finished the 2.1 plugin. So that the proposers know what architecture they would be building on top of.
18:42:12 <plowsof> will make sure Deverick napoly see this meeting log , thank you 
18:42:15 <plowsof>   c. [Initial commit of MoneroKon 2025 CCS proposal](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/554)    
18:42:49 <ofrnxmr> they made a profit last yr, i dont understand why they need ccs this year?
18:43:04 <ofrnxmr> + a 10% buffer even tho theyre going to market sell it into a stablecoin
18:43:06 <plowsof> there was an issue with the front end UI of the Safe wallet, but hbs and fancisscom clarified "funds are safe, the only issue is that Safe hasn't restored the UI to interact with the multi sig safe on polygon yet, so any interaction would require direct smart contract calls, doable but not ideal" 
18:43:34 <m-relay> <s​gp_:monero.social> I read it as basically them needing a loan to cover the initial costs
18:43:43 <ofrnxmr> Are they repaying it?
18:44:09 <m-relay> <s​gp_:monero.social> Not in this case, though arguably them continuing to invest in the community event is reasonable (imo)
18:44:12 <ofrnxmr> I read it like that too, but i dont see anything about where the surplus goes 
18:44:24 <plowsof> the smiles on attendees faces shall be payment in full 
18:44:37 <m-relay> <s​tnby:kernal.eu> Thanks for bringing our toy up
18:45:12 <m-relay> <h​bs:matrix.org> The surplus, if any, will be used to finance future editions of MoneroKon
18:45:59 <plowsof> do note that the general fund has a history of contributing to monerokon proposals 
18:46:08 <m-relay> <s​gp_:monero.social> Ideally you should aim to have a surplus to avoid this next year. I'm not against this proposal if the goal is still sustainability
18:46:25 <nioc> They are not selling all to stable coin and the 10% volatility has already beeb
18:46:28 <ofrnxmr> hbs, how about using surplus up to the amount of the ccs, used to improve this years experience 
18:46:42 <nioc> Already been hit
18:47:37 <ofrnxmr> Niocat, xmr is 220
18:48:13 <nioc> Was 235 wen proposal was made
18:48:21 <ofrnxmr> It was priced at 223
18:48:22 <m-relay> <h​bs:matrix.org> it was decided to go with a CCS because we have not filled all sponsors slots, so CCS is seen as a way to ensure the event can take place
18:49:15 <ofrnxmr> nvm 223 eur
18:49:53 <m-relay> <h​bs:matrix.org> as specified in the proposal, we will seek a new venue for future editions to reduce the total budget, so if things go as planned we should not require a CCS in the future
18:50:51 <ofrnxmr> i think the 223 includes 10% buffer, @hbs?
18:52:04 <m-relay> <h​bs:matrix.org> the exchange rate used was the EMA50, we divided 20k by that rate then added the 10% to the number of XMR
18:52:22 <m-relay> <h​bs:matrix.org> leading to 99
18:52:44 <ofrnxmr> 223 does include the 10%
18:53:03 <ofrnxmr> So ~200eur + 10% 
18:53:16 <ofrnxmr> 223*99=22k
18:54:47 <plowsof> maths are confusing, we can confirm the amounts shortly sirs 
18:55:31 <plowsof> thanks for the feedback so far, i think we can move on 
18:55:35 <plowsof>   d. [Monero Browser Wallet](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/555)    
18:56:07 <plowsof> spirobel there has been some feedback that mentioned the amount , but you clarified that it is a bargain 
18:57:50 <ofrnxmr> I'm doing math backwards, sorry plow. Real rate is 202eur/xmr (209usd/xmr)
18:57:53 <m-relay> <s​pirobel:kernal.eu> lets go through the deliverables there was also some critique that mentioned it should be split up, but I disagree with that
18:57:55 <m-relay> <s​pirobel:kernal.eu> it should not be split up
18:58:48 <plowsof> ok thanks for confirming, this is your proposal, as is - no changes required 
18:59:04 <m-relay> <r​ucknium:monero.social> > Currently Monero shoppers have to copy and paste addresses from the tor browser into their wallets. This can be made more convenient and secure by a browser wallet.
18:59:42 <m-relay> <s​gp_:monero.social> No qr codes?
18:59:48 <m-relay> <r​ucknium:monero.social> But the Tor Project discourages installing extensions in the Tor Browser https://tb-manual.torproject.org/plugins/
18:59:48 <m-relay> <r​ucknium:monero.social> > However, the only add-ons that have been tested for use with Tor Browser are those included by default. Installing any other browser add-ons may break functionality in Tor Browser or cause more serious problems that affect your privacy and security. It is strongly discouraged to install additional add-ons, and the Tor Project will not offer support for these configurations.
18:59:48 <ofrnxmr> Or uris?
18:59:50 <plowsof> open in wallet button href="monero:"
19:00:24 <m-relay> <s​pirobel:kernal.eu> yes for good reason
19:01:26 <m-relay> <s​pirobel:kernal.eu> you mean deeplinks right? It means that often when you click an x.link on a mobile browser suddenly the x app opens
19:01:39 <m-relay> <s​gp_:monero.social> Danger: You should never install any additional extensions on Tor Browser or edit about:config settings, including the ones we suggest for Firefox. Browser extensions and non-standard settings make you stand out from others on the Tor network, thus making your browser easier to fingerprint.
19:01:40 <m-relay> <s​gp_:monero.social> https://www.privacyguides.org/en/tor/
19:02:08 <m-relay> <s​pirobel:kernal.eu> yeah very good point. Most random extensions shouldnt be installed.
19:02:18 <m-relay> <s​pirobel:kernal.eu> but this is an exception
19:02:55 <m-relay> <s​pirobel:kernal.eu> anyway lets go through the deliverables and address this first
19:03:57 <m-relay> <s​gp_:monero.social> I just wanted to note the goal of an extension with Tor browser is fundamentally incompatible. Extensions can be used in other cases
19:04:32 <m-relay> <s​pirobel:kernal.eu> blanket statement
19:05:56 <plowsof> as we're over the hour we have to touch on the other proposals, thank you for the feedback so far and apologies 
19:06:17 <m-relay> <s​pirobel:kernal.eu> yeah its 3am here
19:06:25 <plowsof> thank you for attending 
19:06:32 <plowsof>   e. [Walletverse monero integration](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/556)    
19:06:58 <plowsof> has recently been rejected by MAGIC, so we can skip this one for now as we're over time but open for feedback none the less
19:07:10 <plowsof>   f. [acx Monfluo maintenance and further development (3 months)](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/557)    
19:07:33 <plowsof> low asking amount of 14 xmr to add features to a MySu fork 
19:07:52 <plowsof>   g. [Revuo Monero Maintenance (2025 Q2)](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/559)    
19:08:13 <plowsof>   h. [plowsof CCS Coordinator](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/560)   
19:08:37 <ofrnxmr> +1 acx, revuo and plowsof dont start til april so no big rush. But +1 plowsof 
19:08:39 <m-relay> <s​iren:kernal.eu> I see value in a browser wallet from an UI/UX perspective. Especially if it improves the multisig experience.
19:09:15 <m-relay> <s​pirobel:kernal.eu> https://matrix.monero.social/_matrix/media/v1/download/kernal.eu/ywzqHFIZQgFMupWQtVhGWuQo
19:09:17 <ofrnxmr> Multisig is changing wirh fcmp
19:09:33 <plowsof> thank you for the feedback and updoots on mine and other proposals :) 
19:09:45 <m-relay> <s​pirobel:kernal.eu> tor browser has no script pre installed. It is not as black and white
19:09:47 <plowsof> v1do has been up for funding for some time 
19:10:13 <ofrnxmr> Yeah, i'm not against merging em
19:10:44 <ofrnxmr> Payouts for those dont come til end of April or-so, but no harm in getting a head start
19:11:16 <ofrnxmr> Well, luigi has been taking 4 weeks to do payouts, so payouts will come end of may :D
19:12:28 <ofrnxmr> (i'm voting merge acx and plow)
19:12:45 <m-relay> <s​pirobel:kernal.eu> alright good night everyone. If you have any questions about the browser wallet, library, etc abstract or concrete. pls ask 🙏
19:13:23 <ofrnxmr> Spirobel, you recently closed out (successfully) the previous ccs, right?
19:13:40 <plowsof> good night thanks for joining . and all who have attended. yes spirobels prev porposal has been paid out and completed 
19:13:41 <m-relay> <s​pirobel:kernal.eu> yes. It was the preliminary work for all of this
19:14:33 <v1docq47[x]> as an option, im considering a reduction in the amount
19:14:40 <plowsof> kewbits proposal has been terminated i am delighted to share 
19:14:50 <v1docq47[x]> funding is going very hard...
19:15:19 <plowsof> v1docq47 there are also approx 1~xmr available from your previous proposals (overfunding) which is also another option to help 
19:16:41 <ofrnxmr> V1d
19:16:47 <v1docq47[x]> lets see for another month, then ill think about it 
19:16:53 <ofrnxmr> You have some overpayment from previous ccs'
19:17:16 <ofrnxmr> So we can probably vote to apply the funds if the fundraising is unsuccessful 
19:17:36 <ofrnxmr> Plowsof. 1xmr or 10?
19:17:38 <plowsof> it would be a shame to see this happen as v1do has been completing ccs proposals for years 
19:17:42 <plowsof> closer to 1 
19:17:49 <v1docq47[x]> i wouldnt want to have to resort to that 
19:18:28 <plowsof> ofrnxmr closer to 10***** yes https://github.com/plowsof/scrape_ccs_fr/tree/ccs1
19:18:45 <plowsof> apologies. 10 is substantial 
19:18:45 <v1docq47[x]> theres still 3 months of work ahead, so theres no rush :)
19:20:06 <plowsof> thanks for joining us and good luck with funding
19:20:24 <plowsof> i think we can end the meeting here, thanks all for attending 
19:20:24 <v1docq47[x]> tnx
19:20:26 <ofrnxmr> you can still request payouts before funding is completed, if needed (according to the rules)
19:20:56 <plowsof> currently this is not preferred 
19:21:14 <ofrnxmr> Rule 6 "Your work on the project can begin before the proposal is fully funded, and milestones may (at times) be paid out before the proposal is fully funded."
19:21:18 <v1docq47[x]> luigi said he wanted to wait until the proposal was fully funded
19:23:10 <plowsof> we'll have to yell at him, getting overfunded amounts approved is a positive step 
19:23:12 <ofrnxmr> ofc you cant request funds that havent been donated, but i dont think it hurts anything to request funds that have been
19:23:36 <ofrnxmr> Yeah. We can give it another 4 weeks if v1d is ok with that
19:23:56 <v1docq47[x]> i wrote to him a month ago about the payment for dec+jan
19:24:21 <ofrnxmr> did you post request on the proposal?
19:24:56 <ofrnxmr> A month ago a lot of ppl requested payouts and it took him a month to pay them. So dont worry, he's just on a boat right now
19:26:07 <v1docq47[x]> yup, i wrote him and plowsof after the two month works report
20:10:12 <m-relay> <b​oog900:monero.social> yeah I think that was a wallet thing
20:11:15 <plowsof> I will make my false memory true soon, thanks boog900
20:11:18 <m-relay> <b​oog900:monero.social> The 4hr sync was bottlenecked by bandwidth, the 1hr 50m sync was on a server with a lot of bandwidth
20:17:41 <m-relay> <b​oog900:monero.social> IMHO trying to fix monerod's inefficiencies is not going to be an easy task, just look at 9135. I don't think there are going to be many low hanging fruits like our sync mode was.
20:19:42 <m-relay> <b​oog900:monero.social> also Cuprate always beat monerod at syncing it was just the first 100,000 blocks that monerod got ahead.
20:23:02 <m-relay> <b​oog900:monero.social> I would much prefer work be done on stuff like improving the p2p tx relay, which would help both cuprate & monerod.
20:41:49 <m-relay> <o​frnxmr:xmr.mx> The charts posted show a slowdown around the rx height?
20:48:04 <m-relay> <b​oog900:monero.social> It's fast sync so no RX hashes/VMs. The slow down is writing the blocks to the DB. I think because it's more smaller bits of data (more txs, outputs) rather than the large chunks of early RCT data (huge tx proofs). I do think improvements would be possible here but at this time it's not really worth it, bandwidth will probably be the limiting factor for most users.
20:49:12 <m-relay> <b​oog900:monero.social> we synced the first 3,000,000 blocks in 1 hour, the other ~300,000 was the 50 mins after.
21:00:23 <m-relay> <o​frnxmr:xmr.mx> So about 10hrs for a full sync
21:00:26 <m-relay> <o​frnxmr:xmr.mx> (Verifying)
21:04:52 <m-relay> <b​oog900:monero.social> 16 is the best we got, currently full syncing on that sever that got the ~ 2hr sync now
21:06:18 <m-relay> <3​21bob321:monero.social> the reason why they dont want you to install extensions on tor is for browser finger printing reasons
21:13:03 <m-relay> <s​pirobel:kernal.eu> https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/555#note_28974 Rucknium  sgp_ I wrote a comment about some of the issues with  QR-Codes and Deeplinks. But I really hope the discussion is not reduced to this. There is so much excitement and potential in browser wallets. Say what you want about eth. But the web3.js library in conjunction with the development<clipped message>
21:13:04 <m-relay> <s​pirobel:kernal.eu>  of metamask led to a lot of rapid innovation. It is not just about Extension. See the bigger picture of making things more modular.
21:14:12 <m-relay> <s​pirobel:kernal.eu> yes and the extensions could also mix up circuits which would be bad. But we are going to be careful. And make sure that this does not happen. A monero browser wallet extension has to be noscript tier.
21:15:06 <m-relay> <s​pirobel:kernal.eu> and the next step after that is monerochan browser in any case. But we need to go down the path of the browser extension first. Because it drives the development of the library
21:17:54 <m-relay> <s​pirobel:kernal.eu> https://repo.getmonero.org/monero-project/ccs-proposals/-/merge\_requests/555#note\_28974 Rucknium  sgp_ I wrote a comment about some of the issues with  QR-Codes and Deeplinks. But I really hope the discussion is not reduced to this. There is so much excitement and potential in browser wallets. Say what you want about eth. But the web3.js library in conjunction with the developme<clipped message>
21:17:54 <m-relay> <s​pirobel:kernal.eu> nt of metamask led to a lot of rapid innovation. It is not just about the Extension. See the bigger picture of making things more modular.
22:55:51 <m-relay> <s​iren:kernal.eu> If anyone wants to share their workflows as a merchant, has questions or complaints about Metronero please join the public Q&A on Thursday 2025-03-06 17:00 UTC https://github.com/MAGICGrants/Monero-Fund/issues/41#issuecomment-2692453872
22:59:04 <m-relay> <s​iren:kernal.eu> Yes you! The anime commission artist and electronic roulette table operator.