Monero Community Workgroup Meeting: February 1st 16:00 UTC

[plowsof]

Location: Libera.chat, #monero-community | Matrix

Instructions for joining the monero.social Matrix server.

Time
16:00 UTC Check your timezone

Moderator: plowsof

Please reach out in advance of the meeting if you would like to propose an agenda item.

Proposed Meeting Items:

1. Introduction
2. Greetings
3. Community highlights
   • Cuprate 2025 roadmap
     News: Monero Observer - Revuo Monero
4. CCS updates
   a. XMRChat - a service for content creators to receive messages and tips in Monero.
   b. NoShore: Groundwork for on-the-go offline payments
   c. dmvp2p: Donate Monero Via P2Pool
   d. Funding Proposal for Unstoppable Wallet: Enabling Native Monero Integration on iOS & Android
   e. Revuo Monero Maintenance (2025 Q1)
   f. Btcpayserver plugin
   g. Add jeffro256 full time dev 2025Q1
   h. SNeedlewoods-02_part-time dev work
   i. New Year's Resolutions
5. Workgroup reports
   a. Dev workgroup
   b. Localization workgroup
   c. Outreach workgroup
   d. Events workgroup - MoneroKon 2025
   e. Website workgroup
   f. Policy workgroup
   g. Research workgroup
   h. Seraphis Migration workgroup
6. Open ideas time
7. Confirm next meeting date/time

Previous meeting including logs

Meeting logs will be posted here afterwards.

[plowsof]

Logs

< plowsof > v1do has been up for funding for 53 days. achieving loose consensus takes time also. Netriks coordinator ccs proposal will have no applicable proposal in sight for repurposing (on account of translation proposals not allowed on the CCS

< plowsof > ofrnxmr "we shouldnt be reducing ccs amounts when we repurpose "Reducing the requested amount from 45.6 -> 30.6". We should instead be donating the xmr to the ccs" Currently not possible as it would require a tweak to the back end. This is why the amount is reduced manually and a note attatched, as is the plan for XMRChat. The CCS maintainer is

< plowsof > fine with this at the moment.

< o​frnxmr:xmr.mx > I thought it went to funding in jan?

< o​frnxmr:xmr.mx > It doesnt require a tweak, just required luigi to send the funds

< p​lowsof:matrix.org > the first payment is due 31st December (the confusing part)

< p​lowsof:matrix.org > it was merged on the 10th December https://repo.getmonero.org/monero-project/ccs-proposals/-/commits/master/v1docq47-monerotopia-2024-voiceovers-and-working-on-xmr.ru.md

< p​lowsof:matrix.org > just putting it up now for discussion

< o​frnxmr:xmr.mx > attaching a note is a poor way to do accounting

< o​frnxmr:xmr.mx > All funds should be accounted for in the ccs totals and milestones, not in comments and descriptions

< p​lowsof:matrix.org > i consider it to be acceptable enough , and so does the maintainer. the alternative being self sending from a cold wallet

< o​frnxmr:xmr.mx > xmrchat, v1d etc should not appear on the funding page as worth less than they are

< o​frnxmr:xmr.mx > Doesnt req a backend change. Just requires luigi to send 15xmr to v1ds ccs

< o​frnxmr:xmr.mx > Or from the spend wallet. Doesnt really make a different

< o​frnxmr:xmr.mx > if the funds are literally in the GF, then its still no diff, as the funds need to come out of the GF to pay v1d

< o​frnxmr:xmr.mx > By this, i'm referring to the progress bar for funding. 30/45xmr shouldnt show as 15/30. The ccs is 45 xmr, not 30

< o​frnxmr:xmr.mx > Better the funds come out now, than v1d claim the funds and later we are wondering if the funds were ever send from GF

< p​lowsof:matrix.org > currently "Note: 15XMR has been awarded to v1docq47 after closure of Netriks translation coordinator proposal" , this can be changed to make the original total clear

< p​lowsof:matrix.org > there are more funds to be sent from the general fund - likely in a batch rather than individually (eventually)

< p​lowsof:matrix.org > or even the title of the proposal can include the original amount 🤷

< o​frnxmr:xmr.mx > My point is, is we simply lower the amount on paper (not on chain), then the funds are still in GF

< o​frnxmr:xmr.mx > When paying v1d, where are the funds coming from? Ccs wallet. Ccs wallet doesnt have the funds tho?

< o​frnxmr:xmr.mx > The logical solution to any of this is to physically send the donation and call it a day

< o​frnxmr:xmr.mx > No messy paper tracking, no need to chase down transparency reports or find out where the money is

< o​frnxmr:xmr.mx > Everything is done 1 time and problem solved.

< p​lowsof:matrix.org > i also changed the bigger re-purposing proposal https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/537

< p​lowsof:matrix.org > simply " will be repurposed or reallocated to similar proposals (subject to community consensus)."

< o​frnxmr:xmr.mx > Literally "hey bf, send 15xmr to this proposal. Thx"

< o​frnxmr:xmr.mx > Donr

< o​frnxmr:xmr.mx > > whales (probably) wont be funding things forever. Generalfund is unreliable. The jetfund should be there for us on a bad day, not be empty when we have that day. That was im intent everytime ive discussed jetfund. Not convenience, but necessity.

< o​frnxmr:xmr.mx > > finishing / build upon another ccs (tipxmr -> xmrchat) is different than a repurpose

< o​frnxmr:xmr.mx > I disagree with the part about trying to maintain a 0 balance

< o​frnxmr:xmr.mx > This means its first come, first serve, and leaves us (community)bnothing to fall back on for a rainy day

< o​frnxmr:xmr.mx > (we have GF, which proved useless for a lot of people during out last rainy day event)

< o​frnxmr:xmr.mx > Literally got bailed out by our 🐳 buddy

< o​frnxmr:xmr.mx > if repurposing 15xmr to a 45 xmr ccs, should the funding page should show as:

< o​frnxmr:xmr.mx > A) 0/30xmr (+ a note in description about the 15xmr)

