gingeropolous_1TB_MRC.md

+---
+layout: cp
+title: Gingeropolous 1TB MRC upgrade
+author: Gingeropolous
+date: November 9, 2024
+amount: 20
+milestones:
+  - name: Install 1TB ram in new epyc server
+    funds: 100% (20 xmr)
+    done: 24 January 2025
+    status: finished
+payouts:
+  - date: 3 February 2025
+    amount: 20
+---
+
+
+1TB ram for new MRC server
+
+I finally purchased a new epyc server, and I need to get ram for it. I was just going to get the minimal needed to make the thing mine some xmr, but figured we can pack this thing to the gills to provide some monstrous compute capacity for monero R&D.
+
+For some background, I manage the Monero Research Computing cluster, which is essentially just my mining rigs that I've put more ram and storage in. I provide access to the MRC to various monero researchers and developers, so they can get some stuff done. The rigs mine when there is no activity by the users. 
+
+Currently, monero researchers are primarily using the box "Junior", which is a 64 thread AMD Ryzen Threadripper 3970X with 256 GB ram (max ram for the mobo). There is a 5x nvme striped lv thingy that allows for some fast swap, but its still just swap. This rig was upgraded years ago through the CCS (https://ccs.getmonero.org/proposals/gingeropolous_zenith_storage.html) to provide ample storage space for researchers (74 TB HDD - funded by me, 14TB nvme - funded by CCS), as working with the monero blockchain requires storing and moving massively large files. I have other boxes, but they are your average mobo that can take a max 128 GB. Rucknium has been able to do some distributed compute across all the boxes (at one point 7 or so boxes?), but I've found most folks just want a single box with massive amounts of ram. 
+
+This proposal is for funds for me to purchase 1 TB of ram to install in a new 2x 7h12 server (256 threads!) so monero researchers can stop fiddling with memory constraints when working or waiting for the poor 64 threads to chug through their tasks. The system maxes out at 4 TB (!!!!), so perhaps if funding goes over the request and hits enough to get more ram, then that will happen. 
+
+This is important for the community because more compute ==  more research capabilities for monero researchers. This request was already brought up during a monero research lab meeting, and the members were interested in adding this capacity to our cluster. 
+
+Milestone 0 isn't included, because its me purchasing the 2x epyc server. I just did that. So thats done. 
+
+Milestone 1 is when I have the 2x epyc server up and running with 1TB of ram installed. I'll take a screen shot and upload it. 
+Timeline: 3 months? This should all be done by 2025-02-01 at the latest, but I expect this to be up and running by 2025-01-01.
+
+Amount: I plan on purchasing this ram:
+https://www.ebay.com/itm/225753803091
+
+So that comes out to around 15 xmr. I'm requesting 20 xmr for some padding and to pay for some of my time and I'll probably end up buying more stuff I wouldn't need for mining (like a 4TB nvme for the box because always more storage). If I receive a lot over the requested amount, I'll consider either finding higher quality ram (anyone have any input on that A-tech stuff?) or more ram. 
+

hardenedsteel-getmonero-2.md

 ---
-layout: wip
+layout: cp
 title: Part-time Work on getmonero.org (2 Month)
 author: HardenedSteel
 date: 14 September, 2024
@@ -7,17 +7,15 @@ amount: 10
 milestones:
   - name: Month 1
     funds: 5 XMR
-    done:
-    status: unfinished
+    done: 3 December 2024
+    status: finished
   - name: Month 2
     funds: 5 XMR
-    done:
-    status: unfinished
+    done: 3 December 2024
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 13 December 2024
+    amount: 10
 ---
 
 # Who?

haveno-multi-platform-native-app-for-every-os.md

 ---
-layout: wip
+layout: cp
 title: Haveno Multi-Platform Native App for Android, iOS, Windows and Linux.
 author: Kewbit
 date: August 19, 2024
@@ -31,11 +31,65 @@ payouts:
   - date:
     amount: 50
 ---
-# Haveno Multi-Platform Native App for Android, iOS, Windows, MacOS and Linux
+### Haveno Multi-Platform Native App for Android, iOS, Windows, MacOS and Linux
 
 **Author**: Kewbit  
 **Date**: 19/08/2024
 
+# Proposal termination December 31st, 2024
+
+A contractor presented themselves to the CCS for the sole purpose of creating a Multi-OS Haveno App using a portion of funds from the abandoned Haveno frontend proposal. [1] (of which 378XMR remain)
+
+There has since been a public controversy surrounding this proposal/contractor. [2] [3]    
+
+The CCS itself is devoid of opinion/emotion regarding 'extra curricular' activities. [4]
+
+As per the Community meeting on December 7th [5], the partial payout request was unanimously denied.
+
+During this meeting, Woodser, the lead developer of Haveno suggested [6]:
+> [a] deadline to release the code, in hopes of getting the code for the greater benefit of the project
+
+Whilst the majority voted to close the proposal with immediate effect.
+
+Community trust and sentiment plays a significant role in our Crowdfunding System. For this contractor, it has been **irrevocably and permanently lost**.
+
+On December 10th the contractor was *explicitly informed* [7] to not expect payment outside of milestones 2.
+
+_"Work done as per your proposal is work paid"_: 
+
+* As per the contractors own admission[8] on December 21st via another partial payout request, the work is not done. 
+
+The decision is simple and the contractor is to blame. They:
+* Will not continue working on the proposal until a partial payout is made. (This will not happen again)
+* Demand a decision as soon as possible.    
+
+All deadlines have passed:
+
+* The latest, mentioned by the contractor in their own proposal (*31st December*)
+* The community calling for immediate closure (*December 7th*)
+* One mention of allowing an extra week to complete[9] (*December 14th*).
+
+* Given this, the expert witness review will now focus solely on:
+  1. Validating the legitimacy of the previous Milestone 2 payout (75 XMR)[10].
+  2. Assessing the utility of the existing open source code for future development.
+ 
+If Milestone 2's work meets the proposal requirements and the existing source code is of high quality, despite being incomplete, a new team or contractor can continue the development after a more stringent vetting process if the community wishes to continue this venture.
+
+Should the review expose any shortcomings in the payout review process, these will be addressed moving forward.
+
+[1]: https://ccs.getmonero.org/proposals/haveno-frontend.html
+[2]: https://librejo.monerodevs.org/SyntheticBird/kewbit-drama
+[3]: https://github.com/MAGICGrants/Monero-Fund-Elections/issues/10#issuecomment-2565810794
+[4]: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/334#note_19962
+[5]: https://github.com/monero-project/meta/issues/1120#issuecomment-2525531999
+[6]: https://libera.monerologs.net/monero-community/20241207#c471605
+[7]: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/489#note_27830
+[8]: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/489#note_27825
+[9]: https://libera.monerologs.net/monero-community/20241207#c471632-c471633
+[10]:https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/489#note_26721
+
+---
+
 ## Overview
 
 The Haveno Multi-Platform Native App will be an interface for decentralized applications that can connect to the Haveno Daemon, allowing users to conduct transactions in Monero (XMR) using the Haveno decentralized network. Users will be able to buy and sell multiple fiat currencies with their XMR through Haveno. The app will be able through all app stores and installers, or you can build from source.

hinto-3.md

 ---
-layout: wip
+layout: cp
 title: hinto-janai full-time work on Cuprate (3 months)
 author: hinto-janai
 date: August 9, 2024
@@ -7,23 +7,21 @@ amount: 221
 milestones:
   - name: JSON RPC handlers
     funds: 40% (88.4)
-    done:
-    status: unfinished
+    done: 25 December 2024
+    status: finished
   - name: Binary/other RPC handlers
     funds: 40% (88.4)
-    done:
-    status: unfinished
+    done: 25 December 2024
+    status: finished
   - name: Other work
     funds: 20% (44.2)
-    done:
-    status: unfinished
+    done: 4 November 2024
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 12 November 2024
+    amount: 44.2
+  - date: 21 January 2024
+    amount: 176.8
 ---
 
 ## What

hinto-4.md

+---
+layout: wip
+title: hinto-janai full-time work (3 months)
+author: hinto-janai
+date: February 7, 2025
+amount: 186
+milestones:
+  - name: Month 1
+    funds: 62 XMR
+    done:
+    status: unfinished
+  - name: Month 2
+    funds: 62 XMR
+    done:
+    status: unfinished
+  - name: Month 3
+    funds: 62 XMR
+    done:
+    status: unfinished
+payouts:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+## What
+Work full-time for 480 hours on:
+- Cuprate
+  - Alpha release cycle [1](https://github.com/Cuprate/cuprate/issues/371) [2](https://github.com/Cuprate/cuprate/issues/374)
+  - User book [1](https://user.cuprate.org) [2](https://github.com/Cuprate/cuprate/pull/165) [3](https://hinto-janai.github.io/cuprate-user-book)
+  - Project roadmap Q1/Q2 goals [1](https://github.com/Cuprate/cuprate/issues/376) [2](https://github.com/Cuprate/cuprate/pull/369) [3](https://github.com/Cuprate/cuprate/pull/370)
+  - Misc. review work
+- Monero
+  - FCMP++ related review [1](https://github.com/monero-project/monero/pull/9440) [2](https://github.com/monero-project/monero/pull/9436) [3](https://github.com/monero-project/monero/issues/9422#issuecomment-2504037485)
+
+Cuprate is preparing its first alpha release, with a 4-week cycle. A progress report for 2024 is [here](https://www.reddit.com/r/Monero/comments/1ij2sw6/cuprate_2024_progress_report), the roadmap for 2025 is [here](https://github.com/Cuprate/cuprate/issues/376). I will be buying/renting a variety of hardware for testing/development and will post receipts for all hardware acquired at the time of exchange within this CCS.
+
+If developer resources becomes a bottleneck for FCMP++ activation on `monerod`, I will switch priority when/where possible. This was discussed [here](https://github.com/monero-project/meta/issues/1137). Otherwise, I will continue working on Cuprate Q1/Q2 goals noted in the project roadmap, specifically: user book, release cycle, RPC integration [1](https://github.com/Cuprate/cuprate/issues/379).
+
+## Who
+[hinto-janai](https://github.com/hinto-janai)
+
+Previous proposals:
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/422
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/456
+- https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/484
+
+## Funding
+186 XMR. 
+
+$65 + 0.1 XMR per hour for 480 hours at $225/XMR.

j-berman-3months-full-time-8.md

 ---
-layout: wip
+layout: cp
 title: j-berman full-time development (3 months)
 author: j-berman
 date: August 26, 2024
@@ -11,19 +11,19 @@ milestones:
     status: finished
   - name: Month 2
     funds: 33% (106 Monero)
-    done:
-    status: unfinished
+    done: 11 November 2024
+    status: finished
   - name: Month 3
     funds: 33% (106 Monero)
-    done:
-    status: unfinished
+    done: 12 December 2024
+    status: finished
 payouts:
   - date: 20 October 2024
     amount: 105
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 19 November 2024
+    amount: 106
+  - date: 12 January 2025
+    amount: 106
 ---
 
 ## What

j-berman-3months-full-time-9.md

+---
+layout: wip
+title: j-berman full-time development (4 months)
+author: j-berman
+date: December 16, 2024
+amount: 360 Monero
+milestones:
+  - name: Month 1
+    funds: 25% (90 Monero)
+    done: 21 January 2025
+    status: finished
+  - name: Month 2
+    funds: 25% (90 Monero)
+    done: 24 February 2025
+    status: finished
+  - name: Month 3
+    funds: 25% (90 Monero)
+    done: 19 March 2025
+    status: finished
+  - name: Month 4
+    funds: 25% (90 Monero)
+    done:
+    status: unfinished
+payouts:
+  - date: 4 February 2025
+    amount: 90
+  - date: 19 March 2025
+    amount: 90
+  - date: 8 April 2025
+    amount: 90
+  - date:
+    amount:
+---
+
+## What
+
+Work full-time 4 months on:
+
+- Work towards a test network that includes Full-Chain Membership Proofs++.
+  - Continue optimizing building the FCMP++ curve tree to improve sync time both in the daemon and wallet.
+  - Construct FCMP++ transactions via the CLI/RPC/GUI.
+  - Verify FCMP++ transactions in the daemon.
+  - Implement all consensus changes needed for FCMP++.
+    - New unlock time logic.
+    - Allowing new FCMP++ RCT type.
+    - Implement a grace period for current tx types in the pool at the fork to make it into the chain.
+    - Misc. necessary changes.
+  - Update the cold wallet <> hot wallet integration and background syncing for FCMP++.
+- Misc. high priority tasks as they arise.
+
+## Who
+
+j-berman on github / jberman on matrix / IRC
+
+My open PR for the WIP FCMP++ integration: https://github.com/monero-project/monero/pull/9436
+
+My branch that includes the wallet sync integration: https://github.com/j-berman/monero/commits/fcmp%2B%2B-tree-sync-dev/
+
+Past CCS's:
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-8.html
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-7.html
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-6.html
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-5.html
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-4.html
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-3.html
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-2.html
+- https://ccs.getmonero.org/proposals/j-berman-3-months-full-time.html
+
+## Proposal
+
+360 XMR
+
+640 hours, 0.25 XMR/hr + $65/hr, $208/XMR from coingecko

j-berman-4months-full-time-10.md

+---
+layout: fr
+title: j-berman full-time development (4 months)
+author: j-berman
+date: April 14, 2025
+amount:  396 Monero
+milestones:
+  - name: Month 1
+    funds: 25% (99 Monero)
+    done:
+    status: unfinished
+  - name: Month 2
+    funds: 25% (99 Monero)
+    done:
+    status: unfinished
+  - name: Month 3
+    funds: 25% (99 Monero)
+    done:
+    status: unfinished
+  - name: Month 4
+    funds: 25% (99 Monero)
+    done:
+    status: unfinished
+payouts:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+## What
+
+Work full-time 4 months on:
+
+- Completing the FCMP++ integration.
+    - Complete the blinds cache to speed up FCMP++ transaction construction ([WIP PR](https://github.com/seraphis-migration/monero/pull/25)).
+    - Work on the following, some of which @jeffro256 is already working on:
+        - Fee logic for FMCP++.
+        - Incorporate composition changes to tree building and remove code for the key image migration: https://github.com/monero-project/meta/issues/1168
+        - Cold wallet <> hot wallet integration.
+        - HW wallet interface changes.
+        - Multisig.
+        - The `scan_tx` feature.
+        - Background sync.
+        - Clean up the FFI.
+        - Cleaner logging.
+    - Manage the [FCMP++ optimization contest](https://github.com/j-berman/fcmp-plus-plus-optimization-competition) and implement the winning submissions as necessary.
+        - It should be noted: if the contest does not yield significant improvements specifically to `helioselene`, it may be worth it to re-work the FCMP++ wallet scanner to *download* the tree instead of re-build it locally.
+            - Re-working the wallet scanner would likely take 1-2 weeks.
+- Review the Carrot integration.
+- Update documentation for the FCMP++ integration, using the same format as in this (now outdated) [WIP PR](https://github.com/monero-project/monero/pull/9436).
+- Start submitting piecemeal FCMP++ PR's to the main Monero repo.
+- Review @vtnerd's p2p encryption PR: https://github.com/monero-project/monero/pull/8996
+- Continue Seraphis wallet library work:
+    - My next task on this front is to bring the Serpahis lib async scanner into the current wallet API ([source](https://github.com/seraphis-migration/wallet3/issues/64#issuecomment-2067030930))
+    - In the latest round of tests, I observed scanning speed-ups of 50-60% with a clearnet remote node, 35-45% with a tor node, 25-35% with a local node.
+    - The async scanner has already undergone a round of review ([source](https://github.com/UkoeHB/monero/pull/23))
+    - To be usable in the wallet API, the following still needs to be implemented:
+        - A mutable subaddress lookahead ([source](https://github.com/UkoeHB/monero/pull/23#issuecomment-2036086371))
+        - Pool scanning ([source](https://github.com/UkoeHB/monero/issues/41))
+        - A clean way to save tx metadata ([source](https://github.com/UkoeHB/monero/issues/48))
+        - The FCMP++ tree builder + Carrot scanning needs to be integrated.
+
+A note: once I've completed all work on FCMP++, reviewing the Carrot integration, and reviewing [p2p encryption](https://github.com/monero-project/monero/pull/8996)), I may work on Serai independent from this CCS. I would like to see Serai launched and operating smoothly (and I still owe @kayabaNerve [more work on Serai in exchange for their research into FCMP's](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/359#note_21276)). I would then return to continue Seraphis wallet library work.
+
+## Who
+
+j-berman on github / jberman on matrix / IRC
+
+Past CCS's:
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-9.html
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-8.html
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-7.html
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-6.html
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-5.html
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-4.html
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-3.html
+- https://ccs.getmonero.org/proposals/j-berman-3months-full-time-2.html
+- https://ccs.getmonero.org/proposals/j-berman-3-months-full-time.html
+
+## Proposal
+
+396 XMR
+
+640 hours, 0.3 XMR/hr + $65/hr, $204/XMR from coingecko
+
+Requesting a raise of 0.05 XMR/hr from my prior CCS given I have demonstrated the ability to take the FCMP++ integration to the finish line.

jeffro256-full-time-2024Q4.md

 ---
-layout: wip
+layout: cp
 title: jeffro256 full-time development 2024Q4
 author: jeffro256
 date: September 16, 2024
@@ -7,23 +7,23 @@ amount: 144
 milestones:
   - name: Month 1
     funds: 33% (48.0)
-    done:
-    status: unfinished
+    done: 9 November 2024
+    status: finished
   - name: Month 2
     funds: 33% (48.0)
-    done:
-    status: unfinished
+    done: 12 December 2024
+    status: finished
   - name: Month 3
     funds: 33% (48.0)
-    done:
-    status: unfinished
+    done: 14 January 2025
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 12 November 2024
+    amount: 48
+  - date: 12 January 2025
+    amount: 48
+  - date: 23 January 2025
+    amount: 48
 ---
 
 ## What

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: 28 March 2025
+    status: finished
+  - name: Month 3
+    funds: 33% (38.0)
+    done:
+    status: unfinished
+payouts:
+  - date: 24 February 2025
+    amount: 38
+  - date: 10 April 2025
+    amount: 38
+  - 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

@@ -11,12 +11,12 @@ milestones:
     done: 15 October 2024
   - name: 2nd month
     funds: 121.5
-    status: unfinished
-    done:
+    status: finished
+    done: 26 November 2024
   - name: 3rd month
     funds: 121.5
-    status: unfinished
-    done:
+    status: finished
+    done: 21 January 2025
   - name: 4th month
     funds: 121.5
     status: unfinished
@@ -32,10 +32,10 @@ milestones:
 payouts:
   - date: 19 October 2024
     amount: 121.5
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 6 December 2024
+    amount: 121.5
+  - date: 3 February 2025
+    amount: 121.5
   - date:
     amount:
   - date:

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: wip
+layout: cp
 title: "monerobull for website workgroup"
 author: monerobull
 date: 5 July 2024
@@ -7,23 +7,19 @@ amount: 30
 milestones:
   - name: 2 meetings + hours worked
     funds: 10 XMR
-    done:
-    status: unfinished
+    done: 1 January 2025
+    status: finished
   - name: 2 meetings + hours worked
     funds: 10 XMR
-    done:
-    status: unfinished
+    done: 1 January 2025
+    status: finished
   - name: 2 meetings + hours worked
     funds: 10 XMR
-    done:
-    status: unfinished
+    done: 1 January 2025
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 30 January 2025
+    amount: 30
 ---
 
 # Who, what, when, where?

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

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

@@ -11,12 +11,12 @@ milestones:
     status: finished
   - name: Sep 2024
     funds: 14 XMR
-    done:
-    status: unfinished
+    done: 31 January 2025
+    status: finished
   - name: Oct 2024
     funds: 14 XMR
-    done:
-    status: unfinished
+    done: 6 April 2025
+    status: finished
   - name: Nov 2024
     funds: 14 XMR
     done:
@@ -55,10 +55,10 @@ milestones:
 payouts:
   - date: 28 September 2024
     amount: 14
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 25 February 2025
+    amount: 14
+  - date: 18 April 2025
+    amount: 14
   - date:
     amount:
   - date:

ofrnxmr_basicswap.md

@@ -35,28 +35,28 @@ milestones:
     status: finished
   - name: M2-O (ofrnxmr, 3rd month)
     funds: 20 XMR
-    done:
-    status: unfinished
+    done: 30 November 2024
+    status: finished
   - name: M2-F (~320-480hrs, 3rd month)
     funds: 40 XMR
-    done:
-    status: unfinished
+    done: 30 November 2024
+    status: finished
   - name: M2-B (~320-480hrs, 3rd month)
     funds: 55 XMR
-    done:
-    status: unfinished
+    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:
-    status: unfinished
+    done: 19 January 2025
+    status: finished
   - name: M3-B - Backend v0.13 - v0.15+ (prepaid, ~6 months)
     funds: 410 XMR
-    done:
-    status: unfinished
+    done: 19 January 2025
+    status: finished
   - name: M4 - Delivery of 1.0 (postpaid, ~3 months)
     funds: 190 XMR
     done:
@@ -73,10 +73,10 @@ payouts:
     amount: 80
   - date: 23 October 2024
     amount: 115
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 6 December 2024
+    amount: 115
+  - date: 6 February 2025
+    amount: 730
   - date:
     amount:
   - date:

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

@@ -11,8 +11,8 @@ milestones:
     status: finished
   - name: Payment for first test build
     funds: 40 % (79.706 XMR)
-    done:
-    status: unfinished
+    done: 23 March 2025
+    status: finished
   - name: Payment for completion
     funds: 40 % (79.706 XMR)
     done:
@@ -20,11 +20,19 @@ milestones:
 payouts:
   - date: 29 April 2024
     amount: 39.853
+  - date: 3 April 2025
+    amount: 79.706
   - date:
     amount:
 ---
 
+### Deadline update: July 1, 2025
+
+Prior to the deadline, the proposer MUST provide regular updates on their progress as per the CCS rules.
+
+If the provided updates/progress (or lack thereof) is unsatisfactory, all remaining funds **can be** relinquished either before or after the deadline.
 
+The community will then seek another person/team to take over. If this cannot be accomplished within a reasonable timeframe, the funds will be repurposed or reallocated to a similar proposal (subject to community consensus).
 
 # Who
 
@@ -75,4 +83,4 @@ For the past year and a half we relied on our small community to help fund us, a
 
 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.
+~~CCS will expire one year from date of first payout and funds can be send to the General Fund.~~

revuo-monero-maintenance-2024-q4.md

 ---
-layout: wip
+layout: cp
 title: Revuo Monero maintenance (2024 Q4)
 author: rottenwheel
 date: September 2, 2024
@@ -7,23 +7,23 @@ amount: 8.5
 milestones:
   - name: October
     funds: 3
-    done:
-    status: unfinished
+    done: 1 November 2024
+    status: finished
   - name: November
     funds: 3
-    done:
-    status: unfinished
+    done: 28 November 2024
+    status: finished
   - name: December
     funds: 2.5
-    done:
-    status: unfinished
+    done: 26 December 2024
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 12 November 2024
+    amount: 3
+  - date: 6 December 2024
+    amount: 3
+  - date: 12 January 2025
+    amount: 2.5
 ---
 
 # What