jeffro256-full-time-2024Q4.md

+---
+layout: cp
+title: jeffro256 full-time development 2024Q4
+author: jeffro256
+date: September 16, 2024
+amount: 144
+milestones:
+  - name: Month 1
+    funds: 33% (48.0)
+    done: 9 November 2024
+    status: finished
+  - name: Month 2
+    funds: 33% (48.0)
+    done: 12 December 2024
+    status: finished
+  - name: Month 3
+    funds: 33% (48.0)
+    done: 14 January 2025
+    status: finished
+payouts:
+  - date: 12 November 2024
+    amount: 48
+  - date: 12 January 2025
+    amount: 48
+  - date: 23 January 2025
+    amount: 48
+---
+
+## What
+
+The last quarter I began implementing [Jamtis-RCT](https://gist.github.com/tevador/d3656a217c0177c160b9b6219d9ebb96), as written by tevador. However, with the FCMP++ integration PR opened against master, and upon discussion of the general health of wallet development in the broader ecosystem, it became readily apparent that the way to move forward is to initially support existing Monero addresses in a way that would be indistinguishable on-chain from Jamtis-RCT, adding full Jamtis-RCT support later. As such, I formulated the [Carrot specification](https://github.com/jeffro256/carrot/blob/master/carrot.md), which expanded upon the legacy address section in tevador's original Jamtis-RCT proposal. I contacted and conducted meetings with auditors in regards to auditing this spec, which culminated in several proposals. I also implemented transaction scanning code and transaction construction code for Carrot. I would like to continue this work for the next few months ahead of the hardfork. The main things to work on for Carrot at this point are 1) persistent enote stores for both legacy and Carrot scan types together, 2) integration into the main wallet codepaths, 3) hardware device support, and 4) picking and organizing an auditor to move forward with. Ideally, there should also come a point in the near future where the implementation is reviewed against the audited specification. I wish the development of Carrot generally to be swift, in order not to impede the release date of the FCMP++ consensus protocol. It should be noted that if the current addressing protocol is not modified, then users' transactions will *not* be afforded conditional forward secrecy. This would mean that a potential future adversary with the ability to solve the decisional Diffie-Helman problem (e.g. a usable quantum computer) would be able to retroactively reveal the transaction graph without any obfuscation. Carrot, like Jamtis-RCT, leverages the forward secrecy property of FCMP++ while also tackling other issues like the burning bug, Janus attacks, etc. If all goes well, the adoption of Carrot will seamlessly move Monero users into the full realization of the privacy and security that the FCMP++ proving system has to offer. 
+
+To recap, here is a list of things I will attempt to work on this quarter, in rough order of execution:
+
+- Finalize Carrot spec audit
+- Implement Carrot enote store
+- Implement Carrot hardware device support
+- Integrate Carrot into main wallet codepaths
+- Begin soliciting Carrot implementation audit
+
+P.S. To all the generous supporters of my previous proposals, I apologize that the direction of my work has shifted so significantly and so frequently in the past. So many developments have occurred within the last year that it makes my head spin, which in the end will no doubt be a good thing. So while a lot of previous goals have been abandoned, and a lot of previous work put on ice indefinitely, things seem to be finally solidifying towards a forseeable, readily-achieveable outcome in regards to the upcoming hardfork, thanks to many hard-working contributors. Hopefully, all of the work for this quarter will actually see the light of day in the short to medium term. Thanks for your patience. I am very grateful for it.
+
+## Who
+
+I have been contributing to the Monero core repository for [over two years](https://github.com/monero-project/monero/pulls?page=2&q=is%3Apr+author%3Ajeffro256) with a total of [76 merged commits to master](https://github.com/monero-project/monero/commits?author=jeffro256) thus far, with many open PRs. I also began working on the Seraphis migration project, so you can see some of my contributions [here](https://github.com/seraphis-migration/monero/pulls?q=is%3Apr+author%3Ajeffro256) and [here](https://github.com/UkoeHB/monero/pulls?q=is%3Apr+author%3Ajeffro256). Additionally, as I mentioned, last quarter I wrote up the [Carrot specification](https://github.com/jeffro256/carrot/blob/master/carrot.md) for formal auditing, which will be the main addressing protocol post-FCMP++ if all goes according to plan.
+
+Previous Proposals:
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/319
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/390
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/421
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/436
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/467
+
+## Payment
+
+I propose to work 40 hours/week for 3 months so `40 (hours/week) * 3 (months) * weeks_per_month = 40 (hours/week) * 3 (months) * (365 / 12 / 7) (weeks/month) = 521` hours total on-paper, though I usually work more than that. The proposal is broken into 3 milestones, one for each month. I am setting my hourly rate at 47 USD/hour (+1 USD/hour higher than last quarter), and at a market price of 170.37 USD/XMR, that makes for a total of 143.7 XMR. Price was calculated as 14-day simple average of opening prices on [CoinGecko](https://www.coingecko.com/en/coins/monero/historical_data) from 2024-09-04 to 2024-09-17 (day of writing), same as last quarter.
+

jeffro256-full-time-2025Q1.md

+---
+layout: wip
+title: jeffro256 full-time development 2025Q1
+author: jeffro256
+date: January 27, 2025
+amount: 114
+milestones:
+  - name: Month 1
+    funds: 33% (38.0)
+    done: 18 February 2025
+    status: finished
+  - name: Month 2
+    funds: 33% (38.0)
+    done:
+    status: unfinished
+  - name: Month 3
+    funds: 33% (38.0)
+    done:
+    status: unfinished
+payouts:
+  - date: 24 February 2025
+    amount: 38
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+## What
+
+The last quarter I implemented the core cryptography for [Carrot](https://github.com/jeffro256/carrot/blob/master/carrot.md). I will note that preliminary performance tests put Carrot scanning at about 30% faster on CPU usage versus scanning today, mostly thanks to the use of the X25519 ECDH library [mx25519](https:://github.com/tevador/mx25519). I also implemented pruned `cryptonote::transaction` [construction and scanning](https://github.com/monero-project/monero/pull/9697) for Carrot. The FCMP++ integration and Carrot integration are finally meeting ends and are almost ready for hot path integration. This next quarter, I want to continue this work to get a testnet out ASAP.
+
+To recap, here is a list of things I will attempt to work on this quarter, in rough order of execution:
+
+- Integrate Carrot scanning/transaction construction into main wallet codepaths
+- Provide support to existing hardware wallet manufacturors on how to securely support Carrot outputs
+- Use benchmarkings and static analysis to inform MRL decisions on transaction weight discussions etc
+- Begin soliciting Carrot core implementation audits
+- Provide Rust implementation of Carrot for Serai/Cuprate
+- Solicit help for multisig implementations of Carrot
+- Help out with the FCMP++ integration wherever I can
+
+## Who
+
+I have been contributing to the Monero core repository for [over two years](https://github.com/monero-project/monero/pulls?page=2&q=is%3Apr+author%3Ajeffro256) with a total of [84 merged commits to master](https://github.com/monero-project/monero/commits?author=jeffro256) thus far, with many open PRs. Over the last few months, I wrote up the [Carrot specification](https://github.com/jeffro256/carrot/blob/master/carrot.md), organized []auditing](https://github.com/cypherstack/carrot-audit), for which the  community graciously funded, and [began](https://github.com/monero-project/monero/pull/9559) [implementing](https://github.com/monero-project/monero/pull/9697) it. Carrot will be the main supported addressing protocol post-FCMP++ if all goes according to plan. I also worked on the Seraphis migration project in 2023/2024.
+
+Previous Proposals:
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/319
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/390
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/421
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/436
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/467
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/504
+
+## Payment
+
+I propose to work for 3 months at a rate of 38 XMR per month.
+

mature-atomic-swaps-ecosystem.md

+---
+layout: wip
+title: "From Prototype to Marketplace: Maturing the XMR-BTC Atomic Swaps Ecosystem"
+author: "binarybaron and einliterflasche"
+date: July 9, 2024
+amount: 729
+milestones:
+  - name: 1st month
+    funds: 121.5
+    status: finished
+    done: 15 October 2024
+  - name: 2nd month
+    funds: 121.5
+    status: finished
+    done: 26 November 2024
+  - name: 3rd month
+    funds: 121.5
+    status: finished
+    done: 21 January 2025
+  - name: 4th month
+    funds: 121.5
+    status: unfinished
+    done:
+  - name: 5th month
+    funds: 121.5
+    status: unfinished
+    done:
+  - name: 6th month
+    funds: 121.5
+    status: unfinished
+    done:
+payouts:
+  - date: 19 October 2024
+    amount: 121.5
+  - date: 6 December 2024
+    amount: 121.5
+  - date: 3 February 2025
+    amount: 121.5
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+![https://i.ibb.co/3NvpYp2/upload-398781d371d354427bb455356731258c.png](https://i.ibb.co/3NvpYp2/upload-398781d371d354427bb455356731258c.png)
+![https://i.ibb.co/wgYK9FF/generated-gif-2.gif](https://i.ibb.co/wgYK9FF/generated-gif-2.gif)
+
+### Who
+
+We (binarybaron and einliterflasche) are two Monero enthusiasts from Berlin and both computer science students. We have been excited about XMR<>BTC atomic swaps since the COMIT team started development of their prototype. binarybaron has contributed to the project since its early stages while einliterflasche joined later on.
+
+### What is this project anyway?
+
+The project mostly consists of four parts:
+
+1. A command-line utility ([ASB](https://github.com/comit-network/xmr-btc-swap/blob/master/docs/asb/README.md)) that enables individuals to operate a 'swap provider' service. These swap providers offer to sell Monero in exchange for Bitcoin.
+2. A command-line interface ([CLI](https://github.com/comit-network/xmr-btc-swap/blob/master/docs/cli/README.md)) that allows users to connect with swap providers and exchange their Bitcoin for Monero.
+3. A graphical user interface ([GUI](https://github.com/UnstoppableSwap/unstoppableswap-gui/)) that utilizes the CLI behind the scenes, making the swap process way more user-friendly.
+4. A command-line utility for hosting a [rendezvous point](https://github.com/comit-network/rendezvous-server) in the decentralized discovery network. Swap providers can register at these nodes to make themselves known to the network. CLI users can retrieve a list of swap providers.
+
+### What we have been working on over the last 2 years:
+
+- Developed an early web interface to simplify XMR<>BTC swaps. This project has since been deprecated and replaced with a desktop GUI. 
+- Stepped in as maintainers for the [xmr-btc-swap](https://github.com/comit-network/xmr-btc-swap) project which includes the ASB and CLI applications. We have become the main developers fixing issues, implementing new features and pushing out releases.
+- Developed the [GUI](https://github.com/UnstoppableSwap/unstoppableswap-gui/). Last year alone, more than 3,000 swaps were completed using our GUI. Since we completed our second CCS from May 2022, we worked on the project during our free time. This is also the reason we weren't able to dedicate as much time to the project as we'd like to and, frankly, as it deserves.
+- Running a mainnet swap provider to kickstart adoption that has performed over a thousand swaps with users. This has been put on pause for now as more swap providers have emerged.
+- We have also been hosting, and developing publicely accessible infrastructure
+    - An API service that gathers a list of all known swap providers. This can be used in the GUI and also by others in the community (e.g [OrangeFren](https://orangefren.com/)) in addition to rendezvous points.
+    - A reliable rendezvous point
+- As part of our efforts to make atomic swaps accessible to the general public we have have been writing [documentation](https://docs.unstoppableswap.net/) for atomic swaps in general as well for the GUI and CLI applications.
+
+### Proposal:
+
+We're excited to keep working on atomic swaps. While swaps work realiably under optimal conditions, there are still many imperfections. We are confident that given a few months time to fully dedicate to the project, we can transform the ecosystem from more of a proof of concept into a mature marketplace.
+
+We are asking the community for funding in order to be able to focus our efforts on improving the atomic swaps ecosystem.
+
+We request 729 XMR for continued development for 6 months. At the end of each month 121.5 XMR will be paid out. We will dedicate 35 hours of focused work per week per person. Our hourly rate is 60 EUR. We're calcuating these amounts at a current average price of 138 EUR/XMR.
+
+We will be providing monthly detailed updates in the comment section.
+
+### What we will be working on
+
+We will continue to maintain both the GUI and the underlying CLI/ASB by:
+- Planning, coordinating and implementing new features and bug fixes,
+- Coordinating releases,
+- Keeping in touch with users and the community as a whole as well as offering a built-in feedback system in the GUI.
+
+Furthermore, we will continue to manage some community infrastructure:
+- We host a [webpage](https://unstoppableswap.net/) for the GUI as well as [documentation](https://docs.unstoppableswap.net/).
+- We maintain both a public registry of swap providers as well as a reliable node in the decentralized discovery network.
+
+For the CLI and ASB, which form the backbone of the GUI and swap provider infrastructure respectively, our focus will be to improve overall reliability. While swaps work consistently under optimal conditions, there are many moving parts, leading to various challenges in practice. These challenges include:
+- Reliably staying in sync with both the Bitcoin and Monero blockchains,
+- Completing swaps amid connectivity issues,
+- Discovering peers in the network,
+- Maintaining backwards compatability between peers (network protocols),
+- Handling concurrent swaps,
+- Accounting for blockchain congestion,
+- Stringently enforcing protocol compliance,
+- Ensure fail safety when swaps can't be completed,
+- Minimizing the manual intervention required (e.g having to manually refund in some edge cases),
+- ...
+
+For the ASB daemon specifically, our focus will be on enhancing its ability to handle large amounts of liquidity reliably. We will also make it easier for a wider range of individuals to become a swap provider and sell their Bitcoin for Monero. This will improve competition and in turn lead to lower markup rates. Our work will include:
+- Developing user-friendly tooling to simplify the setup and operation of the ASB and its accompanying services.
+- Improving ASB extensibility and automatability by implementing an JSON-RPC server:
+   - Swap providers can connect to their ASB using a standardized OpenRPC protocol
+   - This will enable providers to:
+     - Dynamically adjust their exchange rate based on current conditions and market assessment
+     - Flexibly set maximum and minimum swap amounts according to their risk tolerance
+     - Automate access to internal Bitcoin and Monero wallets for fund management
+     - Listen for all kinds of events
+- Enabling anyone to automate their ASB service to their liking by developing easy-to-use connector libraries for popular programming languages (e.g. Python, TypeScript, Rust, Java).
+
+Integrating the RPC server and developing client libraries will take a lot of work and large refactors, but it will be worth the effort. It will enable the creation of custom applications and scripts built on top of the ASB. This will open basically unlimited possibilities but the most obvious use cases include:
+   - Complete access to statistics and internal data and logging
+   - Adjust exchange rate and minimum swap amount based on current Bitcoin transaction fees
+   - Listening for specific events and executing custom actions e.g. sending notifications or replenishing funds by executing trades on other platforms
+   - Integration of Bitcoin privacy protocols (e.g., CoinJoin, Whirlpool) for received funds
+
+For the GUI itself our focus will be to:
+- Make the GUI more accessible to non technical users (e.g. tooltips, explanations, ...),
+- Provide documentation for end users as well as technical documentation to improve transparency and attract new developers,
+- Work on migrating the GUI framework (from Electron to Tauri) to simplify the architechture,
+- Release an Android (and possibly iOS) version of the GUI.
+- _(We are also looking into a web version, powered by WebAssembly, which can run in browsers. This may not be possible and will require extensive refactors in the code base.)_
+- Build a new UI for hosting and managing the ASB from inside the GUI. Thereby enabling selling Monero for Bitcoin.
+
+### Why
+
+We want to enable anyone to reliably acquire Monero by building an anonymized, decentralized and trustless market that is resiliant to censorship. We believe that by realizing the potential of this project we can bring this to reality.
+
+A mature ecosystem will attract more users and swap providers. This will lead to increased liquidity and competition and thus make atomic swaps a viable alternative to centralized exchanges.

monero-serai-wallet-audit.md

+---
+layout: wip
+title: Audit monero-serai and monero-wallet
+author: kayabaNerve
+date: October 11, 2024
+amount: 1050 XMR
+milestones:
+  - name: Audit of monero-[serai, wallet], including the FROST-inspired multisig protocol
+    funds: 1050 XMR
+    done:
+    status: unfinished
+payouts:
+  - date: 3 December 2024
+    amount: 1050
+---
+ 
+monero-serai and monero-wallet are public-good libraries built by myself as part of my work on Serai DEX. Despite the "-serai" name, both libraries have always been intended to be usable and actually used by the Monero community as a whole. Development has been ongoing for over two years. During that time, I have hired developers to work on and review it (including j-berman who truly needs credit and acknowledgement for their contributions), yet have never seeked community funding for my work. Now that monero-serai and monero-wallet are ready for their 1.0 release, meaning they have reached the necessary milestone to be considered sufficiently developed and meaningful, I have decided to request the community's support for their audits.
+ 
+monero-serai is a from-scratch reimplementation of the Monero transaction protocol in Rust. It originally also
+included wallet functionality yet that was split out into the monero-wallet library to offer greater
+flexibility to consumers.
+ 
+monero-serai is used by Cuprate[[1]](
+  https://github.com/Cuprate/cuprate
+)[[2]](
+  https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/405
+)[[3]](
+  https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/422
+)[[4]](
+  https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/431
+)[[5]](
+  https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/456
+)[[6]](
+  https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/469
+)[[7]](
+  https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/484
+) for its parsing/handling/stateless verification of Monero transactions. Specifically, included is:
+ 
+- An implementation of v1 and v2 transactions
+- Cryptonote ring signature, MLSAG, and CLSAG verification
+- Borromean, Bulletproofs, and Bulletproofs(+) verification
+ 
+monero-serai also underpins monero-wallet, a Rust library for sending and receiving Monero. It's intended to have a clean, high-level API, be usable in a variety of contexts (from desktops to embedded devices to web browsers), and support everything from traditional wallets to more novel use cases (such as atomic swaps). As part of this, it offers:
+ 
+- Proving CLSAG, Bulletproofs, and Bulletproofs(+)
+- Honest-sender outgoing view keys (deterministically derived transaction keys to simplify payment proofs and allow verifying transactions match an intent)
+- A FROST-inspired multisig which has O(1) per-signer upload complexity and O(n) computational complexity, compared to Monero's multisig which has O(n!) complexity (where n is the amount of signers)
+ 
+Potentially of most note is the work on multisig. FROST is a widely regarded, [IRTF standardized](https://datatracker.ietf.org/doc/rfc9591/) multisignature protocol for Schnorr signatures which I've applied to Monero's CLSAG (caveats apply). The application to CLSAG is built upon [modular-frost](https://github.com/serai-dex/serai/tree/develop/crypto/frost), a FROST implementation I wrote for Serai and have already [prior audited](https://github.com/serai-dex/serai/tree/develop/audits/Cypher%20Stack%20crypto%20March%202023).
+
+Monero has historically had issues with its multisig which has a novel high-complexity DKG and a signing protocol which isn't formalized (though is currently Musig2-inspired). monero-wallet represents an opportunity to step forth with a formalized, proven, and audited multisignature implementation. One idea occassionally brought up has been to remove multisig from Monero proper, placing it in its own distinct repository, in order to not have multisig burden Monero. With the work done on monero-wallet, and the audit being funded here, completely deferring multisig to it would become a viable option.
+ 
+monero-wallet has also been checked to have a matching decoy selection algorithm (specifically, a matching distribution of selected decoys), fee algorithm, and various other properties (such as TX extra) to ensure its transactions won't be fingerprintable.
+ 
+There is interest by multiple wallets to use monero-wallet, and it's already being developed on top of by Serai, a user-facing multisignature use case, and an application premised on web technology (which compiles monero-wallet to WASM).
+ 
+This CCS is to fund the formalization of the implemented CLSAG multisig protocol (already outlined), provide the necessary security proofs (derived from FROST), and audit monero-[serai, wallet]. The audit will be done by Cypher Stack (their quoted amount being the amount requested). The one milestone is to be paid directly, immediately, and in full, to Cypher Stack for their work.
+
+After the audit, the plan is to transfer monero-serai into the newly created [monero-oxide](https://github.com/monero-oxide/monero-oxide) organization (head by myself and boog900 from Cuprate). This is to help ensure it stands as a public good and doesn't solely service a single project's needs. Additional discussions are ongoing regarding the future governance of monero-wallet.

monerobull-bootstrap-workgroup.md

+---
+layout: cp
+title: "monerobull for website workgroup"
+author: monerobull
+date: 5 July 2024
+amount: 30
+milestones:
+  - name: 2 meetings + hours worked
+    funds: 10 XMR
+    done: 1 January 2025
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 10 XMR
+    done: 1 January 2025
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 10 XMR
+    done: 1 January 2025
+    status: finished
+payouts:
+  - date: 30 January 2025
+    amount: 30
+---
+
+# Who, what, when, where?
+
+Hi, I'm monerobull. I run monero.town & monerosupplies.com. I also never did any paid work for Monero before.
+
+I was recently mentioned in a CCS proposal by geonic, famous Monero movie director. 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 my own CCS proposal rather than through geonics. This moves me from being accountable to nobody, to accountable to the community.
+
+A quick summary of what I'd be working on:
+- Setting up / managing a Monero Website Workgroup, keep it up to date (our roadmap still mentions triptych)
+- Joining the moderator teams for Matrix and helping along with discord
+- Being a supportive figure 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, not IRC, Matrix, Reddit, etc.)
+- Aiding and assisting in event work as needed (part of Monerokon team since MK3)
+
+# Why?
+There's lots of non-dev stuff to do, and not so many people to do it. I am mostly capable and willing.
+
+# How long? How much?
+
+30 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. Luigi does a lot of work, I'd like to take on some of that.
+
+# COI
+I would have never made this proposal without geonics preceding yolo proposal. In the past I've tried to stay away from the CCS due to all the drama surrounding it. This very proposal was born out of CCS drama.

monerotopia2024publicity.md

+---
+layout: wip
+title: Monerotopia 2024 Marketing and Publicity
+author: geonic
+date: November 6, 2024
+amount: 36.68
+milestones:
+  - name: Payment to Estrategia Blue PR
+    funds: 36.68
+    status: unfinished
+    done:
+payouts:
+  - date:
+    amount: 36.68
+---
+# Monerotopia 2024 Marketing & Publicity
+
+Hi! As discussed in the [previous community meeting](https://libera.monerologs.net/monero-community/20241026#c451916), I am proposing that we [spend the unused funds](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/70#note_26878) from the last Monero Outreach CCS on marketing & publicity for Monerotopia 2024, which starts next Thursday. I would be the key point of contact for the PR firm and will provide a final report on what's been achieved.
+
+Our events are the perfect opportunity to publicize/advertise Monero and so far we haven't done a good job at that. This proposal is a first step in changing that.
+
+**Estrategia Blue PR**, a leading publicity firm in Mexico, has made a [proposal](https://github.com/geonic1/geonic/blob/master/Monerotopia%20Proposal.pdf) and they are ready to start today. We need to engage them ASAP. Vik Sharma has agreed to handle the payment and receive the XMR at no surcharge. The proposed budget (~$5500) is within the remaining amount (36.68 XMR or ~$6000), which we intend to spend in full with more (or less) media buys, depending on the actual amount received by the firm.
+
+As the only remaining, active member of Monero Outreach, I believe this is a good use of the funds and in the spirit of what the donors wished to support.
+
+Cheers!
+geonic

mrcyjanek-xmruw-development.md

@@ -7,21 +7,21 @@ amount: 76.68
 milestones:
   - name: Month 1
     funds: 25.56
-    done:
-    status: unfinished
+    done: 8 July 2024
+    status: finished
   - name: Month 2
     funds: 25.56
-    done:
-    status: unfinished
+    done: 31 August 2024
+    status: finished
   - name: Month 3
     funds: 25.56
     done:
     status: unfinished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 17 July 2024
+    amount: 25.56
+  - date: 4 September 2024
+    amount: 25.56
   - date:
     amount:
 ---

netrik-translation-coordination-2.md

 ---
-layout: wip
+layout: cp
 title: Three Months of Translation Coordination
 author: netrik182
 date: December 7, 2021
@@ -15,18 +15,22 @@ milestones:
     status: finished
   - name: February
     funds: 15
-    done:
-    status: unfinished
+    done: 12 February 2025
+    status: finished
 payouts:
   - date: 5 January 2022
     amount: 15
   - date: 8 February 2022
     amount: 15
-  - date: 
-    amount: 
+  - 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/). 
 

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-4.md

 ---
-layout: wip
+layout: cp
 title: "CCS Coordinator"
 author: plowsof
 date: March 29th 2024
@@ -7,22 +7,22 @@ amount: 80.07
 milestones:
   - name: 2 meetings + hours worked
     funds: 26.69 XMR
-    done:
-    status: unfinished
+    done: 2 June 2024
+    status: finished
   - name: 2 meetings + hours worked
     funds: 26.69 XMR
-    done:
-    status: unfinished
+    done: 2 June 2024
+    status: finished
   - name: 2 meetings + hours worked
     funds: 26.69 XMR
-    done:
-    status: unfinished
+    done: 5 September 2024
+    status: finished
 payouts:
-  - date:
+  - date: 24 June 2024
     amount: 26.69
-  - date:
+  - date: 24 June 2024
     amount: 26.69
-  - date:
+  - date: 28 September 2024
     amount: 26.69
 ---
 

plowsof_6_ccs_coordinator.md

+---
+layout: fr
+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.

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.

selsta-10.md → selsta-10p.md

 ---
 layout: cp
-title: selsta part-time monero development (3 months)
+title: selsta part-time monero development (3 months) (10)
 author: selsta
 date: 31 July 2023
 amount: 115
@@ -42,7 +42,7 @@ selsta, I have been contributing to monero since around 2018 with over 628 merge
 
 - CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
 - GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
-- Previous CCS: https://ccs.getmonero.org/proposals/selsta-9.html
+- Previous CCS: https://ccs.getmonero.org/proposals/selsta-9p.html
 
 If funded I will provide monthly updates in the CCS comment section.
 

selsta-11.md → selsta-11p.md

 ---
 layout: cp
-title: selsta part-time monero development (3 months)
+title: selsta part-time monero development (3 months) (11)
 author: selsta
 date: 02 November 2023
 amount: 105
@@ -42,7 +42,7 @@ selsta, I have been contributing to monero since around 2018 with over 645 merge
 
 - CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
 - GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
-- Previous CCS: https://ccs.getmonero.org/proposals/selsta-9.html
+- Previous CCS: https://ccs.getmonero.org/proposals/selsta-10p.html
 
 If funded I will provide monthly updates in the CCS comment section.
 

selsta-12.md → selsta-12p.md

 ---
 layout: cp
-title: selsta part-time monero development (3 months)
+title: selsta part-time monero development (3 months) (12)
 author: selsta
 date: 02 February 2023
 amount: 153
@@ -44,7 +44,7 @@ selsta, I have been contributing to monero since around 2018 with over 656 merge
 
 - CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
 - GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
-- Previous CCS: https://ccs.getmonero.org/proposals/selsta-11.html
+- Previous CCS: https://ccs.getmonero.org/proposals/selsta-11p.html
 
 If funded I will provide monthly updates in the CCS comment section.
 

selsta-13.md → selsta-13p.md

 ---
-layout: wip
-title: selsta part-time monero development (3 months)
+layout: cp
+title: selsta part-time monero development (3 months) (13)
 author: selsta
 date: 01 May 2023
 amount: 159
 milestones:
   - name: May
     funds: 33% (53 XMR)
-    done:
-    status: unfinished
+    done: 31 May 2024
+    status: finished
   - name: June
     funds: 33% (53 XMR)
-    done:
-    status: unfinished
+    done: 4 July 2024
+    status: finished
   - name: July
     funds: 33% (53 XMR)
-    done:
-    status: unfinished
+    done: 3 August 2024
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 9 June 2024
+    amount: 53
+  - date: 16 July 2024
+    amount: 53
+  - date: 11 August 2024
+    amount: 53
 ---
 
 ## What
@@ -43,7 +43,7 @@ selsta, I have been contributing to monero since around 2018 with over 663 merge
 
 - CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
 - GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
-- Previous CCS: https://ccs.getmonero.org/proposals/selsta-12.html
+- Previous CCS: https://ccs.getmonero.org/proposals/selsta-12p.html
 
 If funded I will provide monthly updates in the CCS comment section.