< o​frnxmr:xmr.mx > B) 15/45xmr (funds physically sent to the new ccs)

< o​frnxmr:xmr.mx > imo:

< o​frnxmr:xmr.mx > pros - a) initially easier for wallet holder (dont have to do anything, so ofc maintainer is OK with it), makes ccs appear less costly to casual observer b) accurate display of cost, better accounting (accurate totals and milestones), bonus: if funds are in GF (most purgatory ccs are in GF) then we paying proposers using funds that dont belong to them (we payout from ccs wallet bu

< o​frnxmr:xmr.mx > t the funds being repurposed are actually in GF. They need to be moved. Better to move them directly to the proposal than to just mark it on a comment and hope its paid before milestones are collected)

< o​frnxmr:xmr.mx > cons - a) gives false impression about value. Requires more work to track b) requires making a transaction

< s​yntheticbird:monero.social > I just realized something

< s​yntheticbird:monero.social > We are calling CCS proposals, the proposal to be approved into CCS.

< s​yntheticbird:monero.social > then we are funding CCS proposals

< s​yntheticbird:monero.social > then CCS proposals are being worked on

< s​yntheticbird:monero.social > then CCS proposals are finished

< s​yntheticbird:monero.social > PROPOSAL SHOULD STOP AT THE FUNDING STAGE

< plowsof > it has become sentient

< s​yntheticbird:monero.social > plowsof what would you call a "CCS Proposal" pass the idea stage? CCS contract?

< o​frnxmr:xmr.mx > CCS funding required**

< nioc > has anyone seen my bike?

< s​yntheticbird:monero.social > lol

< o​frnxmr:xmr.mx > After fundind required CCS WIP, then Completed CCS

< s​yntheticbird:monero.social > alright I'll just call these "CCS items"

< o​frnxmr:xmr.mx > for v1d, there is also the funds from his own overages

< nioc > I thought we were talking about the overages

< plowsof > overages not involved in this https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/542

