mooo-2020-12.md

 ---
-layout: wip
+layout: cp
 title: "moneromooo: three months from December 2020"
 author: moneromooo
 date: 05 December 2020
@@ -7,16 +7,21 @@ amount: 225
 milestones:
   - name: first month
     funds: 33.33% (75 XMR)
-    done:
-    status: unfinished
+    done: 1 January 2021
+    status: finished
   - name: second month
     funds: 33.33% (75 XMR)
-    done:
-    status: unfinished
+    done: 1 February 2021
+    status: finished
   - name: third month
     funds: 33.34% (75 XMR)
-    done:
-    status: unfinished
+    done: 17 May 2023
+    status: finished
+payouts:
+  - date: 17 June 2021
+    amount: 150
+  - date: 17 August 2023
+    amount: 75
 ---
 Hi,
 

mrcyjanek-xmruw-development.md

+---
+layout: wip
+title: xmruw - development of cross platform wallet
+author: mrcyjanek
+date: February 29, 2024
+amount: 76.68
+milestones:
+  - name: Month 1
+    funds: 25.56
+    done: 8 July 2024
+    status: finished
+  - name: Month 2
+    funds: 25.56
+    done: 31 August 2024
+    status: finished
+  - name: Month 3
+    funds: 25.56
+    done:
+    status: unfinished
+payouts:
+  - date: 17 July 2024
+    amount: 25.56
+  - date: 4 September 2024
+    amount: 25.56
+  - date:
+    amount:
+---
+
+Hello! I'm mrcyjanek and I'm currently working on the Unnamed Monero Wallet (short: xmruw) that aims to be as portable as possible and as close to `wallet2_api.h` as it is reasonably possible.
+
+However, this project got much bigger than I initially expected and resulted in a project that is huge in size, but also has really large portability capabilities, after fighting for a couple days with Wayland implementation on SailfishOS I (with the help from Mister_Magister and NotKit) managed to run the first cryptocurrency wallet natively on SFOS ([that is available on the app store of that os](https://openrepos.net/content/mrcyjanek/unnamed-monero-wallet-xmruw)). More details and the origin story can be found in a [blog post announcing the wallet](https://www.mrcyjanek.net/p/xmruw-monero-wallet/).
+
+I'm developing `xmruw` with a few critical points in mind:
+- There should be no database responsible for any of the monero-releated functions - so I won't accidentally do something that shouldn't be done.
+- The app should be as close to `wallet2_api.h` as possible to eliminate things like overly complex state management as something that causes issues.
+- Privacy should be prioritized - no external services are contacted in the app, and if there ever happens to be some external feature it will be opt-in in settings with an option to route entire traffic through Tor.
+- Security is also prioritized - not only by minimizing the attack surface but also by providing features such as stealth mode (inspired by Samourai wallet)
+- UX is the most critical of them all in my opinion - without the right UX, not many users are going to use a wallet, so it is my responsibility as a developer to make the wallet available on all platforms and to be appealing to users.
+- As a mobile Linux enthusiast I'll also do my best to offer secure monero wallet solutions for owners of non-Android and non-iOS mobile devices
+
+# About
+
+I've decided to take the simplest path from `wallet2_api.h` to the actual wallet UI, so instead of forking m2049r/cake implementation I've decided to use `dart:ffi` to call the native functions - this made a lot of code unnecessary, and the part that was still required was mostly generated - so I call that a huge win. But not without it's own cost - I had to write a wrapper for `wallet2_api.h` that would provide C headers instead of C++ - which meant [writing a bunch of boilerplate code](https://git.mrcyjanek.net/mrcyjanek/monero_c/src/commit/abaa3a2d165577a79ce0c3fe5382b68fa260ecc1/libbridge/src/main/cpp/wallet2_api_c.cpp#L1549) and implementing a couple of dart/flutter libraries, that gave birth to the foundation of the wallet
+
+## Unnamed Monero Wallet (xmruw)
+
+[Website](https://xmruw.net), [Gitea](https://git.mrcyjanek.net/mrcyjanek/unnamed_monero_wallet), [GitHub](https://github.com/mrcyjanek/unnamed_monero_wallet), [Downloads](https://download.xmruw.net/)
+
+Features of the wallet include:
+- Sending/Receiving monero
+- Online/Offline wallet modes
+  - With URQR and file exports for Android/iOS
+  - With clipboard-based exports for QubesOS
+- Embedded Tor support
+- (soon) Embedded i2p support [^1]
+- Stealth mode (fake calculator app that opens wallet if the correct pin is provided)
+- Multiple account support
+- Coin control
+- Signing / Verifying of messages
+- Custom themes
+- Advanced settings
+  - Performance analysis tool for the `wallet2_api.h` functions called
+  - Debug information that makes development easier
+  - Configuration options to opt-in to experimental features (such as [background sync](https://github.com/monero-project/monero/pull/8619))
+- OpenAlias resolving
+- Backup/Restore
+- Historically accurate currency conversion done fully offline
+- And all of the "obvious" features such as transaction list, subaddress list, wallet locking, QR code scanning, etc.
+
+## Scope of work
+
+While working on Unamed Monero Wallet, here is a non-comprehensive list of the things I want to accomplish in no particular order, as it doesn't make sense to separate some things.
+
+- Expanding compatibility of `monero_c` to all platforms that I have access to (Linux (glibc+musl), FreeBSD, iOS, MacOS, Windows) in an easily-reproducible way (single script and a docker environment)
+- Making `xmruw` available for all platforms (and I do mean all platforms) and in app stores (including play store, self-hosted f-droid repository, apple app store, .deb, and .rpm repository).
+- Implementing features desired by users, currently this includes
+  - periodic sync (via [background-sync](https://github.com/monero-project/monero/pull/8617)) to provide seamless experience, no matter how frequently the app is actually opened
+  - merchant mode
+  - many UI/UX improvements/changes (some of more important ones: make seed offset and its role more obvious, better backup mechanism, time-lock warn, automatic node selection)
+- Work on documentation (this will be a significant task on its own, but the goal is to allow anybody to integrate monero no matter what language/framework they are using by using monero_c/monero.dart).
+- Fix issues that were made along the way
+  - Bytewords entering an infinite loop when incorrect text is passed in
+  - No compatibility with Feather / ANONERO in offline mode due to lack of CBOR encoding
+  - Not cross-platform QR scanner [^2]
+  - Bad UI on desktop (not that it's bad, it is just mobile-first)
+  - and more, if found when developing
+  - sending fixes to relevant peers and upstream
+
+## Milestones
+
+Given the nebulous nature of development, I would prefer my milestones to be time-based. I prpose a milestone completion and subsequent payout once every month (after services rendered).
+
+In addition to the above features mentioned in the scope of work, I propose an additional deliverable of a weekly report so my progress can be verified.
+
+# Payment
+
+I'm proposing to work for 20 hours/week for `40$/hour` at a rate of `~125,14$/XMR` (according to open prices between 2024-02-17 and 2024-03-01 (date of writing) via [CoinGecko](https://www.coingecko.com/en/coins/monero/historical_data)) for 12 weeks, summing up to a total of `~76,68` XMR split into 3 payments of `25,56` XMR every 4 weeks.
+At the end of each week, I'll comment a summary of what happened along the way and what tasks were done.
+
+[^1]: The library is there, it needs some love to be usable, cross platform and built in a reproducible fashion.
+
+[^2]: Camera isn't fun, especially when being cross-platform is a goal, but supporting it is critical for URQRs. This isn't a milestone on it's own, but a topic that I'll research, do some PoC and come up with a solution, especially because getting camera to work is one task, then we need to scan qr the codes (and be **very** fast at it), so this milestone is more of "explore the possibilities" and come up with a reasonable plan for future regarding cross-platform camera support.

netrik-tranlation-coordination-1.md

+---
+layout: cp
+title: Translation Coordinator for the Monero Project
+author: netrik182
+date: October 6, 2021
+amount: 11
+milestones:
+  - name: One month work
+    funds: 11
+    done: 3 December 2021
+    status: finished
+payouts:
+  - date: 8 December 2021
+    amount: 11
+---
+
+## Translation Coordinator for the Monero Project
+Translations have always been an important part of this community and an essential tool to spread Monero to everyone. ErCiccione has been the manager of this workgroup for a long time (see their proposals at the bottom) and recently has been looking for someone to take on these responsibilities as they are focusing their time on other projects now (e.g. Haveno).
+
+The Monero Project has always benefited from having well structured and consistent translations across its many resources thanks to ErCiccione and many other contributors/translators. After they announced on #monero-translations that they are looking for someone to take care of it, I want to step in and keep that going.
+
+## About me
+I have been involved with FLOSS and Monero-specific translation work for more than 5 years now. I also run https://monerobrasil.org/ and [#monero-brasil](https://matrix.to/#/#monero-brasil:monero.social).
+
+### My profiles
+- repo.getmonero.org [profile](https://repo.getmonero.org/users/netrik182/activity) where I contributed before Pootle (and now Weblate) was a thing.
+- Weblate [profile](https://translate.getmonero.org/user/netrik182/) where I contribute to getmonero.org, Monero GUI translations, Monero Means Money, and other Dr. Kim's videos, etc.
+- GitHub [profile](https://github.com/netrik182) where most things were done.
+
+### Previous Work
+- **Monero Ecosystem Translations:** Provided the transcription, captions and translations. As well as the terminology guides. You can check all [here](https://github.com/monero-ecosystem/monero-translations/pulls?q=netrik182) and [here](https://github.com/ajs-xmr/moneromovie/pulls?q=is%3Apr+author%3Anetrik182+).
+- **Monero Website and Monero GUI:** Most of my contributions to GUI Wallet are on Weblate. Contributions I made on GitHub [here](https://github.com/monero-project/monero-gui/pulls?q=netrik182+) and [here](https://github.com/monero-project/monero-site/pulls?q=netrik182).
+- **Monero Outreach:** I contributed with translation, transcription and revision of many [outreach materials](https://github.com/monero-ecosystem/outreach-docs/pulls?q=netrik182).
+- **Monerujo:** Translation and review of [Monejuro](https://github.com/m2049r/xmrwallet/pulls?q=netrik182).
+- **AgoraDesk/LocalMonero:**  [Translation and review](https://github.com/AgoraDesk-LocalMonero/translation/pulls?q=is%3Apr+author%3Anetrik182) of their website.
+- **Mastering Monero:**  [Translation](https://github.com/monerobook/monerobook/pull/94) and [review](https://github.com/monerobook/monerobook/pull/93). Also see [the book itself](https://netrik182.gitlab.io/docs-monerobrasil.org/masteringmonero/) and the [CCS proposal](https://ccs.getmonero.org/proposals/netrik182-mastering-monero-translation.html).
+
+## Responsibilities
+Things the manager must take care of are:
+1. Manage translators and their work on Weblate for the following projects:
+- **Community:** https://translate.getmonero.org/projects/community/
+- **Getmonero:** https://translate.getmonero.org/projects/getmonero/
+- **Getmonero user guides:** https://translate.getmonero.org/projects/getmonero-user-guides/
+- **Monero CLI and GUI:** https://translate.getmonero.org/projects/monero/
+2. Manage translators and their work on GitHub for the following projects:
+- **Monero Translations:** https://github.com/monero-ecosystem/monero-translations
+- **Monero Website:** https://github.com/monero-project/monero-site
+- **Monero GUI Guide (translation only):** https://github.com/monero-ecosystem/monero-GUI-guide
+3. Maintain a list of contributors and their working language;
+4. Manage translations on Weblate (this includes adding notes and keeping an eye on the entire platform for spam, etc.);
+- Making sure strings have clarifications and explanations where necessary;
+- Communicate with ErCiccione when translations are ready so they can push them to the repository (where they are supposed to be: /monero, /monero-site, /monero-gui, /monero-translations for subtitles);
+5. Take care of translations-related CCS (the current system is not optimal and needs to be improved. See more bellow.);
+6. Unify, update and maintain documentation on different repositories;
+- [/monero](https://github.com/monero-project/monero/blob/master/docs/README.i18n.md) instructions;
+- [/monero-translations](https://github.com/monero-ecosystem/monero-translations) instructions;
+- [/monero-gui](https://github.com/monero-project/monero-gui#translations) instructions;
+- [/monero-site](https://github.com/monero-project/monero-site#translation) instructions;
+- [Weblate](https://github.com/monero-ecosystem/monero-translations/blob/master/Weblate.md) instructions;
+- [Translations tips](https://github.com/monero-ecosystem/monero-translations/blob/master/translation-tips.md);
+- [Monerujo](https://github.com/monero-ecosystem/monero-translations/blob/master/translate-monerujo.md) instructions;
+7. Answer questions and coordinate people in the chat-rooms (#monero-translations on Libera/Matrix);
+8. Make sure when there are translations available on Weblate, they are pushed upstream (repository they belong to);
+9. Provide updates to the community about the state of the translations and workgroup-related activities during #monero-community meetings;
+10. Issue progress reports on a monthly basis as GitLab comments and share within the community (e.g. Reddit/Matrix/IRC).
+
+## Limitation of Scope
+ErCiccione will keep managing the backend side of things (update Weblate, bug issues, etc). I will maintain the languages on Weblate, help and find translators, update the documentation, etc. as highlighted above.
+
+## Translation-related CCS proposals
+One of the first tasks of this role will be to rethink the whole process of contributors using the CCS to fund their translation efforts. We have had problems with low quality work in the past and although some rules have been discussed and laid out with the help from Core, I want to focus on defining and _enforcing_ some basic rules for translation-related CCS's in the future, accepting work from:
+- Translators with a provable portfolio as professional translators
+- Contributors of the Localization Workgroup that have a track record of delivering high quality translations (work that has been reviewed by others and deemed of high quality, for example)
+
+The end goal is to guarantee the Monero Project has its resources translated and that these translations are of high quality. We plan to establish a hybrid approach in which community members could contribute if they wanted to (as volunteers or paid work) given the rules above and in case we fail to meet the above requirements for any given language a.k.a. these contributors do not exist or are of bad quality, they could be replaced with professional resources.
+
+## Funding
+I want to open this CCS to work for the first month as a trial run and later on if the Community thinks it was worth it, I can move to 3-months proposals for long-term commitment. This proposal will consist of 20h/week for 4 weeks at a rate of 30€/h, with a total of 11 XMR (1 xmr = 219€ at Kraken). _I will update the rate shortly before merging (if merged at all)._
+
+## Milestones for the first month:
+1. **Review, update and unify translations instructions from item 6 above:** the idea is to have a single document with all instructions laid out and then each repository could reference this _source_ material. This will simplify maintenance and also help onboarding new contributors. I think this is the most important milestone and hence it will take most of my time.
+2. **Translation-work coordination:** this covers the whole process of managing translations, community and outsourced translators and so on. It is the bulk of responsibilities and must be performed continually. I would also put in here the community reports/updates on a monthly basis and participation on -community meetings.
+
+## Future ideas
+1. **Work with Core and ErCiccione to grab statistics from Monero Website:** the idea is to assess visitors preferred language and use that information to focus on which language we need to prioritize and also which resources are most valuable to translate first. This will enable us to create a prioritization list of sorts.
+2. **Create a Translation Fund for continued maintenance of translation work:** I have talked with some Core Team members and they expressed the possibility of a Translation Fund existing and those funds being used to outsource specific work to translation outlets in the absence of community members meeting the criteria of high quality work. Having money set apart for this specific goal together with the statistics of language/resource prioritization list will help us achieve the end goal of ensuring Monero is translated into the most needed languages.
+
+## Expiration
+October 31, 2021
+
+## Past coordination proposals by ErCiccione for reference
+- https://forum.getmonero.org/22/completed-tasks/89232/coordinator-for-localization-group-various-maintenance
+- https://forum.getmonero.org/22/completed-tasks/90000/monero-localizations-coordinator-2nd-ffs
+- https://forum.getmonero.org/22/completed-tasks/90271/coordinator-of-the-localization-workgroup-3-more-months-erciccione
+- https://forum.getmonero.org/9/work-in-progress/90800/erciccione-coordinator-of-the-localization-workgroup-translations-another-quarter
+- https://forum.getmonero.org/9/work-in-progress/91261/erciccione-coordinator-of-the-localization-workgroup
+- https://ccs.getmonero.org/proposals/ErCiccione-localizations.html
+- https://ccs.getmonero.org/proposals/ErCiccione-Weblate.html

netrik-translation-coordination-2.md

+---
+layout: cp
+title: Three Months of Translation Coordination
+author: netrik182
+date: December 7, 2021
+amount: 45
+milestones:
+  - name: December
+    funds: 15
+    done: 31 December 2021
+    status: finished
+  - name: January
+    funds: 15
+    done: 31 January 2022
+    status: finished
+  - name: February
+    funds: 15
+    done: 12 February 2025
+    status: finished
+payouts:
+  - date: 5 January 2022
+    amount: 15
+  - date: 8 February 2022
+    amount: 15
+  - date: 12 February 2025
+    amount: 15 
+
+---
+
+### Proposal closure / funds reallocation 1st Feb 2025
+
+The remaining 15XMR from this proposal have been transferred to [v1docq47](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests?scope=all&state=merged&author_username=v1docq47)
+
+## Translation Coordinator for the Monero Project
+My first proposal is now completed and I would like to continue working as translation coordinator for the upcoming months. You can read more about the initial proposal [here](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/260), also read the reports in the comments and on [reddit](https://www.reddit.com/r/Monero/comments/qqqoch/ccs_report_translation_coordinator/). 
+
+As stated before, the Monero Project has always benefited from having well structured and consistent translations across its many resources and I want to keep that going.
+
+### My profiles
+- repo.getmonero.org [profile](https://repo.getmonero.org/users/netrik182/activity)
+- Weblate [profile](https://translate.getmonero.org/user/netrik182/)
+- GitHub [profile](https://github.com/netrik182)
+- GitLab [profile](https://gitlab.com/netrik182)
+
+### Previous Work
+You can read a detailed list in my first proposal.
+
+## Responsibilities
+Responsibilities remain the same as before, summarized as:
+1. Manage translators and their work on Weblate for the following projects:
+- **Community:** https://translate.getmonero.org/projects/community/
+- **Getmonero:** https://translate.getmonero.org/projects/getmonero/
+- **Getmonero user guides:** https://translate.getmonero.org/projects/getmonero-user-guides/
+- **Monero CLI and GUI:** https://translate.getmonero.org/projects/monero/
+2. Manage translators and their work on GitHub for the following projects:
+- **Monero Translations:** https://github.com/monero-ecosystem/monero-translations
+- **Monero GUI Guide (translation only):** https://github.com/monero-ecosystem/monero-GUI-guide
+3. Maintain a list of contributors and their working language;
+4. Take care of translations-related CCS (the current system is not optimal and needs to be improved. See more bellow.);
+5. Maintain translation documentation on different repositories;
+- [/monero](https://github.com/monero-project/monero/blob/master/docs/README.i18n.md)
+- [/monero-translations](https://github.com/monero-ecosystem/monero-translations)
+- [/monero-gui](https://github.com/monero-project/monero-gui#translations)
+- [/monero-site](https://github.com/monero-project/monero-site#translation)
+- [Weblate](https://github.com/monero-ecosystem/monero-translations/blob/master/Weblate.md)
+- [Translations tips](https://github.com/monero-ecosystem/monero-translations/blob/master/translation-tips.md)
+- [Monerujo](https://github.com/monero-ecosystem/monero-translations/blob/master/translate-monerujo.md)
+6. Answer questions and coordinate people in the chat-rooms (#monero-translations on Libera/Matrix)
+7. Make sure when there are translations available on Weblate, they are pushed upstream (repository they belong to)
+8. Provide updates to the community about the state of the translations and workgroup-related activities during #monero-community meetings
+9. Issue progress reports on a monthly basis as GitLab comments and share within the community (e.g. Reddit/Matrix/IRC)
+
+## Limitation of Scope
+Core Team is looking for someone to manage the backend structure as ErCiccione announced they're stepping down (update Weblate, bug issues, etc). I will maintain the languages on Weblate, help and find translators, update the documentation, etc. as highlighted above.
+
+## Milestones and Funding
+Now I would like to keep this CCS as 3-months proposals for long-term commitment. This proposal will consist of about 20h/week from December 1st, 2021 to February 28th, 2022 at a rate of 30€/h I'm rounding to 45 XMR (1 xmr = 170€ at Kraken). **Translation coordination** work covers the whole process of managing translations, community members, weblate and the repositories. We're are still having many merging conflicts on Weblate and some integrations are not working properly. Resolving that will ensure we have a friction-free process.
+
+## Expiration
+December 31, 2021

noot-eth-xmr-atomic-swap.md

+---
+layout: cp
+title: ETH-XMR Atomic Swap Development
+author: noot
+date: Dec 4 2021
+amount: 56 XMR
+milestones:
+  - name: Maintainence of existing codebase
+    funds: 5 XMR
+    done: 5 February 2022
+    status: finished
+  - name: Contract improvements
+    funds: 8 XMR
+    done: 27 January 2022
+    status: finished
+  - name: DLEq integration
+    funds: 12 XMR
+    done: 1 May 2022
+    status: finished
+  - name: Integration testing
+    funds: 8 XMR
+    done: 21 March 2022
+    status: finished
+  - name: Network testing 
+    funds: 8 XMR
+    done: 24 May 2022
+    status: finished
+  - name: Pre-print paper and additional research
+    funds: 5 XMR
+    done: 23 June 2022
+    status: finished
+  - name: UI
+    funds: 10 XMR
+    done: 23 June 2022
+    status: finished
+payouts:
+  - date: 28 January 2022
+    amount: 8
+  - date: 8 February 2022
+    amount: 5
+  - date: 22 March 2022
+    amount: 8
+  - date: 27 May 2022
+    amount: 20
+  - date: 29 June 2022
+    amount: 5
+  - date: 29 June 2022
+    amount: 10
+---
+
+# Summary
+
+This proposal is for the continued development of ETH-XMR atomic swaps. The milestones include continued maintence and testing of the current codebase, gas improvements, network and integration testing, and documentation. At the completion of this proposal, there will be an audit-ready pre-production release of the ETH-XMR atomic swap software, as well as a pre-print paper outlining future improvements to the protocol. The total estimated duration of this proposal is 16 weeks.
+
+# Team
+
+[noot](github.com/noot) will be completing milestones 1-6. Milestone 7 will be completed by [Tbaut](https://github.com/Tbaut).
+
+### About me (noot)
+
+Since I'm quite new to the Monero space, I figured I'd post a little bit about me here. I've been working as a professional blockchain protocol engineer for nearly 4 years (will be 4 years in March 2022). I also have a Bachelor's of Applied Science specializing in Computer Engineering from the University of Toronto. For my undergraduate thesis project, I explored adding privacy to Ethereum, which ended up with me writing a Go implementation of RingCT. Although the project didn't really go anywhere, it was my introduction to real-life cryptography and of course Monero. Since then I've been casually following Monero. I've always loved the tech and the ethos and I'm glad to finally be able to contribute to it! 
+
+I'm passionate about privacy-preserving technologies and I think Monero really is the best and only (afaik) cryptocurrency that's truly private. I hope this project will bring more users to Monero by reducing the onboarding overhead, specifically by not needing to rely on a centralized exchange. I hope this work, along with the current inspiring XMR-BTC swap work being done, will help bring in fully decentralized, peer-to-peer exchanges.
+
+Most of my past work is focused on alternative blockchain protocol implementations, including implementations for Polkadot and Filecoin. I've also worked on Ethermint (EVM Cosmos module), a *little* bit on some ETH2 libraries, and written/tested various smart contracts in my day, which consists of most of my Ethereum experience. I've also worked on go-libp2p-noise (a handshake protocol for the p2p library libp2p) and go-schorrkel (schnorr signatures over ristretto255, used in Polkadot), both of which are now in production! The language I've used the most is Go (namely why this project is in Go), but I've also used Rust, JS, and Solidity.
+
+Since I'll be continuing to work full-time, this project will be done on a part-time basis. As of writing I'm the only person who will be working on this. I estimate I'll be able to put in ~15 hours per week, which might vary week-to-week depending on how busy I am.
+
+# Motivation
+
+Atomic swaps are a method for trustlessly exchanging funds across blockchains. An ETH-XMR atomic swap will allow for users to, in a trustless and completely decentralized manner, exchange Ether for Monero. This connects the leading smart contract blockchain (and the home of defi) with the leading privacy-preserving blockchain. Along with the BTC-XMR atomic swaps, this will allow for completely decentralized cross-chain exchanges to be built that allow for XMR swaps. 
+
+# Milestones
+
+## 1. Maintenance of existing codebase (estimated 2 weeks)
+This includes:
+- improved unit tests, >70% test coverage for whole repo
+- inline documentation (ie. code-level docs)
+- JSON-RPC API documentation
+- general code cleanup
+
+## 2. Swap contract improvements (estimated 2 weeks)
+There is already a smart contract (Swap.sol) that implements the Ethereum on-chain side of the protocol. However, to reduce gas costs, this can be turned into a "factory" style contract that allows users to create swap instances without having to re-deploy a contract, thus allowing for gas savings. 
+
+This milestone includes:
+- Creation of swap factory contract
+- Testing and integration of contract with codebase
+- Documentation on how to deploy the swap contract ot any EVM-based chain and interact with it 
+
+## 3. DLEq integration (estimated 2-4 weeks)
+For background, monero uses the ed25519 elliptic curve and ethereum uses the secp256k1 elliptic curve. The current implementation of the protocol verifies that a secret corresponds to a valid public key on the ed25519 curve by performing an elliptic curve multiplication (ECMUL). There is a version of the protocol that allows for massive gas savings (~30x improvement on Claim/Refund calls) by moving some of the computation off-chain. This is achieved by allowing secp256k1 keys to be verified on-chain (instead of ed25519), while off-chain, a DLEq proof is passed by each party to the counterparty that proves that their secret corresponds to public keys on both the secp256k1 curve and the ed25519 curve.
+
+This milestone includes:
+- Completion of the DLEq version of the swap contract, which performs a secp256k1 ECMUL as the verification step
+- Testing of the contract
+- DLEq proof generation and verification
+  - either using an existing Rust library, potentially using CGO to create language bindings from Rust->Go
+  - or, creating a Go implementation of DLEq proof and verification
+- Integration with the codebase (updates of network messages and handling of protocol steps)
+
+A potential alternative to using an existing Rust library is to write a DLEq implementation in Go. This would be preferred in the long run as it will be easier for users to build (as they would only been one language installed) and usage of CGO can cause linking issues during build on different platforms. As well as a developer, it's easier to maintain. I would prefer to create a Go implementation for the aforementioned reasons, although it would take longer than using an existing library. However, in the long run, I believe it would save developer hours.
+
+## 4. Integration testing (estimated 2 weeks)
+This includes:
+- End-to-end testing of the swap from both parties's point of view and for all possible claim/refund cases.
+- Will be in the form of Go test cases.
+
+## 5. Network testing and infrastructure (estimated 3 weeks)
+This includes:
+- setting up infrastructure (servers) to host swap nodes 
+- testing of a larger network of swap nodes (10+ nodes) that has many swap providers
+- testing of node discovery, messaging, and swap initiation
+- testing script to allow for the above cases to be run against a network 
+
+As there will likely be issues that are uncovered while testing, this milestone is assumed to include fixes for those issues.
+
+## 6. Additional research and pre-print paper (estimated 2-4 weeks)
+I would like to formalize the existing swap protocol and its variations, and as well to conduct additional research into improvements to the protocol. 
+
+This includes:
+- a pre-print paper that describes the current ETH-XMR atomic swap protocol and its security guarantees
+- a new version of the protocol that allows the XMR-holding party to move first, as the current protocol is limited by the ETH party needing to lock their funds first
+- potential optimizations to the protocol, focusing on ethereum gas costs
+- discussion of privacy implications on both the ethereum and monero sides
+
+## 7. UI
+This milestone includes an in-browser UI for interacting with the swap network. 
+
+This includes:
+- displaying the current swap offers available on the network
+- ability for a user to log in with a browser-based Ethereum wallet (Metamask) and take a swap offer
+
+## In case of extra funds
+
+If there are extra funds/time left over, this will be used to investigate the following:
+- ERC20 support; ie. ability to directly swap XMR for an ERC20 token
+- privacy improvements on the ethereum side
+- tor support
+
+## Licensing
+
+The codebase is currently licensed as GPLv3 due to usage of a library that is licensed GPLv3. However, this license can be changed after the DLEq integration (milestone 3) is complete. My preference is for GPL but I will also relicense as LGPL if needed. I would like to stick with GPL or LGPL as it prevents the code from being relicensed and used in closed-source software.
+
+## At completion
+
+At completion of this proposal, there will be a pre-production release of the software that includes binaries for Linux, MacOS and Windows.
+
+# Expiration date
+
+This CCS will expire on February 4 2022.

oeAdgK01-Translation of Monero CLI & GUI (GUI Wallet), Getmonero (monero-site) and Community (Monero Means Money (subtitles), Sound Money, Safe Mode (subtitles)) to Greek.md

 ---
-layout: fr
+layout: cp
 title: Translation of Monero GUI Wallet, Getmonero (monero-site), Community (Monero Means Money (subtitles) and Sound Money, Safe Mode (subtitles)) to Greek
 author: Donald A. Iljazi
 date: November 9, 2020
@@ -7,29 +7,23 @@ amount: 30
 milestones:
   - name: Milestone 1 - Completion of GUI Wallet Translation to Greek
     funds: 2 XMR
-    done:
-    status: unfinished
+    done: 11 November 2020
+    status: finished
   - name: Milestone 2 - Completion of monero-site Translation to Greek
     funds: 8 XMR
-    done:
-    status: unfinished
+    done: 25 November 2020
+    status: finished
   - name: Milestone 3 - Completion of Monero Means Money (subtitles) Translation to Greek
     funds: 10 XMR
-    done:
-    status: unfinished
+    done: 20 February 2021
+    status: finished
   - name: Milestone 4 - Completion of Sound Money, Safe Mode (subtitles) Translation to Greek
     funds: 10 XMR
-    done:
-    status: unfinished
+    done: 17 April 2021
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 2 October 2021
+    amount: 30
 ---
 
 # About this Proposal
@@ -107,4 +101,4 @@ Timeline: 21/12/2020 - 10/01/2021
 
 ### Proposal Expiration Date
 
-19/11/2020
\ No newline at end of file
+19/11/2020

ofrnxmr-totw3.md

+---
+layout: wip
+title: ofrnxmr support, docs, site, meta++ (totw pt3)
+author: ofrnxmr
+date: July 31, 2024
+amount: 168
+milestones:
+  - name: Aug 2024
+    funds: 14 XMR
+    done: 23 September 2024
+    status: finished
+  - name: Sep 2024
+    funds: 14 XMR
+    done: 31 January 2025
+    status: finished
+  - name: Oct 2024
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Nov 2024
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Dec 2024
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Jan 2025
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Feb 2025
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Mar 2025
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Apr 2025
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: May 2025
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Jun 2025
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Jul 2025
+    funds: 14 XMR
+    done:
+payouts:
+  - date: 28 September 2024
+    amount: 14
+  - date: 25 February 2025
+    amount: 14
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+Welcome back. Hopefully I still have your ear.
+
+I'd like to take a moment to express gratitude towards all of my anonymous supporters. I see you, and I thank you for everything you've helped me with thus far. I wouldn't be here without you. If this proposal is merged, I will likely be good through til 2026.
+
+This may not seem as abnormal as I'd have liked. The title is what it is, but the proposal is intended to cover contributions to Monero proper. It was requested that I open a new MR instead of editing the [old one](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/444).
+
+- 14xmr/mth includes 20-25hrs/wk on customer support, docs, site, ccs, assisting devs, and attempting to take over the world:
+  - 3xmr/mth work with core devs, community devs, researchers, and other contributors to test or advise on features, issues, community projects etc.
+  - 3xmr/mth #monero-support: Lead the support channel & provide hands on support to users
+  - 3xmr/mth #monero-docs: Maintain¹ (or help to maintain) monero-docs repo and/or assist plowsof, 321bob321 and others with content
+  - 2xmr/mth #monero-site: Maintain¹ (or help to maintain) monero-site repo and/or assist plowsof, hardenedsteel and others with content
+  - 2xmr/mth #monero-community: Assisting CCS proposers (and plowsof) with relations/logistics
+  - 1xmr/mth take over the world: dedicate time to dealing with "meta" stuff. There is quite a bit of unfinished business (on and off repo) that needs to be tackled
+  - donate to others
+
+The above amounts are estimates. Actual distribution may vary.
+
+¹ Maintain = handle merges
+
+Terms:
+- 12 Months @ 168xmr total
+- Estimated 20-25 hr/wk
+
+Rate:
+- 1 XMR = 1 XMR
+
+Payout structure: 
+- 12 monthly milestones
\ No newline at end of file

ofrnxmr_basicswap.md

+---
+layout: wip
+title: "ofrnxmr feat BasicSwapDEX - take over the world pt 2"
+author: ofrnxmr
+date: 12 August 2024
+amount: 1685
+milestones: 
+  - name: M0-O (ofnxmr, 1st month)
+    funds: 20 XMR
+    done: 3 September 2024
+    status: finished
+  - name: M0-Y (80xmr bounties, 3 months)
+    funds: 80 XMR
+    done: 28 September 2024
+    status: finished
+  - name: M0-F (~0-160hrs, 1st month)
+    funds: 40 XMR
+    done: 4 September 2024
+    status: finished
+  - name: M0-B (~0-160hrs, 1st month)
+    funds: 55 XMR
+    done: 4 September 2024
+    status: finished
+  - name: M1-O (ofrnxmr, 2nd month)
+    funds: 20 XMR
+    done: 17 October 2024
+    status: finished
+  - name: M1-F (~160-320hrs, 2nd month)
+    funds: 40 XMR
+    done: 17 October 2024
+    status: finished
+  - name: M1-B (~160-320hrs, 2nd month)
+    funds: 55 XMR
+    done: 17 October 2024
+    status: finished
+  - name: M2-O (ofrnxmr, 3rd month)
+    funds: 20 XMR
+    done: 30 November 2024
+    status: finished
+  - name: M2-F (~320-480hrs, 3rd month)
+    funds: 40 XMR
+    done: 30 November 2024
+    status: finished
+  - name: M2-B (~320-480hrs, 3rd month)
+    funds: 55 XMR
+    done: 30 November 2024
+    status: finished
+  - name: M3-O (ofrnxmr, til completion)
+    funds: 100 XMR
+    done:
+    status: unfinished
+  - name: M3-F - Frontend GUI v3.0.0 - v5.0.0+ (prepaid, ~6 months)
+    funds: 320 XMR
+    done: 19 January 2025
+    status: finished
+  - name: M3-B - Backend v0.13 - v0.15+ (prepaid, ~6 months)
+    funds: 410 XMR
+    done: 19 January 2025
+    status: finished
+  - name: M4 - Delivery of 1.0 (postpaid, ~3 months)
+    funds: 190 XMR
+    done:
+    status: unfinished
+    milestones: 
+  - name: M5 - 1yr maintenance (ongoing)
+    funds: 240 XMR
+    done:
+    status: unfinished
+payouts:
+  - date: 14 September 2024
+    amount: 115
+  - date: 28 September 2024
+    amount: 80
+  - date: 23 October 2024
+    amount: 115
+  - date: 6 December 2024
+    amount: 115
+  - date: 6 February 2025
+    amount: 730
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+Welcome ladies and gentleman, kids and pets.
+
+Lets skip the intro.
+
+  BasicSwapDEX is, as far as I know, Monero's only Bidirectional Atomic swap service, and the only one that allows swapping monero with coins not named Bitcoin (such as Litecoin). 
+
+  BasicSwapDEX has been mainnet for a while now, but is a beta / POC. With this CCS I hope empower and steward BasicSwapDex to production quality software within ~1 year. Some milestones are to be paid to ofrnxmr in advance. I'm also requesting that some funds be escrowed by the CCS Coordinator.
+	 
+##### M0/M1/M2 = accelerate work / probation.
+- M0 paid at funding. To be paid to ofrnxmr to distribute as follows:
+  - M0 = 80xmr to ofrnxmr to pay for bounties / extra help, and/or bonuses to backend/frontend devs
+  - M0/M1/M2 = 20xmr/month (60xmr/3months) to ofrnxmr
+  - M0/M1/M2 = 40xmr/160hrs (120xmr/3mths) to BasicSwap Team - Frontend
+  - M0/M1/M2 = 55xmr/160hrs (165xmr/3mths) to BasicSwap Team - Backend
+
+##### M3-O - Paid end of month 4
+  - 100xmr
+    
+##### M3-F - Frontend GUI v3.0.0 - v5.0.0+
+- Paid start of month 4
+  - 240xmr earmarked for frontend development (paid out by ofrnxmr as work is completed, 40xmr/160hr)
+  - 80xmr to ofrnxmr to pay for bounties / extra help, and/or bonuses to frontend devs
+
+##### M3-B - Backend v0.13 - v0.15+
+- Paid start of month 4
+  - 330xmr earmarked for backend development (paid out by ofrnxmr as work is completed: 55xmr/160hr)
+  - 80xmr to ofrnxmr to pay for bounties / extra help, and/or bonuses to backend devs
+
+##### M4 - Delivery of 1.0
+- Paid after M3 is completed to satisfaction, and 1.0 is shipped 
+  - 80xmr for frontend dev(s)
+  - 110xmr for backend dev(s)
+
+##### M5 = Maintenance
+- Payout in Month 13 at the earliest, to be redistributed on a monthly basis 
+  - 8xmr to backend devs
+  - 8xmr to frontend devs
+  - 4xmr to ofrnxmr
+
+#### Scope (wherever technically possibly)
+- **_M0/M1/M2 = Catchup work. Begin preparing for M3 milestones._**
+  - [Some things yet to be completed](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/457#note_24394)
+- **_M3-F - Frontend GUI v3.0.0 - v5.0.0+_**
+  - CEX-like UI and UX (aside from speed)
+    - Orderbook
+    - Market depth
+    - Order types ie. Market, limit, stop, trailing, profit taker
+  - Private orderbook UI
+  - Overall UI and UX updates
+    - Mobile friendly
+    - Better notifications
+    - Improve / simplify in progress and historical bid details
+  - Historical swap exports
+  - Drop _reliance_ on centralized price APIs
+  - Add wallet (rpc) functionality to the wallets themselves
+  - Ability to use external wallets to take offers
+  - Include new GUI interfaces to match new backend functionalities
+- **_M3-B - Backend v0.13 - v0.15+_**
+  - Secure the backend
+  - Better code reviews
+  - Fix and enhance user APIs
+  - Add provider / swapper APIs
+  - Web frontend APIs
+  - Enable swaps between incompatible coins. [Example: XMR <> FIRO]
+  - Integrations of atomic protocals such as those from BCH and ETH
+  - Disconnect SMSG from Particl blockchain
+  - Create and use a local price oracle
+  - Bridge orderbooks from other services such as Samourai 
+  - EVM wallet compatibility
+  - Necessary changes to enable frontend features
+- **_M4 - Delivery of 1.0_**
+  - M3-X Completed to satisfaction
+  - Ship 1.0 installation packages as (example), a Flatpak, appimage
+- **_M5 - 1yr Maintenance_**
+  - Addressing concerns in an efficient manner
+  - Continued improvement of the codebase
+
+The scope of work is quite large. You can follow Particl dev report (going back to January) for current, ongoing and planned work, which is ever evolving.
+
+Should any part of this CCS fail, I may choose to redirect remaining funds to fork the project or to acquire devs willing/able to complete it.
+
+In the event of total failure, all unused funds will be donated to a 2/3 multisig (The elusive "jetfund") with the COMMUNITY Coordinator and 1 other [TBD] party, to be used **as the community decides**....Though, im ofrnxmr. I'm not _fill in name of scammer_. I will see this through to completion.
+
+##### Coverage
+- M0/M1/M2 = Month 0-3
+- M3-O = Month 4-12
+- M3-X = Month 4 'til Completion of M3-X milestones (target = ~6 months)
+- M4 = Completion of M3-X milestones til the later of completion of M4 or Month 13
+- M5 = 12 Months. Earliest payouts may begin is the later of completion of M4 or Month 13
+
+**This CCS allows the Monero Community to lead the space to a goal of having a FOSS, trustless, unregulatable, P2P, decentralized, liquid economy, with _0 platform fees, 0 dev taxes_ and _0 targets_.**
+
+**I would hope (and assume) that non-monero communities who are under constant threat for having cypherpunk ideals (_cough_ BTC, BCH, ETH, and whoever else shares our ideals) will also support and donate to this endeavor.**

plowsof-ccs-coordinator-2.md

+---
+layout: cp
+title: "CCS Coordinator"
+author: plowsof
+date: April 20th 2023
+amount: 69
+milestones:
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 27 June 2023
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 20 August 2023
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 16 October 2023
+    status: finished
+payouts:
+  - date: 19 July 2023
+    amount: 23
+  - date: 12 September 2023
+    amount: 23
+  - date: 3 November 2023
+    amount: 23
+---
+
+# Who?
+
+Hello, plowsof here, I show up and try to be helpful. My [previous proposal](https://ccs.getmonero.org/proposals/plowsof-com-rel.html) happened, i would like to make it happen again, and do more of the same things.
+
+# What?
+
+- Gather consensus for CCS proposals. (feedback from GitLab/IRC/Reddit).
+- Organise bi-weekly meetings to discuss proposals / current events (more if necessary).
+- Provide decisions in 1 month or less (Yes/No to being funded or if something has to be changed with the proposal to satisfy our community).
+- Be impartial when communicating with CCS proposers - everyone gets a fair shake.
+- Checking up on the WIP list to find / fix problems early (e.g. payments overdue or proposers AWOL).
+    - It has recently came to my attention that there is a seldom enforced CCS rule where "If it's not funded or finished by a certain time, the funds can be released to other proposals or the General Fund.. This keeps things moving along in a timely fashion.", one of my tasks will be to gather support for enforcing this rule where applicable.
+- Take responsibility for the entire CCS process - It's my fault when 'things go wrong'.
+- Someone who is online for several hours a day / 7 days a week that knows what's going on.
+- Act as a liaison to Core - keep them informed of whats happening / poke them when required / handle their requests.
+    - As part of this CCS, you will also be sponsoring my work when quality assurance testing new features/bug fixes each release cycle in the GUI, CLI, and RPC wallets.
+    - And Getmonero.org contributions.
+- Consultancy before / during / after the idea stage.
+
+# Funding
+
+20hr/week - 40 eur/hr with XMR at 145EUR (MA20 @ Kraken) gives 72 but i like 69 better so 23 XMR/milestone bringing the total requested amount to 69XMR. Maximum of 1 milestone can be claimed per month. Price fluctuation after moving to funding will have no effect.
+Consider this proposal expired in the event of my untimely death / unheard of for >5 months / have not claimed all payouts in 12 months. If expired - all remaining unclaimed funds are to be donated to other CCS proposals.

plowsof-ccs-coordinator-3.md

+---
+layout: cp
+title: "CCS Coordinator"
+author: plowsof
+date: October  20th 2023
+amount: 69
+milestones:
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 14 January 2024
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 14 January 2024
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 17 March 2024
+    status: finished
+payouts:
+  - date: 28 January 2024
+    amount: 46
+  - date: 16 April 2024
+    amount: 23
+---
+
+# Who?
+
+Hello, plowsof here, I show up and try to be helpful. My [previous](https://ccs.getmonero.org/proposals/plowsof-com-rel.html) [proposals](https://ccs.getmonero.org/proposals/plowsof-ccs-coordinator-2.html) happened, i would like to make it happen again, and do more of the same things.
+
+# What?
+
+- Gather consensus for CCS proposals. (feedback from GitLab/IRC/Reddit).
+- Organise bi-weekly meetings to discuss proposals / current events (more if necessary).
+- Provide decisions in 1 month or less (Yes/No to being funded or if something has to be changed with the proposal to satisfy our community).
+- Be impartial when communicating with CCS proposers - everyone gets a fair shake.
+- Checking up on the WIP list to find / fix problems early (e.g. payments overdue or proposers AWOL).
+- Take responsibility for the entire CCS process - It's my fault when 'things go wrong'.
+- Someone who is online for several hours a day / 7 days a week that knows what's going on.
+- Act as a liaison to Core - keep them informed of whats happening / poke them when required / handle their requests.
+    - As part of this CCS, you will also be sponsoring my work when quality assurance testing new features/bug fixes each release cycle in the GUI, CLI, and RPC wallets.
+    - And Getmonero.org contributions.
+- Consultancy before / during / after the idea stage.
+
+# Funding
+
+20hr/week - 40 eur/hr with XMR at 144EUR (MA20 @ Kraken) gives 72.420 but i like 69 better so 23 XMR/milestone bringing the total requested amount to 69XMR. Maximum of 1 milestone can be claimed per month. Price fluctuation after moving to funding will have no effect.
+Consider this proposal expired in the event of my untimely death / unheard of for >5 months / have not claimed all payouts in 12 months. If expired - all remaining unclaimed funds are to be donated to other CCS proposals.

plowsof-ccs-coordinator-4.md

+---
+layout: cp
+title: "CCS Coordinator"
+author: plowsof
+date: March 29th 2024
+amount: 80.07
+milestones:
+  - name: 2 meetings + hours worked
+    funds: 26.69 XMR
+    done: 2 June 2024
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 26.69 XMR
+    done: 2 June 2024
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 26.69 XMR
+    done: 5 September 2024
+    status: finished
+payouts:
+  - date: 24 June 2024
+    amount: 26.69
+  - date: 24 June 2024
+    amount: 26.69
+  - date: 28 September 2024
+    amount: 26.69
+---
+
+# Who?
+
+Hello, plowsof here, I show up and try to be helpful. My [previous](https://ccs.getmonero.org/proposals/plowsof-com-rel.html) [proposals](https://ccs.getmonero.org/proposals/plowsof-ccs-coordinator-2.html) [happened](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/418), i would like to make it happen again, and do more of the same things.
+
+# What?
+
+- Gather consensus for CCS proposals. (feedback from GitLab/IRC/Reddit).
+- Organise bi-weekly meetings to discuss proposals / current events (more if necessary).
+- Provide decisions in 1 month or less (Yes/No to being funded or if something has to be changed with the proposal to satisfy our community).
+- Be impartial when communicating with CCS proposers - everyone gets a fair shake.
+- Checking up on the WIP list to find / fix problems early (e.g. payments overdue or proposers AWOL).
+- Take responsibility for the entire CCS process - It's my fault when 'things go wrong'.
+- Someone who is online for several hours a day / 7 days a week that knows what's going on.
+- Act as a liaison to Core - keep them informed of whats happening / poke them when required / handle their requests.
+    - As part of this CCS, you will also be sponsoring my work when quality assurance testing new features/bug fixes each release cycle in the GUI, CLI, and RPC wallets.
+    - And Getmonero.org contributions.
+- Consultancy before / during / after the idea stage.
+- Secretarial tasks for https://bounties.monero.social/ (requesting payouts upon completion of bounties and such)
+
+# Funding
+
+20hr/week - 40 eur/hr with XMR at 126EUR (MA20 @ Kraken) gives 20 * 13 * (40/126) = 80.5 but i like 80.07 better so 26.69 XMR/milestone bringing the total requested amount to 80.07XMR. Maximum of 1 milestone can be claimed per month. Price fluctuation after moving to funding will have no effect.
+Consider this proposal expired in the event of my untimely death / unheard of for >5 months / have not claimed all payouts in 12 months. If expired - all remaining unclaimed funds are to be donated to other CCS proposals.

plowsof-com-rel.md

+---
+layout: cp
+title: "CCS Coordinator (3 months)"
+author: plowsof
+date: 29 October 2022
+amount: 69
+milestones:
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 31 December 2022
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 31 January 2023
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 11 March 2023
+    status: finished
+payouts:
+  - date: 4 January 2023
+    amount: 23
+  - date: 2 February 2023
+    amount: 23
+  - date: 23 March 2023
+    amount: 23
+---
+
+# What?
+
+- Gather consensus for CCS proposals. (feedback from GitLab/IRC/Reddit).
+- Organise bi-weekly meetings to discuss proposals / current events (more if necessary).
+- Provide decisions in 1 month or less (Yes/No to being funded or if something has to be changed with the proposal to satisfy our community).
+- Be impartial when communicating with CCS proposers - everyone gets a fair shake.
+- Checking up on the WIP list to find / fix problems early (e.g. payments overdue or proposers AWOL).
+    - It has recently came to my attention that there is a seldom enforced CCS rule where "If it's not funded or finished by a certain time, the funds can be released to other proposals or the General Fund.. This keeps things moving along in a timely fashion.", one of my tasks will be to gather support for enforcing this rule where applicable.
+- Take responsibility for the entire CCS process - It's my fault when 'things go wrong'.
+- Someone who is online for several hours a day / 7 days a week that knows what's going on.
+- Act as a liaison to Core - keep them informed of whats happening / poke them when required / handle their requests.
+    - As part of this CCS, you will also be sponsoring my work when quality assurance testing new features/bug fixes each release cycle in the GUI, CLI, and RPC wallets.
+    - And Getmonero.org contributions.
+- Consultancy before / during / after the idea stage.
+
+# Who?
+
+I voluntarily took on this role for a few weeks (several months ago) and detailed my progress [here](https://www.reddit.com/r/Monero/comments/uj0lyu/what_i_did_last_week_plowsof/). Soon after, I 'retired'. Since then, i've been doing this role at half capacity. A member of Core has seen value in my contributions and asked me to make this CCS and also provide some other work around the ecosystem which i would be unable to do consistently without being sponsored by the community. 
+
+My other contributions include:
+
+- Monero GUI Packager - from v0.18.1.0 every GUI installer for windows is packaged by one of my scripts. I've also automated the creation of the .zip and .tar.bz2 files for selsta, so instead of 'copy and pasting files' they can focus on important tasks for release. A public version to create the installer is [here](https://github.com/plowsof/monero-gui-exe)
+- Merged PR's in (a really minor bug fix)[Monero GUI](https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+is%3Amerged+author%3Aplowsof) and [Monero Site]( https://github.com/monero-project/monero-site/pulls?q=is%3Apr+is%3Amerged+author%3Aplowsof+)
+- Self-hosted wishlists, examples at [monerujo](https://funding.monerujo.app/) [monerochan.art](https://www.monerochan.art/) and [XMR.radio](https://xmr.radio/)
+later on i created a multi-coin version. examples at [Rucknium.me](https://rucknium.me/donate/) and [ofrnxmr](https://getwishlisted.xyz/ofrnxmr/)
+- General Fund twitter bot, that tweets every donation received https://nitter.it/watchfund
+- Daily updated list of public ZMQ servers [here](https://github.com/plowsof/listen_for_zmq/blob/main/zmq_list.md) for [xmrvsbeast](https://xmrvsbeast.com/p2pool/monero_nodes.html)
+- [monerodevs.org](http://www.monerodevs.org/) - 'handmade feel' to put it nicely, also needs updating.
+- Set up [MoneroResearch.info](https://moneroresearch.info/) with Rucknium
+- I provide tech support / post PSA's when needed on Reddit at https://www.reddit.com/user/KnowledgeMurky9635 
+
+# Milestones
+Some concrete areas to be judged on will be my ability to obtain decisions (yes / no / change this) from the community in 1 month or less by organising at least 2 meetings per month and gathering feedback.    
+Monthly reports will detail what i've been doing in terms of checking up on the WIP list / working with people at the ideas stage / helping where i am able to.    
+As for the liaising with Core part, if at any point they are not satisfied, then this proposal can be terminated with immediate effect (no payout for 'work done' either)
+
+# Funding
+20hr/week - 40 eur/hr with XMR at 147EUR (MA20 @ Kraken) gives 23 XMR/milestone bringing the total requested amount to 69XMR. Maximum of 1 milestone can be claimed per month. Price fluctuation after moving to funding will have no effect.
+Consider this proposal expired in the event of my untimely death / unheard of for >5 months / have not claimed all payouts in 12 months. If expired - all remaining unclaimed funds are to be donated to other CCS proposals.

plowsof_6_ccs_coordinator.md

+---
+layout: wip
+title: plowsof CCS Coordinator 
+author: plowsof
+date: April 1, 2025
+amount: 72.60
+milestones:
+  - name: Month 1
+    funds: 24.2
+    status: unfinished
+    done:
+  - name: Month 2
+    funds: 24.2
+    status: unfinished
+    done:
+  - name: Month 3
+    funds: 24.2
+    status: unfinished
+    done:
+payouts:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+# Who?
+
+Hello, plowsof here, I show up and try to be helpful. My [previous](https://ccs.getmonero.org/proposals/plowsof-com-rel.html) [proposals](https://ccs.getmonero.org/proposals/plowsof-ccs-coordinator-2.html) [happened](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/418), [previously](https://ccs.getmonero.org/proposals/plowsof-ccs-coordinator-4.html) [again](https://ccs.getmonero.org/proposals/ccs-coordinator-5-plowsof.html). I would like to make it happen again, and do more of the same things.
+
+# What?
+
+- Gather consensus for CCS proposals. (feedback from GitLab/IRC/Reddit).
+- Organise bi-weekly meetings to discuss proposals / current events (more if necessary).
+- Provide decisions in 1 month or less (Yes/No to being funded or if something has to be changed with the proposal to satisfy our community).
+- Be impartial when communicating with CCS proposers - everyone gets a fair shake.
+- Checking up on the WIP list to find / fix problems early (e.g. payments overdue or proposers AWOL).
+- Take responsibility for the entire CCS process - It's my fault when 'things go wrong'.
+- Someone who is online for several hours a day / 7 days a week that knows what's going on.
+- Act as a liaison to Core - keep them informed of whats happening / poke them when required / handle their requests.
+    - As part of this CCS, you will also be sponsoring my work when quality assurance testing new features/bug fixes each release cycle in the GUI, CLI, and RPC wallets.
+    - And Getmonero.org contributions.
+- Consultancy before / during / after the idea stage.
+- Secretarial tasks for https://bounties.monero.social/ (requesting payouts upon completion of bounties and such)
+
+
+## Proposal
+Work for 25 hours per week over the next 3 months (from April to end of June 2025) at a rate of 45€ / hour. At 201.72€ / XMR (90-day EMA) this makes ~72.60 XMR.

r4v3r23-anonero-v1.md

+---
+layout: wip
+title: ANONERO version 1.0
+author: r4v3r23
+date: April 12, 2024
+amount: 199.265
+milestones:
+  - name: Inital payment
+    funds: 20% (39.853 XMR)
+    done: 29 April 2024
+    status: finished
+  - name: Payment for first test build
+    funds: 40 % (79.706 XMR)
+    done:
+    status: unfinished
+  - name: Payment for completion
+    funds: 40 % (79.706 XMR)
+    done:
+    status: unfinished
+payouts:
+  - date: 29 April 2024
+    amount: 39.853
+  - date:
+    amount:
+---
+
+
+
+# Who
+
+ANONERO project, creators of the security & privacy focused Monero wallets ANON & NERO.
+
+# What
+
+
+Migrating our codebase to Android's native language Kotlin with Jetpack Compose UI. 
+
+When we first started the project, we bootstrapped development by using a combination of xmrwallet's Java code and Flutter. This allowed for fast interations and great UI performance, but as the app grew with more advanced features, the Native <> Java <> Flutter layers proved to be a bottleneck.
+
+Now that we have a working Proof of Concept alpha wallet, and are much more familiar with the Monero codebase, we've decided to move the app to a new framework that's better suited to our feature set. This will give us a solid, stable codebase and make future developement much easier.
+
+As part of our commitment to privacy & security and using the latest features, ANONERO has contributed to Monero, directly and indirectly, in various ways:
+
+ 1) First fully airgapped DIY HWW cold storage solution: https://monero.town/post/223593
+ 
+ 2) First working implementation of background sync via view-keys
+
+ 3) Helped identify, debug, and fix issue where Polyseed was failing to build on 32-bit Android: https://github.com/tevador/polyseed/issues/5
+
+ 4) Helped identify, debug, and test fix for the DNS leak when using onion nodes: https://github.com/monero-project/monero/pull/8849
+ 
+ 5) Helped discover bug where key images weren't being passed by signed tx payload: https://github.com/monero-project/monero/pull/9049
+ 
+ 6) Discovered background sync bug which caused all cached blocks to be erased: https://github.com/monero-project/monero/pull/8619#issuecomment-1808920063
+ 
+ 7) Helped test tobtoht's upcoming [Polyseed](https://github.com/tevador/polyseed) patch to monero core
+ 
+ 8) Worked with tobtoht to improve offline-signing UX
+ 
+We'll continue to adopt and test new features and upstream fixes to core if/when they arise during the CCS.
+
+# Proposal
+
+Instead of guesstimating work hours and giving an hourly rate, we are asking for an amount that will guarantee funding for the entire wallet rewrite. 
+
+Monerujo's Sidekick project raised 181.15 XMR, and seeing as we addressed the community's concerns by shipping the feature fully airgapped using animated QR codes, we are asking the community to match that amount, plus 10% for misc things like hosting, documentation, website improvement etc for a total of 199.265 XMR.  
+
+For the past year and a half we relied on our small community to help fund us, and now that we've proven we can deliver, we are requesting 20% upfront to start development:
+ 
+- Milestone 1:  39.853 XMR (20%) paid upfront upon funding
+  
+- Milestone 2:  79.706 XMR (40%) paid upon release of first test build (corresponding to v0.5)
+
+- Milestone 3:  79.706 XMR (40%) paid upon final feature-complete release
+
+Progress will be posted on our repo http://git.anonero.io (onion redirect) and we will begin open testing as soon as we can.
+
+CCS will expire one year from date of first payout and funds can be send to the General Fund.

rating89us-1.md

+---
+layout: cp
+title: rating89us part-time Monero GUI UI/UX development (3 months)
+author: rating89us
+date: 30 June 2021
+amount: 48.31
+milestones:
+  - name: July
+    funds: 33% (16.10 XMR)
+    done: 15 August 2021
+    status: finished
+  - name: August
+    funds: 33% (16.10 XMR)
+    done: 15 September 2021
+    status: finished
+  - name: September
+    funds: 33% (16.11 XMR)
+    done: 30 November 2021
+    status: finished
+payouts:
+  - date: 6 December 2021
+    amount: 48.31
+---
+
+## What
+
+Hi, everyone! I am rating89us and this is my first CCS proposal. I have been doing voluntary (unpaid) contributions to Monero GUI on my free time since 2020, adding new UI elements, improving UX and fixing bugs. While Monero GUI has improved a lot during the last years, there is still a lot of work to be done. I'm really motivated in making Monero GUI easy to use by anyone.
+
+Some things I want to work on:
+-	General: add tooltips where still necessary, improve displaying of wallet > accounts hierarchy, discreet mode (hide amounts/balances on all pages); implement tip of the day popup; implement user onboarding popups when the wallet is opened for the first time
+-	LeftPanel: redesign synchronization progress bars, Socks5 proxy/TOR icon
+- Send: display "All" amount as a label with close button
+-	Address book: user avatars, sorting
+-	Transactions: amount filtering, sent/received filtering, historical fiat price
+-	Settings: create a dedicated page to synchronization process, redesign Node page, add "change restore height" menu item
+-	Merchant: redesign merchant page, UI/UX for tablets/smartphones
+-	Wizard: redesign hardware wallet page, create a dedicated page to seed and restore height
+-	Accessibility: add description/navigation for UI elements (support screen readers for visually impaired users)
+-	White theme: improve color contrast of UI elements
+-	Upgrade FontAwesome icons to last version
+-	Android: test and improve UI/UX for tablets/smartphones
+-	Test and review UI/UX pull requests
+-	Update text and screenshots of Monero GUI guides (pdf guide and getmonero.org user guides)
+
+## Who
+
+rating89us, I have been contributing voluntarily to Monero GUI since 2020 with over 77 merged commits. 
+
+Here is a list of my previous merged commits on Monero GUI:
+- Pull requests: https://github.com/monero-project/monero-gui/pulls?page=1&q=is%3Apr+author%3Arating89us+is%3Aclosed
+- Commits: https://github.com/monero-project/monero-gui/commits?author=rating89us
+
+If funded I will provide monthly updates in the CCS comment section.
+
+## Proposal
+
+Work for 20 hours per week over the next 3 months (from Mid July to Mid October) at a rate of 38€/hour. At 188.75€/XMR on Kraken (14-day EMA) this makes 48.31 XMR.

rehrar-help-out.md

+---
+layout: wip
+title: rehrar help the project
+author: rehrar
+date: June 29, 2024
+amount: 75
+milestones:
+  - name: Month 1
+    funds: 25
+    done: 23 August 2024
+    status: finished
+  - name: Month 2
+    funds: 25
+    done:
+    status: unfinished
+  - name: Month 3
+    funds: 25
+    done:
+    status: unfinished
+payouts:
+  - date: 26 August 2024
+    amount: 25
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+# Who, what, when, where?
+
+Hi, I'm Diego "rehrar" Salazar. I run [Cypher Stack](https://cypherstack.com), and me and my team make [Stack Wallet](https://stackwallet.com). I also did work for the core team once upon a time.
+
+I was recently approached my luigi, of the current core team about retaking on some of my old duties. There's a lot of opportunity for improvement in the non-dev areas of the project, and not always enough hands to get it done. It was agreed upon that, were this to happen, this would be done through the CCS rather than through Core as before. This moves me from being accountable to core, to accountable to the community.
+
+A quick summary of what I'd be working on (requested by luigi):
+- Presiding over and helping along a Monero Website Workgroup to merge requests, keep it up to date, and do odds and ends of design and development
+- Facilitating moderator relationships and fostering community in relevant social platforms
+- Being a leader in the Monero Community workgroup and helping that along as needed
+- Keeping a finger on the "pulse of the community" in the various chat rooms and platforms (Telegram, Discord, IRC, Matrix, Reddit, etc.)
+- Assisting plowsof as needed in CCS work (working under him for various tasks if needed)
+- Aiding and assisting in event work as needed
+- Utilizing my "soft skills" as needed elsewhere on the project.
+
+# Why?
+There's lots of non-dev stuff to do, and not so many people to do it. I am capable and willing.
+
+# How long? How much?
+
+75 XMR for three months for half time work. Possibility of renewal depending on community sentiment.
+
+# Deliverables
+I will do all of the above in the beginning section, and give a monthly report to the community on what's been done, and tasks accomplished. The primary metric I will rate myself on though, is how big of a help I am to luigi in terms of taking workload off of his shoulders.
+
+# COI
+My company Cypher Stack does occassional work for Monero in the form of the following:
+- Dan "pigeons" Miller who helps with infrastructure work is employed by Cypher Stack. We typically do anywhere from 5-10 hours a month for Monero here. We are currently doing this work pro bono.
+- Cypher Stack's cryptographer, Aaron Feickert, does occassional research work for Monero. This is funded either by the CCS, or the new Research Fund that has been funded by the CCS.
+- I own and operate Stack Wallet, an open-source, multicoin wallet, of which Monero is supported.
+- I and all of my employees do occassional work for other clients, many of them in the privacy or crypto sphere. Several of them privacy coins themselves.
\ No newline at end of file

revuo-monero-maintenance-2024-q3.md

+---
+layout: cp
+title: Revuo Monero maintenance (2024 Q3)
+author: rottenwheel
+date: June 3, 2024
+amount: 8
+milestones:
+  - name: July
+    funds: 3
+    done: 2 August 2024
+    status: finished
+  - name: August
+    funds: 3
+    done: 5 September 2024
+    status: finished
+  - name: September
+    funds: 2
+    done: 1 October 2024
+    status: finished
+payouts:
+  - date: 12 August 2024
+    amount: 3
+  - date: 10 September 2024
+    amount: 3
+  - date: 2
+    amount: 7 October 2024
+---
+
+# What
+
+I will maintain Revuo Monero (https://www.revuo-xmr.com/) for the next 3 months (2024 Q3): July, August and September. There is a chance I may skip one week to tend to real life issues, in such case, next issue will just cover 2 weeks instead of 1.
+
+Tasks:
+
+- Daily/weekly: search, curate, structure and post new reports/stories.
+- As Needed: outreach (engage with the community on Matrix, XMPP, emails).
+- As Needed: make sure the website is live and working as expected (server maintenance, billing, etc.)
+
+# Who
+
+rottenwheel, I joined the Monero community some time in 2017 by jumping into IRC, attending some Workgroup meetings, volunteering at the Monero village at DEFCON 28 in 2019 (https://redlib.zaggy.nl/r/Monero/comments/cqegma/monero_village_defcon_2019_report/), participating in community events and being involved with other community-driven, smaller projects.
+
+As a proof of work for this specific proposal, I have, since January 2022 until now, written almost 200 issues, 195 of which were published in current Revuo's self-hosted website. That does not take into account the following enhancements.
+
+Up to this point, all efforts behind Revuo Monero's comeback after Diego "rehrar" Salazar was let go and Revuo Monero's publication was paused for a few months, include but are not limited to:
+
+- Light/dark theme with a toggle button (mostly in CSS/HTML, minimizing the reliance in JavaScript as much as possible; site loads everything just fine in Tor browser with strict security mode on.)
+- Support and Source Code sections added.
+- RSS and Support icons.
+- Google fonts removed.
+- Twitter and Nostr profiles set up and posting new issues every week automatically. Twitter: https://nitter.poast.org/revuoxmr; Nostr: https://primal.net/p/npub1tn8spk9zhxrctg2qym3gj8r7eq2wk6z3phrl8304wc54vt9qam4qvzw6jx
+
+# Proposal
+
+I will publish weekly issues (4 per month) at a rate of $100 / issue. At $157.5 / XMR this makes 8 XMR (~7.6++) (100 * 4 * 3 = $1200) to be split in 3 monthly milestones. Rounding current 7.6++ XMR to 8 XMR to cover for price votatility between Work In Progress phase and progressive milestone(s) payouts.
\ No newline at end of file

revuo-monero-maintenance-2024-q4.md

+---
+layout: cp
+title: Revuo Monero maintenance (2024 Q4)
+author: rottenwheel
+date: September 2, 2024
+amount: 8.5
+milestones:
+  - name: October
+    funds: 3
+    done: 1 November 2024
+    status: finished
+  - name: November
+    funds: 3
+    done: 28 November 2024
+    status: finished
+  - name: December
+    funds: 2.5
+    done: 26 December 2024
+    status: finished
+payouts:
+  - date: 12 November 2024
+    amount: 3
+  - date: 6 December 2024
+    amount: 3
+  - date: 12 January 2025
+    amount: 2.5
+---
+
+# What
+
+I will maintain Revuo Monero (https://www.revuo-xmr.com/) for the next 3 months (2024 Q4): October, November and December. There is a chance I may skip one week to tend to real life issues, in such case, next issue will just cover 2 weeks instead of the usual 1.
+
+Tasks:
+
+- Daily/weekly: search, curate, structure and publish new issues.
+- As Needed: outreach (engage with the community on Matrix, XMPP, e-mails, social media, Workgroup channels).
+- As Needed: make sure the website is live and working as expected (server maintenance, billing, etc.)
+- As Needed: cover code enhancements/fixes expenses, sysadmin consultations and additional Revuo tools/services for the community. 
+
+# Who
+
+rottenwheel, I joined the Monero community some time in 2017 by jumping into IRC, attending some Workgroup meetings, volunteering at the Monero village at DEFCON 28 in 2019 (https://redlib.zaggy.nl/r/Monero/comments/cqegma/monero_village_defcon_2019_report/), participating in community events and being involved with other community-driven, smaller projects.
+
+As a proof of work for this specific proposal, I have, since January 2022 until now, written almost 200 issues, 195 of which were published in current Revuo's self-hosted website. That does not take into account the following enhancements.
+
+Up to this point, all efforts behind Revuo Monero's comeback after Diego "rehrar" Salazar was let go and Revuo Monero's publication was paused for a few months, include but are not limited to:
+
+- Light/dark theme with a toggle button (mostly in CSS/HTML, minimizing the reliance in JavaScript as much as possible; site loads everything just fine in Tor browser with strict security mode on.)
+- Support and Source Code sections added.
+- RSS and Support icons.
+- Google fonts removed.
+- Twitter and Nostr profiles set up and posting new issues every week automatically. Twitter: https://nitter.poast.org/revuoxmr; Nostr: https://primal.net/p/npub1tn8spk9zhxrctg2qym3gj8r7eq2wk6z3phrl8304wc54vt9qam4qvzw6jx
+
+**New**: Revuo Calc, a moner.ooo fork that had its original code shrunk by half (# of total lines), improved upon and it offers 2 versions, adjusted according visitor's browser settings: JavaScript-free front and JavaScript-friendly front; think of Tor users and clearnet users. The cherry on top? Its own subdomain hidden service as well. See: https://calc.revuo-xmr.com/ // Source code: https://github.com/rottenwheel/moner.ooo/ 
+
+# Proposal
+
+I will publish weekly issues (4 per month) at a rate of $120 / issue. Using MA10 - Moving Average 10 (10 days) of ~$170 / XMR at the time of writing this proposal, this makes for **8.5 XMR** (~8.47058++...) [(120 * 4) * 3 = $1440) to be split in three (3) monthly milestones. Rounding ~8.47058++... XMR to 8.5 XMR to cover for price votatility between Work In Progress phase and progressive milestone(s) payouts.

revuo-monero-maintenance-2025-q1.md

+---
+layout: wip
+title: Revuo Monero maintenance (2025 Q1)
+author: rottenwheel
+date: December 26, 2024
+amount: 8
+milestones:
+  - name: January
+    funds: 3
+    done: 10 February 2025
+    status: finished
+  - name: February
+    funds: 3
+    done: 3 March 2025
+    status: finished
+  - name: March
+    funds: 2
+    done:
+    status: unfinished
+payouts:
+  - date: 24 February 2025
+    amount: 3
+  - date: 19 March 2025
+    amount: 3
+  - date:
+    amount:
+---
+
+# What
+
+I will maintain Revuo Monero (https://www.revuo-xmr.com/) for the next 3 months (2025 Q1): January, February and March. There is a chance I may skip one week to tend to real life issues, in such case, next issue will just cover 2 weeks instead of the usual 1.
+
+Tasks:
+
+- Daily/weekly: search, curate, structure and publish new issues.
+- As Needed: make sure the website is live and working as expected (server maintenance, billing, etc.)
+- As Needed: cover code enhancements/fixes expenses, sysadmin consultations and additional Revuo tools/services for the community. 
+
+# Who
+
+rottenwheel, I joined the Monero community some time in 2017 by jumping into IRC, attending some Workgroup meetings, volunteering at the Monero village at DEFCON 28 in 2019 (https://redlib.zaggy.nl/r/Monero/comments/cqegma/monero_village_defcon_2019_report/), participating in community events and being involved with other community-driven, smaller projects.
+
+As a proof of work for this specific proposal, I have, since January 2022 until now, written more than two hundred (200) weekly issues of the Revuo Monero newsletter, the first five (5) first published and hosted at [LocalMonero](https://localmonero.co/revuo) and the rest, 200++, were published in current Revuo's self-hosted website. About 24-25 of them had their maintenance and editorial work funded through the CCS, for 2024 Q3 and Q4; now looking to get funding secured for 2025 Q1 with this proposal. Beyond that, I have completed and deployed the following enhancements:
+
+Up to this point, all efforts behind Revuo Monero's comeback after Diego "rehrar" Salazar was let go and Revuo Monero's publication was paused for a few months, include but are not limited to:
+
+- Light/dark theme with a toggle button (mostly in CSS/HTML, minimizing the reliance in JavaScript as much as possible; site loads everything just fine in Tor browser with strict security mode on.)
+- Support and Source Code sections added.
+- RSS and Support icons.
+- Google fonts removed.
+- Twitter profile set up and posting new issues every week automatically, which often get reposted via @monero main account. Twitter: https://nitter.poast.org/revuoxmr
+- Addition of RM's group chats and social media profile links at the bottom of hamburger menu. Nostr, X, XMPP, Matrix, SimpleX and IRC.
+
+**New**: Revuo Calc. See: https://calc.revuo-xmr.com/ // Source code: https://github.com/rottenwheel/moner.ooo/ 
+[WIP] Moneroj.net maintenance and enhancements. Almost ready for relaunch/announcement, under Revuo's umbrella, as Revuo Moneroj.
+
+# Proposal
+
+I will publish weekly issues (4 per month, average) at a rate of $120 / issue. Using MA10 - Moving Average 10 (10 days) of ~$191 / XMR at the time of writing this proposal, this makes for **8 XMR** (~7.5392++...) [(120 * 4) * 3 = $1440) to be split in three (3) monthly milestones. Rounding ~7.5392++... XMR to 8 XMR even to cover for price votatility between Work In Progress phase and progressive milestone(s) payouts.

savandra-videos-for-monero.md

+---
+layout: cp
+title: New Animated Videos
+author: savandra
+date: April 7, 2022
+amount: 45
+milestones:
+  - name: Complete Video 1
+    funds: 20% (9 XMR)
+    done: 22 March 2023
+    status: finished
+  - name: Complete Video 2
+    funds: 20% (9 XMR)
+    done:
+    status: unfinished
+  - name: Complete Video 3
+    funds: 20% (9 XMR)
+    done:
+    status: unfinished
+  - name: Complete Video 4
+    funds: 20% (9 XMR)
+    done:
+    status: unfinished
+  - name: Complete Video 5
+    funds: 20% (9 XMR)
+    done:
+    status: unfinished
+payouts:
+  - date: 3 April 2023
+    amount: 9
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+### Proposal closed
+
+The remaining funds (36XMR) have been absorbed by https://ccs.getmonero.org/proposals/VOSTOEMISIO-Continuation-of-Core-Monero-Concepts-A-Series-of-Animated-Explainers.html
+
+Hello guys,
+
+It's savandra, who created animated explainer videos,
+
+here's a link to our channel.
+
+I contacted u/dsmlegend, https://www.reddit.com/u/dsmlegend/ and he developed an awesome draft of probably anything should be covered on the topic (though it's a bit business-focused).
+
+Here's a link to the document https://www.youtube.com/channel/UCnjUpT9gGxyQ_lud7uKoTCg
+
+I'd like to add, that since then, we improved on the animations a lot and we hope Monero will benefit from it!
+
+
+Our proposal is to be billed per minute of the animation, which covers:
+
+script development ( with implementing all the feedback from the community)
+
+illustrations development
+
+animations
+
+voice-over
+
+sound effects
+
+Considering the above, I think $400 per minute of the animation should work out nicely.
+Also, it's been a while since the last video, so let me know if there are any updates on how the pitch should be handled.
+
+It is expected to complete one video a month
+An expiration date for the proposal: June, 7