0xfffc-2025Q1.md

+---
+layout: wip
+title: "0xfffc full-time C++ development (3 months, Jan, Feb, Mar, 2025)"
+author: 0xfffc
+date: December 13, 2024
+amount: 111
+milestones:
+  - name: 160 hours
+    funds: 37
+    done:
+    status: unfinished
+  - name: 160 hours
+    funds: 37
+    done:
+    status: unfinished
+  - name: 160 hours
+    funds: 37
+    done:
+    status: unfinished
+payouts:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+    
+### What
+
+The bulk of my focus will be on opportunities related to performance improvement. To find out performance improvement opportunities a performance test suite is necessary for the Monero project. Here is a list of tasks I have on my todo list:
+
+- Bandwidth-Efficent Transaction Propagation Usage: Work on the @boog900 proposal ( https://github.com/monero-project/monero/issues/9334 ). And reduce the communication load between peers when syncing. The final goal is to merge a PR that uses this mechanism in Monero P2P subsystem. 
+
+- Exclusive incoming ip: --exclusive-incoming-ip flag: (a) Require --add-exclusive-node to be set. (b) Be able to be set multiple times.
+
+- Cleanup the sleepwait: Remove this _sleep_wait_ and change it to condition variable: https://github.com/monero-project/monero/blob/cc73fe71162d564ffda8e549b79a350bca53c454/src/daemon/daemon.cpp#L198
+
+- Sync time estimation: When calculating how long it will take to finish the sync, is uses a number of blocks. Example: 200 blocks remaining, synced 20 blocks in 1 min = 10 mins remaining. It should use the size, instead of the block number.
+
+- Performance benchmarks. The performance benchmark test I am working on right now is stress testing Monerod under an intense load that tries to mimic a real-world heavy node. Right now it is in very early shape. The end goal is to mimic real-world wallet usage on the Monero daemon.
+
+- Completion of Read/Write Lock PR [#9181](https://github.com/monero-project/monero/pull/9181). PR 9181 is a huge change to the core of the blockchain implementation of the Monero project. It requires a lot of careful analysis and testing. Task 1 and Task 2 are kind of depend on each other. I use benchmarking results from task 1 to test/improve/debug 9181. @jeffro256_ has implemented an important and sensitive part of the 9181 code and has improved the PR with his suggestions.
+
+- Seraphis wallet LMDB storage. Based on our discussion in the IRC #monero group, it seems porting the entire wallet2 storage to LMDB at this point is not a wise decision. Instead of that, we should start implementing the Seraphis wallet cache with LMDB. Once I am finished with Task 1 and 2, my next big goal is to start focusing on this task. The target of this task is to have Seraphis wallet only using LMDB as its cache/storage engine.
+
+- Static analysis. This task hasn't been finished from my previous CCS by the time I am submitting this CCS. I am hopeful I will finish it before the end of my previous CCS. But in case I am not able to finish it, this is one of the tasks I have on my todo list: "Analyze existing static analyzers (clangd-based analyzer, NASA/ikos, Facebook/infer, etc) and report to @selsta about the possibility of adding one of them as a workflow to our GitHub repository. Target will be running static analysis on submitted PR as workflow."
+
+### Who
+
+I have been contributing to the Monero core repository for the past few months with a total of multiple ([PRs]( https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3A0xFFFC0000+)) merged commits thus far. Some ongoing contributions:
+
+- Helped review multiple [PRs](https://github.com/monero-project/monero/pulls?q=is%3Apr+reviewed-by%3A%40me).
+- Implemented Read/Write lock mechanism for core blockchain implementation. [9181](https://github.com/monero-project/monero/pull/9181).
+- Helped to review and fix multiple HackerOne reports with @selsta.
+
+A special thanks to all community members who are always available to help me with technical questions.
+  
+Previous Proposals:
+  
+- [429](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/429)
+- [438](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/438)
+- [487](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/487)
+
+
+### Funding
+
+- 37xmr/mth * 3 months = 111xmr
+
+- Schedule: 40hr/week * 12week
+
+
+Freedom wins.
+0xFFFC

MoneroSignerResurrection.md

 ---
-layout: wip
+layout: cp
 title: "Monero Signer Resurrection: Reviving and Enhancing the Monero Signing Project"
 author: Thor a.k.a vthor a.k.a DiosDelRayo
 date: May 24, 2024
@@ -11,26 +11,29 @@ milestones:
     status: finished
   - name: Monero Signer working with companion Application
     funds: 5 XMR
-    done:
-    status: unfinished
+    done: 28 July 2024
+    status: finished
   - name: Cleanup and production ready
     funds: 35 XMR
-    done:
-    status: unfinished
+    done: 12 August 2024
+    status: finished
   - name: Monero-GUI integration
     funds: 10 XMR
-    done:
-    status: unfinished
+    done: 27 September 2024
+    status: finished
 payouts:
   - date: 20 June 2024
     amount: 5.38
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 29 July 2024
+    amount: 5
+  - date: 13 August 2024
+    amount: 35
+  - date: 28 September 2024
+    amount: 10
 ---
+
+_Note: this proposal has been awarded 55.38 XMR from [MoneroSigner](https://ccs.getmonero.org/proposals/MoneroSigner.html)_
+
 # Monero Signer Resurrection: Reviving and Enhancing the Monero Signing Project
 
 ## Proposal

0xfffc-2024Q2.md

 ---
-layout: wip
+layout: cp
 title: "0xFFFC full-time C++ development (3 months, May, June, July, 2024)"
 author: 0xFFFC
 date: 21 March 2024
@@ -15,15 +15,15 @@ milestones:
     status: finished
   - name: 160 hours
     funds: 30
-    done:
-    status: unfinished
+    done: 14 August 2024
+    status: finished
 payouts:
   - date: 20 June 2024
     amount: 30
   - date: 19 July 2024
     amount: 30
-  - date:
-    amount:
+  - date: 26 August 2024
+    amount: 30
 ---
 
 ### What

0xfffc-2024Q3.md

+---
+layout: cp
+title: "0xfffc full-time C++ development (3 months, Sep, Oct, Nov, 2024)"
+author: 0xfffc
+date: 14 Aug 2024
+amount: 111
+milestones:
+  - name: 160 hours
+    funds: 37
+    done: 30 September 2024
+    status: finished
+  - name: 160 hours
+    funds: 37
+    done: 14 November 2024
+    status: finished
+  - name: 160 hours
+    funds: 37
+    done: 25 December 2024
+    status: finished
+payouts:
+  - date: 7 October 2024
+    amount: 37
+  - date: 15 November 2024
+    amount: 37
+  - date: 4 January 2025
+    amount: 37
+---
+  
+### What
+
+The bulk of my focus will be on opportunities related to performance improvement. To find out performance improvement opportunities a performance test suite is necessary for the Monero project. Here is a list of tasks I have on my todo list:
+
+- Dynamic BSS: The issue is dynamic BSS (block-sync-size) size. If BSS goes over a threshold, then we hit the packet limit size (100mb). I expect to hit the serialization limit (https://github.com/monero-project/monero/pull/9433) too at some point if we fix the packet size limit. This one hopefully will be solved by the time this CCS kicks in.
+
+- Bandwidth-Efficent Transaction Propagation Usage: Work on the @boog900 proposal ( https://github.com/monero-project/monero/issues/9334 ). And reduce the communication load between peers when syncing. The final goal is to merge a PR that uses this mechanism in Monero P2P subsystem. 
+
+- OOM: Spend time on finding the root cause of OOM. Report to community and eventually submit PR fixing it.
+
+- Exclusive incoming ip: --exclusive-incoming-ip flag: (a) Require --add-exclusive-node to be set. (b) Be able to be set multiple times.
+
+- Cleanup the sleepwait: Remove this _sleep_wait_ and change it to condition variable: https://github.com/monero-project/monero/blob/cc73fe71162d564ffda8e549b79a350bca53c454/src/daemon/daemon.cpp#L198
+
+- Sync time estimation: When calculating how long it will take to finish the sync, is uses a number of blocks. Example: 200 blocks remaining, synced 20 blocks in 1 min = 10 mins remaining. It should use the size, instead of the block number.
+
+- Performance benchmarks. The performance benchmark test I am working on right now is stress testing Monerod under an intense load that tries to mimic a real-world heavy node. Right now it is in very early shape. The end goal is to mimic real-world wallet usage on the Monero daemon.
+
+- Completion of Read/Write Lock PR [#9181](https://github.com/monero-project/monero/pull/9181). PR 9181 is a huge change to the core of the blockchain implementation of the Monero project. It requires a lot of careful analysis and testing. Task 1 and Task 2 are kind of depend on each other. I use benchmarking results from task 1 to test/improve/debug 9181. @jeffro256_ has implemented an important and sensitive part of the 9181 code and has improved the PR with his suggestions.
+
+- Seraphis wallet LMDB storage. Based on our discussion in the IRC #monero group, it seems porting the entire wallet2 storage to LMDB at this point is not a wise decision. Instead of that, we should start implementing the Seraphis wallet cache with LMDB. Once I am finished with Task 1 and 2, my next big goal is to start focusing on this task. The target of this task is to have Seraphis wallet only using LMDB as its cache/storage engine.
+
+- Static analysis. This task hasn't been finished from my previous CCS by the time I am submitting this CCS. I am hopeful I will finish it before the end of my previous CCS. But in case I am not able to finish it, this is one of the tasks I have on my todo list: "Analyze existing static analyzers (clangd-based analyzer, NASA/ikos, Facebook/infer, etc) and report to @selsta about the possibility of adding one of them as a workflow to our GitHub repository. Target will be running static analysis on submitted PR as workflow."
+
+### Who
+
+I have been contributing to the Monero core repository for the past few months with a total of multiple ([PRs]( https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3A0xFFFC0000+)) merged commits thus far. Some ongoing contributions:
+
+- Helped review multiple [PRs](https://github.com/monero-project/monero/pulls?q=is%3Apr+reviewed-by%3A%40me).
+- Implemented Read/Write lock mechanism for core blockchain implementation. [9181](https://github.com/monero-project/monero/pull/9181).
+- Helped to review and fix multiple HackerOne reports with @selsta.
+
+A special thanks to all community members who are always available to help me with technical questions.
+  
+Previous Proposals:
+  
+- [429](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/429)
+- [438](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/438)
+
+### Funding
+
+- 37xmr/mth * 3 months = 111xmr
+
+- Schedule: 40hr/week * 12week
+
+
+Freedom wins.
+0xFFFC

Lovera-Create-educational-content-Spanish.md

 ---
-layout: wip
+layout: cp
 title: Create Educational Content in Spanish
 author: Lovera
 date: August 28, 2023
@@ -15,15 +15,15 @@ milestones:
     status: finished
   - name: Videos and Educational Articles
     funds: 3.5 XMR
-    done:
-    status: unfinished
+    done: 16 February 2025
+    status: finished
 payouts:
   - date: 11 November 2023
     amount: 3.5
   - date: 15 January 2024
     amount: 3.5
-  - date:
-    amount:
+  - date: 25 February 2025
+    amount: 3.5
 ---
 
 ### Introduction

MoneroKon-2025-CCS.md

+---
+layout: wip
+title: MoneroKon 2025 CCS
+author: hbs
+date: February 24, 2024
+amount: 99
+milestones:
+  - name: Funding goal reached
+    funds: 99
+    done:
+    status: unfinished
+payouts:
+  - date:
+    amount:
+---
+
+# Table of Contents
+
+- [Who?](#who)
+- [What?](#what)
+- [Amount](#amount)
+- [Exchange Rate](#exchange-rate)
+
+# Who:
+
+I, hbs, am one of many MoneroKon staff members contributing to this funding proposal. I have been actively involved with the Monero project for several years and have taken part in MoneroKon organizing team since its 2022 edition in Prague. This CCS proposal is intended to support the work of a larger team, not just my own. Active community members, including ajs, midipoet, monerobull, franciscom, dadajo, comradeblin, Siren, ceetee, recanman, and others, coordinate and hold weekly meetings in the [#monerokon Matrix room](https://matrix.to/#/#monerokon:matrix.org).
+In 2024, a Czech non-profit [Twisted Edwards z.s.](https://twed.org/) was set up to support education and scientific research in cryptography, distributed systems, and information technology security. Siren, ajs, and midipoet volunteered as directors of Twisted Edwards z.s., with their roles confirmed through community voting. Twisted Edwards z.s. oversees the organization of MoneroKon and is responsible for contracting essential services, including the venue, A/V staff, equipment rentals, food trucks, storage, and more.
+As of 19 February 2025, Twisted Edwards holds approximately 32,200 EUR in stablecoins in a [Safe Polygon multisig wallet](https://polygonscan.com/address/0x22942517e3eDEF1e1016070951a7081F99AE50A3) and 105.43 XMR in a hardware wallet in accordance with the [Cryptocurrency Funds Management Policy](https://github.com/MoneroKon/meta/blob/main/policies/funds-management-policy.md).
+All MoneroKon staff members are unpaid volunteers.
+
+# What
+
+[Monero Konferenco (“MoneroKon”)](https://www.monerokon.org/) is an annual gathering of privacy advocates, cypherpunks, scientists, and philosophers focused on advancing privacy and financial technologies such as censorship-resistant digital cash. The event first took place in Denver, Colorado in 2019, and after a hiatus due to COVID-19, it resumed in Lisbon, Portugal in 2022. In 2023 and 2024, MoneroKon was held in Prague.
+The popularity of MoneroKon has steadily increased, with growing attendance over the years:
+
+* 2019 - Denver - 73 attendees - [27 speakers](https://www.youtube.com/playlist?list=PLsSYUeVwrHBkJHJg_l2uDgbicDJ1PmAVW)
+* 2022 - Lisbon - 160 attendees - [40 speakers](https://www.youtube.com/playlist?list=PLsSYUeVwrHBndRQoQ-vLezzlHPLRDNzaw) |
+* 2023 - Prague - 200 attendees - [~40 speakers](https://www.youtube.com/playlist?list=PLsSYUeVwrHBm1m7IaU3JiDVb5EC7cn0KG) |
+* 2024 - Prague - 300 attendees - [~40 speakers](https://www.youtube.com/playlist?list=PLsSYUeVwrHBk-C3zImaDAQLx453PL7dR-) |
+
+Previous MoneroKon editions in [2019](https://forum.getmonero.org/22/completed-tasks/90909/surae-noether-first-denver-monero-konferenco-spring-2019) ([postmortem](https://github.com/ajs-xmr/mrl-skunkworks-mirror/blob/master/Konferenco/2019/postmorto.md#1-budget-actuals)), [2022](https://ccs.getmonero.org/proposals/MoneroKon-2022-CCS.html), and [2023](https://ccs.getmonero.org/proposals/monerokon-2023-ccs-1.html) were partially funded through the CCS. For MoneroKon 2024, the organizers aimed to make the event self-funded through ticket sales and sponsorships. A concerted effort was made to keep costs low, such as by renting a smaller section of the venue. The previous edition taught us that a smaller, more intimate space created a better experience for all attendees. Feedback confirmed that this was a successful change. Moreover, cost savings efforts resulted in approximately 20,000 EUR net surplus, which has been rolled over to finance future editions of the conference.
+
+For MoneroKon 2025, we also aim to achieve self-funding through ticket sales and sponsorships. However, as of February 2025, several [sponsor slots](https://www.monerokon.org/sponsor.html) remain unfilled. The funds raised so far, combined with the surplus from the previous edition and projected ticket sales, suggest a potential shortfall for paying some major suppliers on time. Additionally, some community members have expressed concerns about seeking sponsorships from "pre-mined" or "dev-tax" funded projects, contributing to delays in sponsor outreach efforts. Given the economic uncertainty, we are requesting community funding via this CCS proposal to bridge the gap until ticket sales and sufficient sponsorships are fully secured.
+
+Compared to earlier editions, MoneroKon 2025 has a more modest budget. The [current budget](https://cryptpad.monerokon.org/sheet/#/2/sheet/view/t+QGKaxkHNqtRn2HKQlM168Cddh5G3uh6aO7uuyGnOc/embed/) will remain balanced if sponsorships and ticket sales meet the specified targets. To ensure the event proceeds smoothly, the organizing team is requesting 20,000 EUR in funding as a safety buffer. The funds raised will be used for MoneroKon-related expenses. Any leftover funds will be allocated to future editions of the conference.
+
+MoneroKon 2025 Budget Breakdown:
+
+* La Fabrika, event venue - 33,520 EUR - 42.6% of total
+* A/V and livestreaming - 4,612.2 EUR - 5.9% of total
+* [Speaker](https://github.com/MoneroKon/meta/blob/main/policies/contributor-travel.md) and [staff](https://github.com/MoneroKon/meta/blob/main/policies/staff-travel.md) travel reimbursement - 9,000 EUR - 11.4%
+* IT Stuff - 4,000 EUR - 5.1%
+* Accounting and tax related expenses - 6,260 EUR - 8%
+
+The "IT Stuff" category is a one-time investment in network and IT infrastructure. This equipment will be reused for future editions, as we cannot rely on the venue’s Wi-Fi to meet the high standards expected by our attendees. The investment includes dedicated local nodes (one for P2P and one for RPC) to ensure the best possible Monero transaction experience. It will also allow us to set up multiple screens with high-quality livestreaming, reducing the need for extra rental equipment.
+
+As attendee numbers continue to grow, MoneroKon 2025 is likely to be the last edition at this venue. The organizing team has already begun scouting alternative venues for MoneroKon 2026, and initial findings suggest that venue costs may be lower, further reducing the need for community funding.
+
+# Amount and milestone
+
+The MoneroKon 2025 organizing team is seeking to raise 99 XMR and, given the nature of event organization and the track record of the team for delivering the previous editions, proposes a single milestone for full amount released on reaching funding goal.
+# Exchange rate
+20,000 EUR / 223.650 EUR ([EMA50 Euro monthly rate](https://www.investing.com/crypto/monero/xmr-eur-technical)) + 10% volatility buffer = 99 XMR

Rucknium-OSPEAD-Fortifying-Monero-Against-Statistical-Attack.md

@@ -11,8 +11,8 @@ milestones:
     status: finished
   - name: Milestone 2 - Deliver initial probability density function to scientific review panel
     funds: 74
-    done:
-    status: unfinished
+    done: 15 January 2025
+    status: finished
   - name: Milestone 3 - Deliver final version of probability density function to Monero developers
     funds: 30
     done:
@@ -20,8 +20,8 @@ milestones:
 payouts:
   - date: 24 September 2022
     amount: 67
-  - date:
-    amount:
+  - date: 23 January 2025
+    amount: 74
   - date:
     amount:
 ---

Rucknium-Statistical-Research.md

@@ -7,21 +7,21 @@ amount: 204
 milestones:
   - name: Month 1
     funds: 33% (68 XMR)
-    done:
-    status: unfinished
+    done: 10 October 2024
+    status: finished
   - name: Month 2
     funds: 33% (68 XMR)
-    done:
-    status: unfinished
+    done: 18 February 2025
+    status: finished
   - name: Month 3
     funds: 33% (68 XMR)
     done:
     status: unfinished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 16 October 2024
+    amount: 68
+  - date: 26 February 2025
+    amount: 68
   - date:
     amount:
 ---

SNeedlewoods-01_part-time-dev-work-1-month.md

+---
+layout: cp
+title: SNeedlewoods-01_part-time dev work (1 month)
+author: Sneedlewooods
+date: October 4, 2024
+amount: 2.15
+milestones:
+  - name: month 1
+    funds: 18.64
+    done: 4 December 2024
+    status: finished
+payouts:
+  - date: 13 December 2024
+    amount: 18.64
+---
+
+## What?
+
+For this proposal the focus of work will be on the new wallet API ([context](https://github.com/monero-project/monero/issues/9308)). The work is already ongoing since May 2024, there is [this PR](https://github.com/monero-project/monero/pull/9368) to organize functions and [this branch](https://github.com/monero-project/monero/compare/master...SNeedlewoods:seraphis_wallet:x_api_comments) to add comments, but most recent and most important is this [WIP PR](https://github.com/monero-project/monero/pull/9464) that adds functions to the API to make it "feature-complete" with `wallet2`.
+
+There will not be a direct deliverable for the milestone and it's very unlikely the feature-complete API will be completely done (including reviews) before this proposal ends, but here are alternatives I would work on:
+- If current API PR gets finished:
+  - Help with step 2 from [this proposal](https://github.com/seraphis-migration/wallet3/issues/64): "Stop using the wallet2 object in the CLI and RPC wallets and instead use the wallet API."
+  - Add unit_tests for the wallet API, or try to resurrect libwallet_api_tests (which are [temporarily disabled](https://github.com/monero-project/monero/blame/9866a0e9021e2422d8055731a586083eb5e2be67/Makefile#L60))
+- If for any reason current API PR gets blocked:
+  - Things found during the API work, mostly in CLI and RPC wallet. An incomplete list can be found [here](https://github.com/SNeedlewoods/seraphis_wallet/issues/1).
+
+I give weekly updates on what I've worked on in the "Monero Tech Meeting", where I also get feedback from more experienced devs to decide which way to go.
+
+Besides that I try to help out where I can.
+This is a "pilot" proposal to see how things work out. If the majority is satisfied at the end of this proposal, I see it as confirmation that I can justify putting more time and energy into Monero (and will increase my hourly rate in future proposals). Hopefully I will become a long term contributor for general development.
+
+I aim for 15+ hours/week on average, but for precaution I won't promise more than 10 hours/week.
+
+
+## Who?
+
+Hey, I'm SNeedlewoods, since early 2023 I'm lurking around in the Monero community.
+In November 2023 I joined the weekly "Seraphis wallet workgroup meeting" (now called "Monero Tech Meeting") in the [no-wallet-left-behind](https://matrix.to/#/#no-wallet-left-behind:monero.social) matrix room and got encouraged by our friendly and very helpful devs to start coding for Seraphis.
+Only when the main focus in development shifted from Seraphis to FCMPs earlier this year, I started working on Monero core or more accurately on wallet related stuff.
+
+Admittedly I don't have much to show and my expertise is not on par with other contributors, but I think considering the amount I'm asking for this proposal is fair.
+
+Code contributions so far:
+[Seraphis](https://github.com/UkoeHB/monero/pulls?q=is:pr+author:SNeedlewoods)
+[Monero](https://github.com/monero-project/monero/pulls?q=is:pr+author:SNeedlewoods)
+
+
+## Payment
+
+Work 10 hours/week for 1 month.
+10 (hours/week) * 4.3 weeks_per_month = 43 hours total. I am setting my hourly rate at 0.05 XMR/hour regardless of fiat market price (but for those who care, that is roughly around 6,50€ or $7.50 per hour, according to the current 7-day range on coingecko: 123,43€-147,32€ or $136.38-$164.58), that makes for a total of 2.15 XMR.

SNeedlewoods-02_part-time-dev-work.md

+---
+layout: wip
+title: SNeedlewoods-02_part-time dev work
+author: SNeedlewooods
+date: January 27, 2025
+amount: 23
+milestones:
+  - name: M1 - Harden sensitive material in the Wallet API
+    funds: 2.4
+    done:
+    status: unfinished
+  - name: M2 - Replace wallet2 with Wallet API in simplewallet
+    funds: 20.6
+    done:
+    status: unfinished
+payouts:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+## What?
+
+Since the feature-complete Wallet API [PR](https://github.com/monero-project/monero/pull/9464) from my previous CCS proposal is finally in "pending review" state (I will give my best to quickly resolve issues coming up during the review, so it hopefully will get merged soon), it's time for the next steps:
+- Harden handling of sensitive material in the Wallet API (Discussions: [#1](https://github.com/monero-project/monero-gui/issues/1537), [#2](https://github.com/feather-wallet/feather/issues/72#issuecomment-1405602142), [#3](https://github.com/monero-project/monero/pull/8619#issuecomment-1632951461)).
+- Replace wallet2 with the Wallet API in simplewallet as proposed [here](https://github.com/seraphis-migration/wallet3/issues/64) in step 2 by @j-berman.
+
+I'll try to spend at least 12 h/week coding.
+
+
+## Who?
+
+This is my second proposal, the previous one can be found here:
+
+- [Proposal 1](https://ccs.getmonero.org/proposals/SNeedlewoods-01_part-time-dev-work-1-month.html)
+
+
+## Milestone
+
+(Disclaimer: I can't promise the estimated times are accurate, but I tried to keep them low and I'll take the risk if a milestone takes longer to complete.)
+
+1. M1 (2.4 XMR): PR to harden handling of sensitive material in the Wallet API is merged to monero-project/monero
+   - Stop caching the password (in Wallet API and GUI)
+   - Use `epee::wipeable_string` instead of `std::string` for secret keys
+   I estimate this can be completed in ~ 2 weeks, which makes:
+   12 (h/week) * 2 (weeks) = 24 (h total M1).
+
+2. M2 (20.6 XMR): PR to replace wallet2 with the Wallet API in simplewallet is merged to monero-project/monero
+   I estimate this can be completed in ~ 4 months, which makes:
+   12 (h/week) * 4.3 (weeks/month) * 4 (months) = 206.4 (h total M2).
+
+
+## Payment
+
+I am setting my rate at 0.1 (XMR/h) regardless of fiat market price (but for reference, that is roughly around 20,50€ or $21.50 per hour, according to the current 7-day range on coingecko: 195,68€-217,73€ or $202.95-$226.65).
+
+M1: 24 (h) * 0.1 (XMR/h) = 2.4 (XMR).
+M2: 206.4 (h) * 0.1 (XMR/h) = 20.64 (XMR).
+
+That makes for a (rounded) total of:
+2.4 (XMR) + 20.64 (XMR) = 23 (XMR total).

VOSTOEMISIO-Continuation-of-Core-Monero-Concepts-A-Series-of-Animated-Explainers.md

@@ -3,7 +3,7 @@ layout: cp
 title: Continuation of Core Monero Concepts - A Series of Animated Explainers
 author: VOSTOEMISIO
 date: October 3, 2023
-amount: 1
+amount: 37
 milestones:
   - name: Random X and Understanding the significance of ASIC resistance
     funds: 18
@@ -20,19 +20,21 @@ payouts:
     amount: 18
 ---
 
+_Note: this proposal has been awarded 36 XMR from [New Animated Videos](https://ccs.getmonero.org/proposals/savandra-videos-for-monero.html)_
+
 Hey all!
 
 Thank you for the amazing reception and feedback of our first ccs-proposal and the Tail Emission video. We've seen a lot of excitement and engagement with over 7,000 accumulated views in just the initial days.
 
 Our vision is to keep diving deeper into Monero's complex and sometimes tricky and misunderstood features, translating them into short, engaging, and most importantly, understandable animated videos. Here's what we suggest to cover in this proposal:
 
-•	Random X: Understanding the significance of ASIC resistance
+• Random X: Understanding the significance of ASIC resistance
 
-•	Breaking down the how-to and the rationale for P2Pool.
+• Breaking down the how-to and the rationale for P2Pool.
 
-•	Nodes: Why every Monero enthusiast should consider running one.
+• Nodes: Why every Monero enthusiast should consider running one.
 
-•	Fungibility: Explaining its essence in the context of Monero.
+• Fungibility: Explaining its essence in the context of Monero.
 
 Quality & Timeline: 
 

VOSTOEMISIO-FCMP-Animated-Explainer.md

+---
+layout: cp
+title: "VOSTOEMISIO - FCMP Animated Explainer Video"
+author: VOSTOEMISIO
+date: July 29, 2024
+amount: 20
+milestones:
+  - name: Complete FCMP Video
+    funds: 20
+    done: 16 December 2024
+    status: finished
+payouts:
+  - date: 13 January 2025
+    amount: 20
+---
+
+Hey Everyone,
+
+We are happy to inform you that we have already received private funding for the introductory
+Monero video, and therefore, we have adjusted the proposal accordingly.
+After receiving the community’s feedback, we're now excited to present our revised proposal:
+one explainer video about FCMP (Full-Chain Membership Proofs). This will be our 4th video for
+the Monero CCS.
+
+Our previous videos covering core Monero concepts like Tail Emission, the importance of
+running a node, and RandomX have been informative, engaging, and uploaded on
+Getmonero.org, shared across X and YouTube. We believe that visual learning and breaking
+down complex ideas into digestible formats is highly effective, and we aim to do the same with
+FCMP.
+
+References:
+1. [Youtube - Monero's Tail Emission](https://youtu.be/vjn9l3hG4ME)
+2. [Youtube - Monero Nodes](https://youtu.be/hM6TF3co7lI)
+3. [Youtube - Monero's RandomX](https://youtu.be/RsNOi0lpiyM)
+
+Although we haven't finalized the script yet for the FCMP video, we're committed to delivering a
+high-quality video approximately 2-3 minutes long, or however long it needs to be to effectively
+explain the concept. We're proposing a budget of 20 XMR for this video. This is slightly higher
+than our initial proposal since we agreed to extend the scope to include both dark and light
+backgrounds. As before, Xenu will assist with the script and storyboard, with 5 XMR allocated
+for his contribution. Additionally, we've reached out to kayabaNerve (Luke Parker) for
+fact-checking the script to ensure accuracy, and he's agreed to help us. A big thanks to him for
+his support.
+
+As always, we will open-source our project materials after completion.
+We believe we've done a good job of gathering the community's feedback so far in our previous
+proposals, and we'll continue to do so by posting our script and storyboards on Matrix and here
+in the repo.
+
+If anyone has any questions or suggestions, please feel free to chime in.
+
+Thanks!

acx-monfluo-maintenance-and-further-development.md

+---
+layout: wip
+title: acx part-time work on Monfluo (3 months)
+author: acx
+date: February 28, 2025
+amount: 13.98
+milestones:
+  - name: Month 1
+    funds: 4.66 XMR
+    done:
+    status: unfinished
+  - name: Month 2
+    funds: 4.66 XMR
+    done:
+    status: unfinished
+  - name: Month 3
+    funds: 4.66 XMR
+    done:
+    status: unfinished
+payouts:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+## Who
+
+Hi, I am acx.  
+About six months ago I have forked Mysu (an abandoned Android wallet) and continued its development and maintenance.  
+The fork is named Monfluo and is available [here](https://codeberg.org/acx/monfluo)  
+
+Since starting the fork, I did (among other things) the following:  
+
+* Implemented multi-wallet functionality (also wallet renames and deletion)
+* Implemented multi-account functionality
+* Separated wallet password and seed offset (previously you could not set them to different values)
+* Reworked secrets tab, allowing the user to apply seed passpharse offset when saving seed
+* Fixed a bug where sync progress was lost when the wallet was closed before the sync is finished
+* Implemented APK building in the pipeline (making it easier for users to test any commit without waiting for a release)
+* and several other changes, you can check all of them [here](https://codeberg.org/acx/monfluo/compare/b939d526652d174eb6081a0b5e9dd407c409c90a...master)
+
+Monfluo is by design a very simple wallet, and one of the goals is having no "integrations" such as swapping services, sending to other cryptos, fiat on/off-ramps, etc. I do not earn any fees from the wallet.
+
+## What
+
+I will continue maintenance and development of Monfluo. I will be working on the things listed [here](https://codeberg.org/acx/monfluo/issues), among the most important ones:
+
+* Updating to newer Monero versions, when required
+* Setting up a clearnet F-Droid repo together with an onion mirror
+* Setting up translations
+* Issues [#67](https://codeberg.org/acx/monfluo/issues/67) and [#71](https://codeberg.org/acx/monfluo/issues/71)
+* Working on making Monfluo reproducible (I do **not** expect to finish this one during this CCS, but I want to start investigating it)
+
+## Funding
+
+I am asking for 25$/h.  
+With 40 hours a month (~9 hours a week) \* 3 months at ~$215/XMR this makes 25\*40\*3/215 ~= 14 XMR  
+

boog_3_months_cuprate.md

 ---
-layout: wip
+layout: cp
 title:  Boog900 full time work on Cuprate (3 months)
 author: Boog900
 date: January 27, 2024
@@ -19,13 +19,13 @@ milestones:
     status: finished
   - name: P2P Documentation
     funds: 28 XMR
-    done:
-    status: unfinished
+    done: 18 July 2024
+    status: finished
 payouts:
   - date: 20 June 2024
     amount: 162
-  - date:
-    amount:
+  - date: 1 August 2024
+    amount: 28
 ---
 
 This proposal is to continue my work on [Cuprate](https://github.com/Cuprate/cuprate), specifically I will be working on

boog_3_months_cuprate_2.md

 ---
-layout: wip
+layout: cp
 title:  Boog900 full time work on Cuprate (3 months)
 author: Boog900
 date: June 28, 2024
@@ -7,23 +7,23 @@ amount: 215
 milestones:
   - name: Month 1
     funds: 71 XMR
-    done:
-    status: unfinished
+    done: 4 September 2024
+    status: finished
   - name: Month 2
     funds: 72 XMR
-    done:
-    status: unfinished
+    done: 29 October 2024
+    status: finished
   - name: Month 3
     funds: 72 XMR
-    done:
-    status: unfinished
+    done: 6 January 2025
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 27 September 2024
+    amount: 71
+  - date: 10 November 2024
+    amount: 72
+  - date: 21 January 2025
+    amount: 72
 ---
 
 This proposal is to continue my work on [Cuprate](https://github.com/Cuprate/cuprate).

boog_3_months_cuprate_3.md

+---
+layout: wip
+title:  Boog900 full time work on Cuprate (3 months) + January
+author: Boog900
+date: February 11, 2025
+amount: 160
+milestones:
+  - name: January
+    funds: 40 XMR
+    done:
+    status: unfinished
+  - name: Month 1
+    funds: 40 XMR
+    done:
+    status: unfinished
+  - name: Month 2
+    funds: 40 XMR
+    done:
+    status: unfinished
+  - name: Month 3
+    funds: 40 XMR
+    done:
+    status: unfinished
+payouts:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+# Who
+
+I am [Boog900](https://github.com/Boog900), you can see my last CCS [here](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/469).
+
+# What
+
+I will work for 3 months on Cuprate with an initial focus on releasing an alpha `cuprated`, the basic roadmap can be seen here: https://github.com/Cuprate/cuprate/issues/376.
+I plan to work on what I think is best to advance the project.
+
+I am also asking for payment for the hours I worked in January. We had some discussions about changing the way we
+get funded, potentially making a combined "cuprate CCS", however we decided against it, this lead to the delay of this CCS. 
+A list of things I did during January:
+
+- finished the init PR: https://github.com/Cuprate/cuprate/pull/344
+- worked on improving our consensus API: https://github.com/Cuprate/cuprate/pull/366, to prepare for fast-sync.
+- Started working on [issue 174](https://github.com/Cuprate/cuprate/issues/174): https://github.com/Cuprate/cuprate/pull/382
+- Investigated why monerod was syncing the first 100,000 blocks faster than cuprated, which lead to this PR: https://github.com/Cuprate/cuprate/pull/377
+- Started working on changing monero-oxide's tx type to use compressed points: https://github.com/Cuprate/serai/tree/monero-comp-points
+- Started working on fast-sync: https://github.com/Cuprate/cuprate/tree/fast-sync
+
+All the tasks that have been started are pretty much ready just need to be cleaned up, they are all used in the fast-sync branch
+which a few people have tested syncs on, the quickest sync _so far_ was just over 4 hours.
+
+# Funding 
+
+I am asking for 40 XMR for my work in January.
+
+$55/hr for 480 hrs at $220/XMR: 120 XMR
+
+total: 160 XMR

bulletproofs-pp-peer-review.md

 ---
-layout: wip
+layout: cp
 title: Bulletproofs++ Peer Review
 author: Monero Research Lab
 date: March 22, 2023
@@ -11,13 +11,13 @@ milestones:
     status: finished
   - name: Bp++ eprint peer review GenFund part
     funds: ~$14000
-    done:
-    status: unfinished
+    done: 29 March 2024
+    status: finished
 payouts:
   - date: 7 March 2024
     amount: 130
-  - date:
-    amount:
+  - date: 7 April 2024
+    amount: 101
 ---
 
 ## Bulletproofs++ Peer Review

busyboredom-standalone-acceptxmr.md

@@ -3,7 +3,7 @@ layout: wip
 title: Standalone AcceptXMR
 author: busyboredom
 date: February 31, 2023
-amount: 14
+amount: 44
 milestones:
   - name: Dockerize AcceptXMR
     funds: 14
@@ -20,8 +20,14 @@ milestones:
 payouts:
   - date: 19 July 2024
     amount: 14
+  - date:
+    amount:
+  - date:
+    amount:
 ---
 
+_Note: this proposal has been awarded 30 XMR from [xmrSale](https://ccs.getmonero.org/proposals/xmrsale-2021.html)_
+
 # Standalone AcceptXMR
 Another payment gateway CCS proposal.
 

ccs-coordinator-5-plowsof.md

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

cypherstack-carrot-spec-review.md

+---
+layout: wip
+title: Carrot Spec Peer Review
+author: Monero Research Lab
+date: October 11, 2024
+amount: 126
+milestones:
+  - name: Carrot spec peer review
+    funds:
+    done:
+    status: unfinished
+payouts:
+  - date: 24 October 2024
+    amount: 126
+---
+
+## Carrot Peer Review
+
+This CCS will provide funding for the first step towards a Carrot implementation in Monero. Carrot is a specification for a backwards-compatible addressing protocol, as well as a new wallet key hierarchy for the upcoming FCMP++ consensus upgrade. This peer review will be over the specification, not any specific implementation. CypherStack was chosen for this audit from among several firms during the Monero Resarch Lab meetings the last couple weeks.
+
+## Scope / Deliverables
+
+A full peer review of the spec document [[link](https://github.com/jeffro256/carrot/blob/master/carrot.md)]. Note that at the time of writing this proposal, the paper is not yet published in a peer-reviewed conference/journal.
+
+The deliverable is a write-up which will include security proofs for all properties listed in section 9. It will also include notes on weaknesses, issues, or recommendations (if any). In the case that a security proof is not possible, a note will be included describing why that proof is not possible. In the case that CypherStack requires more funds to complete the security proofs, an MRL meeting will be held and a new CCS may be opened.
+
+## Out of scope
+
+- Multiparty computation. There are no specific protocols presented for this, and no corresponding security model of proofs of security.
+- Collaborative construction. For the same reason as multiparty computation.
+
+## Funding
+
+Because CypherStack has had a long successful history with Monero, has agreed to accept the XMR directly, wishes to mitigate volatility risks, and has received upfront payment for reviews before, the 126 XMR for this review is to be paid out in full to Cypherstack immediately upon reaching the funding goal.