< plowsof > giving netrik the boot (sorry)

< o​frnxmr:xmr.mx > Its also not netriks fault that TL workgroup is dead

< o​frnxmr:xmr.mx > And it might be alived again when new site comes on

< plowsof > ofrnxmr the cons can be addressed with notes or Notes or NOTES or for extreme visibility, amounts in the title so donors can clearly see. and the original quoted amount is written in the proposal

< plowsof > you are underestimating the extreme opsec measures , and risks required to just send a transaction

< plowsof > life and death, the maintainer is not going to addd any extra risks, nor is the GF custodian

< plowsof > netrik was already being replaced michael... michaelizer? by erciccione, he was invoilved in some controversy regarding poor translations already so not happening

< plowsof > and irrc there was a few voices from community suggesting there not to be "1 coordinator" of translations, that each language should have a leader of sorts

< o​frnxmr:xmr.mx > why are calling them "maintainer" and "custodian"

< o​frnxmr:xmr.mx > Luigi sends funds every couple weeks. Bf wakes up the GF a few times a year

< o​frnxmr:xmr.mx > We'll know from the transparency report how often the GF is woken up to pay for infra + donations.

< o​frnxmr:xmr.mx > theres 0 rush. He can send the 15 xmr the next time he wakes GF up

< o​frnxmr:xmr.mx > And AGAIN, if the actual fund are in the GF, then they HAVE to be sent from GF sooner or later

< plowsof > yes, later, in a batch when necessary

< o​frnxmr:xmr.mx > is this later before or after v1d collects his MS?

< plowsof > i could only guess

< o​frnxmr:xmr.mx > If after, then v1d is collecting someone elses funds

< o​frnxmr:xmr.mx > Theres no reason bf cant send 500xmr today / next time he unlocks the wallet, and luigi donate directly to repurposed ccs when he does payouts and merges

< plowsof > better to focus on things we control

< o​frnxmr:xmr.mx > We should control the jetfund

< o​frnxmr:xmr.mx > thats like, literally the point of it

< plowsof > the current repurposing amounts which need to be sent to the CCS at some point are noted here https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/503#note_27312

< o​frnxmr:xmr.mx > Were those actually paid out?

< o​frnxmr:xmr.mx > Monero Outreach round 3

< o​frnxmr:xmr.mx > 36.68 xmr repurposed

< o​frnxmr:xmr.mx > as an example ^ This was repurposed but not claimed yet, right?

< plowsof > correct

< o​frnxmr:xmr.mx > brb need to finishe these dishes in 3 mins

< plowsof > geonic has not claimed it yet (although appears to be completed)

< plowsof > surely there isn't a meeting beginning right now

< plowsof > #1149

< plowsof > Meeting time, greetings! 😬

< plowsof > a new release is on the horizon, selsta made the final checklist here monero-project/monero#9758

< plowsof > if anyone would like to build the release branch (and also pull in 9740 and 9759 that would help them out) i've done so with 3 nodes

< o​frnxmr:xmr.mx > Hopefully 1 more pr gets added to that list 0xfffc ! Lol

< s​yntheticbird:monero.social > greetings gentlemen

< plowsof > syntheticbird : i hear cuprate is a daemon that is syncing blocks?

< r​4v3r23:monero.social > sup

< plowsof > hello r4v3r23, thanks for joining

< ofrnxmr > Greetings from the other side

< s​needlewoods:monero.social > hey

< plowsof > 👋

< ofrnxmr > Hello mr needlewoods

< ofrnxmr > Gm r4v3r

< plowsof > to follow cuprate / cuprated progress, please join the #cuprate channel , theyve been syncing the entire chain faster than release monerod (in full verification and fast sync mode) , their roadmap which is under discussion if interested Cuprate/cuprate#376

< ofrnxmr > -dev should dive into why cuprate is faster than monerod

< r​ucknium:monero.social > plowsof suggested I give an update on my OSPEAD CCS: https://ccs.getmonero.org/proposals/Rucknium-OSPEAD-Fortifying-Monero-Against-Statistical-Attack.html

< r​ucknium:monero.social > Like I said last meeting (I think), I submitted Milestone 2 last month. I plan to publicly post all OSPEAD-related documents and code on about February 20.

< plowsof > thanks Rucknium!

< r​ucknium:monero.social > Since Milestone 2, I learned a bit of Rust and ported a short but time-consuming piece of the OSPEAD R code to Rust.

< r​ucknium:monero.social > I achieved a 15x speedup over the R code. This bit of code consumed about half of the times of the whole procedure that used to take two weeks on a powerful machine.

< plowsof > 😮

< r​ucknium:monero.social > Special thanks to Synbhebird (Crodyceps infected 🍄☣️) for critiquing my novice Rust code.

< r​4v3r23:monero.social > re: ANONERO - first version (milestone 2) will be ready in a few weeks

< plowsof > thanks syntheticbird!

< r​4v3r23:monero.social > aiming for end of feb

< plowsof > r4v3r23 sounds great, have there been any surprises along the way?

< r​4v3r23:monero.social > yes, we had some delays on dev side which i didnt expect

< r​4v3r23:monero.social > and i underestimated the amount of time/work needed

< r​4v3r23:monero.social > kotlin and jetpack compose isnt as quick and easy as flutter

< plowsof > thanks for the insight, glad you are pushing forward still

< plowsof > valldrac had contacted me 2~ days ago to share progress on his next milestone (CI / Test related) and feels the 1st July deadline is more than enough.

< plowsof > anhdres / monero gardens repo is active (even had an organic shoutout today)

< o​frnxmr:xmr.mx > napoly

< 0​xfffc:monero.social > 🫡😭

< plowsof > News: Monero Observer - Revuo Monero

< plowsof > we can jump into the ideas if nothing else at hand to discuss?

< o​frnxmr:xmr.mx > add moneronews.net (joking)

< plowsof > ofrnxmr has also completed several milestones recently with basicswapdex and his personal proposal 💪

< o​frnxmr:xmr.mx > ya, lets go

< vThor > Hi together. Giving some sign of live from me :)

< plowsof > 👋

< plowsof > can jump into the ideas, some will likely be deferred to no wallet left behind but brought up none the less

< plowsof > a. XMRChat - a service for content creators to receive messages and tips in Monero.

< plowsof > FiatDemise has confirmed that the self hosted version is now working, and successfully sent a tip to their instance. thye've added coin swaps (via trocador) which requires an api key for self hosted instances.

< ofrnxmr > Xmrchat was used on some biger stream the other day and pulled in >100$

< s​yntheticbird:monero.social > sry for the big delay,

< s​yntheticbird:monero.social > plowsof: indeed, alpha is coming soon

< s​yntheticbird:monero.social > Rucknium: np

< s​yntheticbird:monero.social > ofrnxmr: They are busy enough and Im sorry to think they cannot reproduce such improvements because of the complexity of C++. Cuprate have a very complex architecture when you remove the crates layer.

< ofrnxmr > We accept the challenge

< plowsof > Rucknium suggested the retro payments cover exactly 70.56, and this change was made

< o​frnxmr:xmr.mx > 🤺

< plowsof > so this would be merged at the same time tipxmr is put to funding https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/530

< ofrnxmr > Yea, to go back to premeeting suggestion, i dont like that the 70 was removed grom the total. It should be included in the total and donated to the proposal at the time of merger

< plowsof > a note at the top should be added to help clarify the funding situation https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/524#note_28356

< ofrnxmr > I just think its adding complexity to a simply task. I dont know where tip funds are (gf or ccs) but if jn ccs, its even easier

< ofrnxmr > If in GF, save the note for a DM to BF for refund

< ofrnxmr > The funds shouldnt (but technically can) be paid paid to from ccs wallet, if the funds are in GF

< plowsof > other than that, the self hosted version "works" and presumably should be merged to funding

< ofrnxmr > I think so. Payouts dont have to be immediate, if more verification is needed

< plowsof > seems we can move on to the next?

< ofrnxmr > 👍

< plowsof > b. NoShore: Groundwork for on-the-go offline payments

< plowsof > i had invited the proposer to this room (they where not in) after the previous community meeting

< plowsof > it has been open since 11th December

< ofrnxmr > also invited on the proposal itself

< plowsof > enough time to reach a conclusion, or show something to extend it

< ofrnxmr > I think this is a close.. reopen if they reappear with am update or addressing some feedback or smthn.

< ofrnxmr > But its been nacked and deferred for a while and no feedback this year

< plowsof > i support closure on this one, lack of a buzz around it

< plowsof > we can move on?

< plowsof > actually vthor's work shuld be beneficial to this proposal eventually.

< plowsof > or could be

< ofrnxmr > otslib documentation is boomin

< plowsof > lol

< a​nhdres:matrix.org > Thanks for the ping I didn't know! Summer here has been crazy busy. Looking forward to work more on the garden soon

< plowsof > Offline Transaction Signing library :)

< r​4v3r23:monero.social > whats that

< plowsof > vthorksksksksk

< ofrnxmr > Xmrsigner

< vThor > Think it is another place of construction, full disclosure I was exited to talk with fullmetal science before CCS, and when I finish my CCS it is one thing I want to dedicate my time with to get a protocol up because I think its on of the upmost important features.

< plowsof > also proposal link https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/495

< plowsof > so a closure and open invitation to return for NoShore

< r​4v3r23:monero.social > @vthor can you send me relevant info

< vThor > in that threat are also the most conversation about it

< r​4v3r23:monero.social > if offline signing apps need to make any changes

< vThor > No, there will be no need, at least for version 1

< vThor > It will serve exact the same workflow and work as drop in replacement, only for a developer it should be as easy as possible to archive an offline signer.

< plowsof > everoddandeven also made a stand alone monero lws library of sorts

< plowsof > @ woodser/monero-java#117 could be interesting for you both

< plowsof > sorry, not monero-lws, but related

< plowsof > i think we can move on?

< vThor > r4v3r23 https://otslib.monerodevs.org/sdk/ots/reference/ https://github.com/DiosDelRayo/monero-docs/tree/ots

< ofrnxmr > Yea

< plowsof > c. dmvp2p: Donate Monero Via P2Pool

< plowsof > after the last meeting, i went ahead and made sure to install dmvp2p. 4rkal was correct that its 'simple' (current version requires you to point it to xmrig /p2pool binaries and such. but it simple, and small (less than 20~MB)

< plowsof > i still feel this could be implemented into gupaxx .. a lite mode of gupaxx of sorts

< ofrnxmr > I think value propor a stanalone app to dust accoints requiring primary addresses, isnt there. As a gupaxx plugin, maybe. Echoing myself

< plowsof > proposal created on 23rd December, does not look to have enough positive merge sentiment.

< vThor > r4v3r23: Sorry was the wrong link, https://github.com/DiosDelRayo/monero/tree/otslib/ots this is the source, I'm not yet awake.

< plowsof > looks to be a closure.

< ofrnxmr > if no changes made by next meeting, i'd say close

< plowsof > moving on then

< plowsof > d. Funding Proposal for Unstoppable Wallet: Enabling Native Monero Integration on iOS & Android

< ofrnxmr > Big nack based on their new funding model that charges $ for privacy

< plowsof > this has still not been acknowledged by the unstoppable wallet team as being real, or any responses in the comments to the serious negative points raised in the comments

< ofrnxmr > Collects data unless you pay them not to

< ofrnxmr > unrelated note: edge wallet (on getmonero) is basically spyware. We should remove that as well

< plowsof > i would also close this before next meeting unless they ..... hm

< ofrnxmr > Unless they stop charging money to opt out of usage statistics. Etc. But they merged those prs despite user feedback

< plowsof > does anyone have comments about UnstoppableWallet ? thefuzzstone has detailed the implications of a subscription based funding model horizontalsystems/unstoppable-wallet-android#7795 (comment)

< plowsof > else we can move on

< ofrnxmr > unstoppable is charging a subscription model for privacy

< ofrnxmr > Tor, usage statistics, duress password

< plowsof > apologies for rushing to cover all ideas, people can drop comments on others out of sync if they wish

< ofrnxmr > The second (usage stats) is an instant close for me

< vThor > :D there was a time I hoped unstoppable wallet implements finally like promised monero, but always something else was then implemented. Result was I dropped unstoppable wallet. Title unstoppable and without monero is a contradiction.

< ofrnxmr > I've had unstoppable installed for 3+ years, and i'll be deleting it.

< vThor > ofrnxmr: interesting to hear that, one reason more to not lose a thought on it. (not that I have a bitter sentiment :D )

< ofrnxmr > Edge is terrible as well. You cant even create wallets unless you are connected to edge

< ofrnxmr > Anyway, i vote close for 2 reasons. Milestone 1 (r&d) and the direction of the software (anti privacy)

< plowsof > lets move on then

< plowsof > e. Revuo Monero Maintenance (2025 Q1)

< plowsof > first payout is already due because of slow to merge and the community are in uproar. this needs to be rectified asap

< plowsof > we can move on. waiting for merge?

< plowsof > dukenukem rottenwheel ^

< plowsof > moving on?

< ofrnxmr > Next

< plowsof > f. Btcpayserver plugin

< plowsof > Napoly has confirmed there are no blockers for this proposal to be merged as is https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/538#note_28439

< ofrnxmr > Napoly recent comment "As far as I know, there is no support from version 2.1 onward"

< ofrnxmr > is directly contradicted by btcpay dev above "As for the BTCPay Server team, our priority is to release version 2.1 with a Monero plugin that works as it does today, minimizing disruptions for our merchants. What happens beyond this is up to you."

< ofrnxmr > https://github.com/btcpayserver/btcpayserver-monero-plugin and the 2.1 plugin is here

< ofrnxmr > I commented this ^ on the ccs and rotten thumb-down'd my comment as if it wasn't fact. Idk why ppl want to play games

< plowsof > sgp commented " I would support an immediate task to document exactly how lws would work with the plugin and if there are any missing features or performance issues. That doesn't need to wait, if Napoli and deverick want to start on that"

< plowsof > 7 up doots and 1 down doot, looks like a clear merge

< plowsof > "wait and see" is very tempting to luigi though

< ofrnxmr > its not a clear merge

< ofrnxmr > The updoots are all from ppl that cant read, no offense

< plowsof > 😮

< ofrnxmr > Sgp understood the ccs properly, and as he said theres nothing to do atm except for document the switch to lws

< ofrnxmr > And wait for the 2.1 plugin

< plowsof > bitcart.ai multi wallet / third party instance is up.. working.. dockerised.. simple , i wonder why its not taken off?

< ofrnxmr > Napoly commented just days ago that there is no monero support for 2.1, showing that his finger isnt on the pulse of his own ccs

< plowsof > (more coins than btcpayserver)

< ofrnxmr > Nicolas commented directly on the ccs that btcpay 2.1 would have monero support out of the gate

< ofrnxmr > As sgp said, whatever comes after that should be the focus. Not redoing the whole thing and pretending like there is no monero support

< ofrnxmr > I say leave open, but nap and deverick need to address the fact that a plugin already exists and adjust ccs to account for that

< plowsof > open for feedback, moving on

< plowsof > g. Add jeffro256 full time dev 2025Q1

< ofrnxmr > Clear merge

< ofrnxmr > Bitcart ai is used by servers.guru btw

< plowsof > thats great, did not know this

< ofrnxmr > Monerokon's new pos app uses moneropay

< plowsof > MrNaif^

< plowsof > working on 🥕implementation , busy bee

< o​frnxmr:xmr.mx > servers.guru @servers.guru:matrix.servers.guru servers.guru @serversguru:matrix.org

< plowsof > h. SNeedlewoods-02_part-time dev work

< s​yntheticbird:monero.social > I say we close jeffro, he deserve a raise

< ofrnxmr > Jeffro picks his own rate

< s​yntheticbird:monero.social > he can come back with 1000% time his salary

< s​yntheticbird:monero.social > ofrnxmr we need to force him towards fortune

< ofrnxmr > I think we havs sneel a 1000% raise on last ccs

< plowsof > no wallet left behind have informally checked sneedlewoods proposal over and no blockers

< ofrnxmr > Gave*

< s​yntheticbird:monero.social > enough trolling

< s​yntheticbird:monero.social > clear merge for sneedlewoods

< ofrnxmr > So its not unheard of!

< ofrnxmr > +1 sneed and +1 jeffroAI

< nioc > I was just thinking jeffroAI :D

< nioc > already gave my thumbs up to both

< plowsof > thanks everyone for the feedback and updates 💪

< plowsof > moving on?

< s​needlewoods:monero.social > thank you

< ofrnxmr > This part tho "M2 (20.6 XMR): PR to replace wallet2 with the Wallet API in simplewallet is merged to monero-project/monero

< ofrnxmr > I estimate this can be completed in ~ 4 months, which makes:

< ofrnxmr > 12 (h/week) * 4.3 (weeks/month) * 4 (months) = 206.4 (h total M2)." I think moneromooo didnt like wallet_api

< ofrnxmr > Or maybe i misread

< ofrnxmr > Just something sneed might want to check with mooo about

< plowsof > rbrunner ^

< plowsof > i. New Year's Resolutions

< plowsof > note that Rucknium, Anhdres, r4v3r23, valldrac have reached out to prove theyre actively working on their proposal (Rucknium has even completed a milestone already)

< plowsof > key aspects here are written @ https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/537#deadline-update-july-1-2025

< plowsof > and the immediate closure proposals at the top " will be repurposed or reallocated to a similar proposal (subject to community consensus)."

< a​nhdres:matrix.org > Got it. From my CCS I have to do the illustrations. That's all I have pending.

< ofrnxmr > -_- msg got dropped

< ofrnxmr > As a WIP and soft guideline, its fine, but as a formal arrangement i think its a bit overly aggressive. I'll make some official suggestions later

< vThor > I'm sorry, I need to leave before the puppy pee on my leg. Only want to say, that I'm not actively read in the channels at the moment (moment is already lasting some time), but you can always ping and I will happily respond. I wish you all a great one! :)

< ofrnxmr > essentially saying we will "fire" someone for being slow (before deadline), when the firing deadline has been set. Regular (acceptable) updates should potentially give breathing room for the deadline, not push the deadline forward

< ofrnxmr > Lets say ccs C is making good progress but doesnt provide updates publicly, and will meet the deadline. Close? No. Lets say the same ccs will not meet the deadline. Close? No.

< ofrnxmr > Closures should only come if we hit the deadline AND progress is not looking good

< ofrnxmr > The top proposals (for immediate closure) k8s, anon, translation*, should be set aside, not paid out immediately to other ccs

< plowsof > there are indeed edge cases. community consensus should handle this.

< ofrnxmr > Especially consider none of these funds are in CCS wallet

< plowsof > If the provided updates or progress (or lack thereof) is unsatisfactory, all remaining funds can be relinquished either before or after the deadline.

< plowsof > Note 'can be' and the consensus for the funds later

< ofrnxmr > Maybe that list should be "how much to get BF to transfer to the jetfund so that they can be repurposed"

< plowsof > immediate closures "All remaining funds will be repurposed or reallocated to a similar proposal (subject to community consensus)."

< ofrnxmr > (the immediate list)

< ofrnxmr > They have to be moved out of GF before we can do anything with em

< ofrnxmr > So that should be a formal req for BF to send 197.94014XMR to CCS jetfund wallet

< ofrnxmr > + tipxmr

< ofrnxmr > Are we really 30mins over 👀

< plowsof > can end the meeting here, thanks all for attending 😃

Automated by this