escapethe3ra-monero-observer-2024-q3.md

+---
+layout: cp
+title: escapethe3RA Monero Observer maintenance (2024 Q3)
+author: escapethe3RA
+date: Jul 10, 2024
+amount: 42
+milestones:
+  - name: July
+    funds: 14
+    done: 31 July 2024
+    status: finished
+  - name: August
+    funds: 14
+    done: 31 August 2024
+    status: finished
+  - name: September
+    funds: 14
+    done: 1 October 2024
+    status: finished
+payouts:
+  - date: 5 September 2024
+    amount: 28
+  - date: 10 October 2024
+    amount: 14
+---
+
+# What
+
+I will continue to maintain *Monero Observer* (https://monero.observer) for the next 3 months (2024 Q3): July, August and September.
+
+Tasks:
+
+- Daily: search, curate, structure and post new reports/stories
+- Daily: update reports, stats, changelog
+- Daily/As Needed: post new *MO Community Messages*
+- Daily/As Needed: post new *MO Resources* and *Blacklist* items
+- Daily/As Needed: post new *MO Calendar Events*
+- Weekly (Sunday): publish the *Monero Dev Activity Report*
+- Weekly (Saturday): publish the *MO Artistic Saturday Top 5 Report*
+- Monthly (1st): publish the *MO Blitz Report*
+- As Needed: publish the *MO Cypherpunk Transmission Report*
+- As Needed: housekeeping (revise and update reports)
+- As Needed: engage with the community on Matrix, XMPP, emails
+- As Needed: make sure the website is live and working as expected (server maintenance, billing, etc)
+- Optional/bonus: publish new Monero and privacy related guides, meeting logs and summaries, add new features, improvements and website sections, start new community initiatives
+
+# Who
+
+escapethe3RA, I have started contributing to the Monero ecosystem in August 2021 with Monero Observer and other smaller projects:
+
+- published 2677 x daily MO stories/reports (https://monero.observer/stories)
+- published 1299 x on demand MO Community Messages (https://.monero.observer/tag/community)
+- published 31 x monthly MO Blitz reports (https://monero.observer/tag/blitz)
+- published 106 x weekly Monero Dev Activity Reports (https://monero.observer/tag/dev)
+- published 112 x weekly MO Artistic Saturday Top 5 Reports (https://monero.observer/tag/art)
+- published 56 x weekly MO XMR TA reports (https://monero.observer/tag/analysis)
+- published 27 x on demand Monero Workgroup Meeting Log Summaries & uploaded 280 meeting logs to MO (https://monero.observer/tag/logs/)
+- published 17 x on demand MO Cypherpunk Transmission reports (https://monero.observer/tag/CT)
+- added 342 x on demand MO Resources (https://monero.observer/resources) & 18 x Blacklist items (https://monero.observer/blacklist)
+- posted 385 x on demand Calendar events (https://monero.observer/tag/calendar)
+- created several Monero, privacy and security related guides (https://monero.observer/tag/guides/, https://monero.observer/verify-install-update-monero-cli-wallet-linux-guide/, https://monero.observer/ultimate-guide-new-monero-contributors/, https://monero.observer/gpg-cleartext-signatures/, https://monero.observer/gpg-generate-full-keypair/, https://monero.observer/list-anon-email-service-providers/, https://monero.observer/read-monero-observer-terminal-newsboat/, https://monero.observer/monero-cli-wallet-cheat-sheet/)
+- redesigned *Monero Means Money* website, donated bounty to GF (https://moneromeans.money/, https://github.com/escapethe3RA/monero-means-money/)
+- started multiple MO initiatives: Community Messages, Monero Dev Activity Report, XMR TA Report, MO Artistic Saturday, and Cypherpunk Transmission  (https://monero.observer/tag/community, https://monero.observer/tag/dev/, https://monero.observer/tag/analysis, https://monero.observer/tag/art, https://monero.observer/tag/CT)
+- added multiple MO sections: XMR Stats, Resources, Calendar, Blacklist (https://monero.observer/stats/, https://monero.observer/resources/, https://monero.observer/tag/calendar/, https://monero.observer/blacklist/)
+- added multiple RSS feeds (https://monero.observer/rss/)
+- other project improvements (https://monero.observer/changelog/)
+ 
+# Proposal
+
+I will work for 25 hours per week over 3 months at a rate of 0.14 XMR / hour. At ~$160 / XMR (21 daily EMA) this makes 42 XMR (0.14 * 100 * 3).
\ No newline at end of file

fcmp++-development.md

+---
+layout: wip
+title: Full-Chain Membership Proofs + Spend Authorization + Linkability Development CCS
+author: kayabaNerve
+date: April 13, 2024
+amount: 920 XMR
+milestones:
+  - name: Provide a specification of the circuit and high-level protocol
+    funds: 80 XMR
+    done:
+    status: unfinished
+  - name: Productionize the crate for the arithmetic circuit proof
+    funds: 160 XMR
+    done:
+    status: unfinished
+  - name: Productionize the crate for the Elliptic Curve Divisor Library
+    funds: 80 XMR
+    done:
+    status: unfinished
+  - name: Implement the gadgets
+    funds: 320 XMR
+    done:
+    status: unfinished
+  - name: Implement the circuit
+    funds: 200 XMR
+    done:
+    status: unfinished
+  - name: Implement the Generalized Schnorr Protocol
+    funds: 40 XMR
+    done:
+    status: unfinished
+  - name: Implement multisig for the Generalized Schnorr Protocol
+    funds: 40 XMR
+    done:
+    status: unfinished
+
+payouts:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+This CCS is to develop Full-Chain Membership Proofs (a trustless solution) into Monero under RingCT, replacing the existing CLSAG. This is distinct from prior intents to integrate FCMPs into Monero with Seraphis, and was prior discussed in a [MRL meeting](https://libera.monerologs.net/monero-research-lab/20240401) with well reception. That same meeting organized the [funding of security proofs for Generalized Bulletproofs](https://ccs.getmonero.org/proposals/cypherstack-gbp-security-proofs.html), a critical component for FCMPs (under both this proposal and Seraphis). This builds upon the [work prior done on FCMPs](https://ccs.getmonero.org/proposals/kayabaNerve-fcmp-retroactive.html), and does most of the ground work for FCMPs with Seraphis as well.
+
+The exact deliverables will be:
+- A document detailing the arithmetic circuit (a 'ZK program') and necessary integration work
+- A ready-for-auditing Rust implementation of an amenable (trustless, formally proven, sufficiently performant) arithmetic circuit proof (currently expected to be Generalized Bulletproofs)
+- A Rust library for calculating elliptic curve divisors
+- The FCMP proof, as necessary for usage with RingCT
+- The GSP (Generalized Schnorr Protocol) proof acting as the signature, with multisignature functionality
+
+### Milestones
+
+The milestones are unordered, barring the first to provide a specification. The gadgets will be specified as a series of constraints in a non-machine-interpretable manner intended to allow human understanding and review of the flow and composition. With the definition of the proofs (largely modelled as black boxes to the protocol), all of the supporting infrastructure will also be defined as necessary to comprehend the integration into Monero and new privacy protocol created.
+
+"Productionize the crate for the arithmetic circuit proving system" means to develop the arithmetic circuit proof implementation to the point I endorse auditing it. With those audits, the crate would be eligible for usage in production. Any audits of the implementation would only be sane after the proof implemented is formalized, with security proofs. Currently, the proposed proof is GBPs, and security proofs for it are actively being worked on. If they fail to be proven, this milestone is worded in such a way an alternative proof (with acceptable properties, from being trustless to sufficiently performant to building upon sufficiently accepted academia) may also be accepted. If there are no alternative proofs acceptable, this milestone will be considered not possible at this time, and for the purposes of this CCS, 'failed'.
+
+"Productionize the crate for the Elliptic Curve Divisor Library" means to develop the crate for calculation of divisors into a point it can be audited.
+
+"Implement the gadgets" means to implement the prior-specified gadgets, and all supporting code for them, such that they are ready for soundness proofs, formal verification, auditing, and etc.
+
+"Implement the circuit" means to implement the prior-specified circuit, and supporting high-level functions, to the degree described for the gadgets. This will also include an implementation of the towering curve cycle, Helios and Selene, though not one expected to be performant enough for deployment.
+
+"Implement the Generalized Schnorr Protocol" means to implement the [Generalized Schnorr Protocol](https://eprint.iacr.org/2009/050.pdf) as needed for Monero's usage.
+
+"Implement multisig for the Generalized Schnorr Protocol" means to implement a 2-round multisignature protocol, inspired by FROST, for the aforementioned Generalized Schnorr Protocol. This would have O(n) signing complexity and identifiable aborts.
+
+All of these milestones will be done myself, kayabaNerve. Integration into Monero will be handled externally to this CCS, with jberman stating their intent to submit their own CCS. The steps for integration (regarding new protocol structures and how data such as the tree root will be specified/used when verifying transactions) will be part of the specification from the first milestone.
+
+### Audits
+
+https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/449 establishes an earmarked fund for paying for audits, as necessary for all of the work produced by this CCS. The justification for this structure is mainly provided within that CCS, and is considered out of scope to this CCS.
+
+### Relation to Seraphis
+
+GBPs, the Elliptic Curve Divisor library, the circuit specification (except the first layer), and the gadgets apply to a deployment of FCMPs with Seraphis (making this work largely reusable even if we don't move forward with FCMPs *before* Seraphis). The only part which wouldn't explicitly is the first layer of the circuit (which is currently expected to be composed of two distinct layers) and potentially the Generalized Schnorr Protocol work (as they are not currently used by Seraphis, yet I have proposed their use within Seraphis).
+
+This work, if extended with the forward-secrecy discussions held *and all associated wallet code necessary*, would also be feature-complete with Seraphis. This would leave Seraphis, the protocol, a simpler/potentially more performant protocol, not an upgrade to privacy. This CCS, as currently specified, does not intend to detail all of the wallet upgrades which would be necessary (leaving that to future hard forks, keeping the scope of this concise and minimizing the timeline till deployment).
+
+### Other Necessary Development
+
+As aforementioned, integration must also be done, and development of a performant implementation of the towering curve cycle. While jberman has spoken up for the former, another party will need to be found for the latter (such as tevador, who found the cycle and has expressed domain expertise). Barring finding another party for the latter, I would have to personally learn how to implement efficient modulo arithmetic and step up (a problem left to the future).
+
+### Failure
+
+If the work within this CCS for any reason fails, the funds raised and remaining (held by core, per the rules of the CCS) will roll over into a general MRL research fund to sponsor further research and development, such as proofs for and review of Seraphis. The direction of and process for this new fund will be decided and agreed upon such a roll over occurring by core and discussions within MRL. The idea for this was premised on the idea of hiring researchers, Cypher Stack specifically, on retainer with the MRL having discretion over how those hours were spent. That was discussed at the same meeting as this proposal (proposal as in cryptographic idea, not proposal as in CCS proposal) with sufficiently well reception for me to propose it as the fallback here.

fcmp++-research.md

+---
+layout: wip
+title: "Full-Chain Membership Proofs + Spend Authorization + Linkability Research CCS"
+author: kayabaNerve
+date: April 13, 2024
+amount: 2000
+milestones:
+  - name: Provide a soundness proof for the proof using Elliptic Curve Divisors (MAGIC/Veridise)
+    funds: 70
+    done:
+    status: unfinished
+  - name: Formally verify the gadgets
+    funds: 0
+    done:
+    status: unfinished
+  - name: Prove the composition to be unlinkable, unforgeable, and non-malleable
+    funds: 0
+    done:
+    status: unfinished
+  - name: Audit the Implementation of GBPs
+    funds: 0
+    done:
+    status: unfinished
+  - name: Audit the Elliptic Curve Divisors Library
+    funds: 0
+    done:
+    status: unfinished
+  - name: Audit the implementation of the gadgets
+    funds: 0
+    done:
+    status: unfinished
+  - name: Audit the implementation of the circuit
+    funds: 0
+    done:
+    status: unfinished
+  - name: Audit the implementation of the Towering Curve Cycle
+    funds: 0
+    done:
+    status: unfinished
+  - name: Audit the implementation of the Generalized Schnorr Protocol
+    funds: 0
+    done:
+    status: unfinished
+payouts:
+  - date: 22 May 2024
+    amount: 198
+  - date: 30 May 2024
+    amount: 70
+  - date: 13 August 2024
+    amount: 38
+  - date: 25 November 2024
+    amount: 38.5
+  - date: 13 December 2024
+    amount: 118.5
+  - date: 7 March 2025
+    amount: 53.43
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+This CCS is to prove, review, and audit Full-Chain Membership Proofs (a trustless solution based on Generalized Bulletproofs) into Monero under RingCT, replacing the existing CLSAG. This is distinct from prior intents to integrate FCMPs into Monero with Seraphis, and was prior discussed in a MRL meeting with well reception. That same meeting organized the [funding of security proofs for Generalized Bulletproofs](https://ccs.getmonero.org/proposals/cypherstack-gbp-security-proofs.html), a critical component for FCMPs (under both this proposal and Seraphis). The review and audits here would also lay the ground work for FCMPs with Seraphis as well.
+
+All of these milestones have "?" for their required funds. The goal of this CCS is to raise the funds necessary to contract various external parties. All XMR will be held per the usual CCS policy, by core, until the necessary agreements are made for each milestone. The intention of this is to prevent needing to file several CCSs (addng delays) and to minimize the amount of confusion re: funding efforts. I do not want to have to justify to the community, after 5 CCSs for audits, why a 6th one is still justified and FCMPs aren't a black hole of endless fundraises for audits.
+
+Unfortunately, that last note cannot be completely unavoided. Since there are not auditors ready for each and every milestone, this CCS may run out of funds prior to completion of all milestones (requiring another CCS). The amount chosen (2000 XMR, roughly 230k USD) was chosen on the belief it's reasonable for the scope described. Due to the subject matter (ZK proofs and circuits) currently being one of the hottest fields in the cryptocurrency space at large, with both startups and VCs, I'm unable to provide any such guarantee.
+
+With that note, it may sound optimal to do individualized CCSs. That'd not only add weeks/months to the process (as some of these audits are serialized, so a delay in one adds to the delay in the next), it'd risk being unable to contract certain auditors. In my experience, auditors schedule as long as months out *from time of agreement*. In the time it takes to discuss the proposal and raise the funds, auditors' availability schedules may shift dramatically, including in rates (shifting the amount necessary/adding a deadline for the discussion and fundraising). Hence this proposal.
+
+kayabaNerve and jberman are the people primarily expected to find such parties, with the actual agreement on parties and amount to be by their endorsement, and a general agreement within MRL that the proposed expenditure is reasonable. The word choice of reasonable means that the proposed parties are reasonably trusted to be able to adequately perform the work proposed, the amount to be paid is understandable and amenable, and if there are other potential parties, none are clearly, completely, and definitively better choices. 
+
+If the work within this CCS for any reason fails, or completes with a remaining balance, the funds raised and remaining (held by core, per the rules of the CCS) will roll over into a general MRL research fund to sponsor further research and development, such as proofs for and review of Seraphis. The direction of and process for this new fund will be decided and agreed upon such a roll over occurring by core and discussions within MRL. The idea for this was premised on the idea of hiring researchers, Cypher Stack specifically, on retainer with MRL having discretion over how those hours were spent. That was discussed at the same meeting as this proposal (proposal as in cryptographic idea, not proposal as in CCS proposal) with sufficiently well reception for me to propose it as the fallback here.

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. 
+

gingeropolous_zenith_storage.md

 ---
-layout: wip
+layout: cp
 title: Research Computing Upgrade
 author: Gingeropolous
 date: May 10, 2022
@@ -15,19 +15,17 @@ milestones:
     status: finished
   - name: Month 2 support 
     funds: 8
-    done:
-    status: unfinished
+    done: 23 August 2024
+    status: finished
   - name: Month 3 support 
     funds: 8
-    done:
-    status: unfinished
+    done: 24 August 2024
+    status: finished
 payouts:
   - date: 27 December 2022
     amount: 35
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 4 September 2024
+    amount: 16
 ---
 
 # Gingeropolous CCS Request

gupax.md

 ---
-layout: wip
+layout: cp
 title: "Gupax: GUI for P2Pool+XMRig"
 author: hinto
 date: 10 October 2022
@@ -11,13 +11,13 @@ milestones:
     status: finished
   - name: 1 year of maintenance
     funds: 20% (20 XMR)
-    done:
-    status: unfinished
+    done: 28 December 2023
+    status: finished
 payouts:
   - date: 22 December 2022
     amount: 80
-  - date:
-    amount:
+  - date: 9 January 2024
+    amount: 20
 ---
 
 ![banner.png](https://github.com/hinto-janaiyo/gupax/raw/main/images/png/banner.png)

hardenedsteel-getmonero-1.md

+---
+layout: cp
+title: Part-time + Flexible Work on getmonero.org (1 Month)
+author: HardenedSteel
+date: 31 July, 2024
+amount: 5
+milestones:
+  - name: Month 1
+    funds: 5 XMR
+    done: 15 September 2024
+    status: finished
+payouts:
+  - date: 27 September 2024
+    amount: 5
+---
+
+
+# Who?
+Hi everyone, I'm HardenedSteel. I've been in Monero ecosystem and contributor for a couple of years. My previous contributions in the Monero ecosystem are:
+
+* Maintenance of getmonero.org[1](https://github.com/monero-project/monero-site/issues?q=involves%3Ahardenedsteel)
+* featherwallet.org[2](https://github.com/feather-wallet/feather-site/issues?q=involves%3Ahardenedsteel)
+* revuo-xmr.com[3](https://github.com/rottenwheel/revuo-weekly/issues?q=involves%3Ahardenedsteel)
+* Helping to newcomers on Reddit[4](https://www.reddit.com/user/HardenedSteelX/), Monero StackExchange[5](https://monero.stackexchange.com/users/12826/hardenedsteel), Monero.Town[6](https://monero.town/u/HardenedSteel) and helping them to onboard Monero ecosystem[7](https://github.com/HardenedSteel/Help4XMR)
+* Translation of Monero.com (and Cake) Wallet[8](https://github.com/cake-tech/cake_wallet/pull/724).
+* and more...
+
+# What?
+I will continue maintaining getmonero.org but with greater level. This will entail reviewing pull requests, fixing issues, adding new content and following social media (such as Reddit and Monero.town) to identify new issues and feature requests for those who do not use GitHub etc.
+
+Furthermore, I will (attempt to) continue contributing to other Monero ecosystems in my spare time.
+
+# Why?
+Many people in Monero community (such as both core and non-core devs and people on social media) complains the website isn't maintained well and there are only a few people working on the site.
+
+# Milestones
+This proposal is only one month since it's my first proposal and requesting 5 XMR for it. Depending on the feedback from the community I'm planning work more than month.
+

hardenedsteel-getmonero-2.md

+---
+layout: cp
+title: Part-time Work on getmonero.org (2 Month)
+author: HardenedSteel
+date: 14 September, 2024
+amount: 10
+milestones:
+  - name: Month 1
+    funds: 5 XMR
+    done: 3 December 2024
+    status: finished
+  - name: Month 2
+    funds: 5 XMR
+    done: 3 December 2024
+    status: finished
+payouts:
+  - date: 13 December 2024
+    amount: 10
+---
+
+# Who?
+Hi again, Its my second proposal I won't copy paste same content to here instead you can reach to my first proposal*.
+
+*https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/481
+
+# What?
+I will continue to maintain getmonero.org and possibly to the docs site (such as migration if it happens) at same pace.
+
+# Milestones
+5 XMR / month. In total 2 months
+
+---
+
+Let me know your concerns or experiences with me or the previous CCS.

haveno-frontend.md

 ---
-layout: wip
+layout: cp
 title: Haveno frontend development
 author: Haveno
 date: Mar 16, 2022
@@ -32,6 +32,20 @@ payouts:
     amount: 151
 ---
 
+
+## Proposal closure / Repurposing of funds (3rd Sep, 2024)
+
+- The proposed structure for Haveno is no longer feasible.
+- No progress has been made in 2 years.
+- A developer (kewbit) has stepped forward to work on the project.
+- Due to these reasons, this proposal is deemed void and the remaining 453XMR will be repurposed.
+
+215XMR will be used to fund a [Haveno Multi-Platform Native App For Every OS](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/489) that will meet all the [functional requirements](https://github.com/haveno-dex/haveno-design/blob/master/functional_requirements.md) of a Haveno UI.
+
+The remaining funds will be used for further Haveno front end related work in keeping with the original goals of this proposal (at the communities discretion)
+
+---
+
 Hello again everyone. As promised, after improving Haveno's structure, we come back with a new (much cheaper) CCS proposal.
 
 For a complete picture and all details, [see our initial proposal](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/284), which assumed the old structure with centralized operators.

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

+---
+layout: cp
+title: Haveno Multi-Platform Native App for Android, iOS, Windows and Linux.
+author: Kewbit
+date: August 19, 2024
+amount: 215
+milestones:
+  - name: Create the User Interface
+    funds: 75
+    done:
+    status: unfinished
+  - name: Write the Protocol Interface
+    funds: 75
+    done: 13 October 2024
+    status: finished
+  - name: Create the Desktop Connector
+    funds: 15
+    done:
+    status: unfinished
+  - name: Create Multi-Platform Installers for Windows, Linux, Mac, Android and iOS.
+    funds: 50
+    done:
+    status: unfinished
+payouts:
+  - date: 23 October 2024
+    amount: 75
+  - date:
+    amount: 75
+  - date:
+    amount: 15
+  - date:
+    amount: 50
+---
+### 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.
+
+![Haveno App Montage](https://i.ibb.co/8xvJrPd/Screenshot-20240817-204709-imageonline-co-merged.png "App Montage")
+## Security Considerations
+
+- **Open Source**: All software created will be open-source, and only auditable, open-source libraries will be used. The project will be released under the AGPL 3.0 license upon completion.
+- **Tor Integration**: The app will enforce Tor usage, requiring users to connect via a Tor VPN relay (such as Orbot or InviZible). Without a Tor connection, the app will not proceed past the splash screen.
+- **gRPC Protocol**: The app will connect to Haveno Daemon using the native gRPC HTTP/2 over Tor (not translated from HTTP/1.2 or HTTP/1)
+- **Haveno Integration**: The app seamlessly connect to any Haveno Daemon hosted anywhere (using .onion via Tor)
+- **Censorship Resistance**: By abstracting the VPN relay away from the app itself and requiring Orbot or InviZible, we avoid potential censorship issues. The app will not require VPN-enabled entitlements that need signing, thus preserving its censorship-resistant nature. The app will be available on [F-Droid](https://f-droid.org/en/).
+- **Secure Device Linking**: The app will support secure linking to a running desktop or server instance via a QR code containing a hashed password in the URI of the Onion Link. [Onion Client Authentication](https://support.torproject.org/onionservices/client-auth/) will be available fro advanced users.
+- **Native Libraries**: The app with use native library per OS directly from trusted sources.
+- **Service Segregation**: Each component of the software will run under it's own service on Dekstop versions, you'll be able to manage the services via a System Tray on Windows, Linux and Mac operating systems.
+
+## Features
+
+- Ability to connect to any Haveno network that you want
+- Customize based on your locale
+- Ability to see Haveno network trade offers
+- Start trades, open your own trades
+- Chat with the peer trader
+- Open disputes if a transaction isn't working out and chat with an arbitrator
+- Manage your payment accounts for both crypto & fiat
+- Get notifications when your have new trades or chat messages (local notifications that don't depend on Google's push notification system)
+- Deposit and withdraw from your wallet
+- Beautiful candlestick trading view for Haveno network activity
+- System Tray to manage your Tor & Haveno Daemon services, keep your daemon online without the client open for mobile users.
+- Docker image will be available for advanced users contingent on colaberative efforts between the Haveno DEX team.
+
+## Installers Available As:
+
+- **Linux**: **.AppImage**
+- **Windows**: A windows **.exe** file.
+- **MacOS**: A **.pkg** file or an **.xarchive** file
+- **Android**: A **.apk** or **.aab** file
+- **iOS**: A **.ipa** file or an **.xarchive** file
+
+## Possible Future Plans
+
+- Matrix integration for server-side notifications to the mobile device (this might be nessesary for iOS users to get notifications reliably and timely.)
+- Design the P2P protocol from Haveno in Dart, so that you may not depend on the Haveno Daemon for the app to work (Standalone Mobile App)
+- A redesign of the desktop version of the app to fit the Figma design plan in [haveno-design](https://github.com/haveno-dex/haveno-design/blob/master/haveno_mockups.pdf)
+
+## Purpose
+
+### What the Proposal is About
+
+This proposal aims to bring the Haveno / Monero ecosystem together through Haveno with a user-friendly, multi-platform app that considers security, censorship resistance, and hardware wallet support. I would like to continue adding value to this project so am seeking funds to priorize it beyond the 2 months I scoped out myself.
+
+### Who Will Complete the Proposal
+
+Kewbit (kewbitxmr@protonmail.com)
+
+### Why It Is Important for Monero and the Community
+
+This app is crucial for the Monero community because it promotes a censorship-resistant and decentralised ecosystem. There is great difficulty in finding places to trade XMR due to certain website closures and crackdowns. By intending to make the app available on multiple OS and platforms, including on F-Droid, Play Store, and App Store, we ensure that it reaches a wide audience, including those who prefer non-traditional Android phones using Play Store.
+
+## Milestones and Projected Timeline
+
+- **Create the User Interface**
+  - **Funds**: 75 XMR
+  - **Status**: Started
+
+- **Write the Protocol Interface**
+  - **Funds**: 75 XMR
+  - **Status**: Started
+
+- **Create the Desktop Connector**
+  - **Funds**: 15 XMR
+  - **Status**: Started
+
+- **Create Multi-Platform Installers for Windows, Linux, Mac, Android, and iOS**
+  - **Funds**: 50 XMR
+  - **Status**: Started
+
+## Payouts
+
+- **10/11/2024**: 75 XMR
+- **10/11/2024**: 75 XMR
+- **10/11/2024**: 15 XMR
+- **01/12/2024**: 50 XMR
+
+## Expiration Date
+
+I do not intend for there to be an expiration date. I plan to release the app quickly as I am working on it full-time, even before producing a CCS. I see this as an ongoing project but expect to have a beta absolute latest by 31st December 2024. 
+
+## Alpha Builds
+You can check out the current source and alpha builds.
+
+https://github.com/KewbitXMR/haveno-plus/ (Name of project is subject to change, as is the organisation)
+
+I provider further updates regularly on my blog which you can subscribe to if interested at [Kewbit.org](https://kewbit.org) you can also find [my current public key](https://kewbit.org/public-key/), which I would encourage you to import into your PGP client.
+

hinto-2.md

+---
+layout: cp
+title: hinto-janai full-time work on Cuprate (3 months)
+author: hinto-janai
+date: May 5, 2024
+amount: 264
+milestones:
+  - name: RPC server design
+    funds: 20% (52.8)
+    done: 5 June 2024
+    status: finished
+  - name: JSON RPC interface
+    funds: 40% (105.6)
+    done: 9 August 2024
+    status: finished
+  - name: Binary/other RPC interface + other work
+    funds: 40% (105.6)
+    done: 9 August 2024
+    status: finished
+payouts:
+  - date: 18 June 2024
+    amount: 52.8
+  - date: 12 August 2024
+    amount: 211.2
+---
+
+## What
+[Cuprate](https://github.com/Cuprate/cuprate) is an alternative Monero node implementation, currently worked on by me and [Boog900](https://github.com/boog900).
+
+The next large section that needs work is the RPC server. Another contributor, [yamabiiko](https://github.com/yamabiiko), is also interested in working on the RPC server, although they currently have limited time, so I'll be starting on it alone for now (with much help from Boog900).
+
+## Who
+I'm [hinto-janai](https://github.com/hinto-janai).
+
+Past CCS: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/422.
+
+## RPC server
+yamabiiko has started a discussion on the design for the RPC server [here](https://github.com/Cuprate/cuprate/issues/106), and Boog900 has suggested some changes.
+
+The first milestone's time will be spent on:
+- Fleshing out the current proposal or potentially finding better alternatives
+- Preparing an initial design document, similar to [`database/`](https://github.com/Cuprate/cuprate/pull/35)
+
+The current design for the database was spread out across several months, although, the design for the RPC server should take much less time.
+
+After a design is set, the second/third milestone will start on the RPC interface library - the timeline for this is by the end of this CCS. This includes testing, documentation, etc. The current plan is to separate the interface from the inner RPC handler. After the interface is finished, the internal handler(s) will be finished in another CCS (potentially split between contributors).
+
+By the end of this CCS, the initial design document will be polished to reflect the implementation, similar to [here](https://github.com/Cuprate/cuprate/blob/main/database/README.md), and user documentation will also be finished (again, like `database/`).
+
+The resulting design document will be added to [Cuprate's architecture book](#cuprates-architecture-book) (see below).
+
+## Other work
+There's also other work that I believe would be beneficial to start on earlier rather than later.
+
+These will be started on during this CCS:
+
+- Cuprate's architecture book
+- Persistent transaction pool
+- `monero-core` RPC PRs
+- Benchmarking suite
+- Project lints
+
+The persistent transaction pool will be finished within this CCS, the rest will grow alongside the project.
+
+### Cuprate's architecture book
+This is a book similar to [Cuprate's protocol book](https://monero-book.cuprate.org), although it will be for Cuprate's implementation. The RPC design will be documented in this book (along with every other component) as they are implemented. The current [database document](https://github.com/Cuprate/cuprate/blob/main/database/README.md) will be ported to the book as well.
+
+Current rough draft: https://hinto-janai.github.io/cuprate-architecture
+
+Expected included items are:
+- Relational map of components (RPC, DB, block downloader, verifier, etc)
+- Component designs
+- Thread model (when/where/how many threads get spawned? for what purpose?)
+- Resource model (files, sockets, memory usage)
+- Instrumentation (logging, data collection methods)
+- Known inefficiencies/tradeoffs, their reasoning
+
+### Persistent transaction pool
+Considering RPC implementation will take a while, implementing a persistent transaction pool sooner rather than later would be preferred; another option Cuprate has is to create an in-memory only transaction pool, although this would only be a stop-gap and would take more work in the long run, thus this work will be done now.
+
+### `monero-core` RPC PRs
+As I'll be going through all of `monerod`'s RPC methods/objects and [`getmonero.org`](https://www.getmonero.org/resources/developer-guides/daemon-rpc.html) documentation, I will open PRs to `monero-core` or create an issue if I notice any discrepancies.
+
+### Benchmarking suite
+Creating a benchmarking suite for Cuprate's components would allow for collecting and storing information on code execution time. This data can be used later on to detect performance regressions as well as measuring optimizations.
+
+Creating a bespoke benchmarking tool would be a project of its own, so Cuprate is planning to use the [Criterion](https://bheisler.github.io/criterion.rs/book/criterion_rs.html) project.
+
+### Project lints
+Lints cause compiler warnings to become hard errors, blocking compilation. An example: [`serai-dex`](https://github.com/serai-dex/serai/blob/21123590bb600323aa424f64ffaa5d321b1b22ed/Cargo.toml#L135-L184).
+
+Cuprate's CI already fails on warnings (among other pedantic things), although there are many additional lints we could add. Selecting the lints that make sense for Cuprate sets higher code standards for the project. Setting this up and fixing current code should not take too much effort, but it will be drawn out over time.
+
+## Funding
+I am asking for a rate closer to market rates, please read [here](https://gist.github.com/hinto-janai/8ce1d4847f51304aa4d71c3614408d7f).
+
+I am asking for $65 + 0.05 XMR per hour for 480 hours at $130/XMR. This gives 264 XMR.
+
+Recent activity has shown that `monerod` does not handle load well. Furthermore, there is little system-level documentation; changes needed to fix issues like this are more difficult than necessary. I do not believe this has to be repeated.
+
+I believe this is a fair rate for creating well documented and maintainable infrastructure. I am also asking for less hours than before as I don't believe I can continue at my current pace long-term.
\ No newline at end of file

hinto-2023-nov.md

+---
+layout: cp
+title: hinto-janai full-time work on Cuprate (3 months)
+author: hinto-janai
+date: Nov 6, 2023
+amount: 153
+milestones:
+  - name: Internals
+    funds: 33% (51)
+    done: 13 March 2024
+    status: finished
+  - name: API
+    funds: 33% (51)
+    done: 5 May 2024
+    status: finished
+  - name: Integration + 3 months of work
+    funds: 33% (51)
+    done: 5 May 2024
+    status: finished
+payouts:
+  - date: 9 April 2024
+    amount: 51
+  - date: 14 May 2024
+    amount: 102
+---
+
+## What
+[Cuprate](https://github.com/Cuprate/cuprate) is an alternative Monero node implementation, currently solely worked on by [Boog900](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/405).
+
+I've been in contact with Boog and there are many sections within Cuprate that can be worked on in parallel, currently the most pressing section is the database. This work was left unfinished by SyntheticBird45 before they left the project. Boog is currently working on block downloading/verification/consensus with cobbled together database-like functions - this means an actual database layer can be worked on in parallel without any merge conflicts, and can be cleanly slotted in once complete.
+
+This CCS is to support me working on full-time on Cuprate for the next 3 months, specifically on the database implementation.
+
+## Benefitting Monero
+This CCS will fund part of a larger effort to create an alternative Monero node implementation (among other things).
+
+As such, things will initially be slow-going as groundwork is laid. This CCS specifically may not _directly_ benefit `monero-core` immediately, yet it's work that must be completed such that Cuprate _can_ benefit `monero-core` (and Monero) in the future.
+
+## Who
+I'm [hinto-janai](https://github.com/hinto-janai).
+
+Past CCS: https://ccs.getmonero.org/proposals/gupax.html.
+
+## Design
+The design document and active PR is here: https://github.com/Cuprate/cuprate/pull/35 and will be updated as things change.
+
+The main goal is to create a layer that separates the underlying database and the higher-level functions that are called by the other portions of Cuprate, e.g, `get_block()`. The aim here is to allow for easy hot-swapping of databases to test for the various operations Cuprate will be performing. In the end, a single database will be selected after testing, although the layer will continue to exist. 
+
+The database implementations in mind (for now) include:
+- LMDB (via [heed](https://github.com/meilisearch/heed))
+- [sanakirja](https://docs.rs/sanakirja) (a database [similar and originally based off](https://pijul.org/posts/2021-02-06-rethinking-sanakirja) LMDB)
+
+Both of these will be forked and maintained by Cuprate as there are `monerod`-specific things that must be added (e.g output lookup using [sub-keys](https://github.com/monero-project/monero/blob/ac02af92867590ca80b2779a7bbeafa99ff94dcb/src/blockchain_db/lmdb/db_lmdb.cpp#L3447C1-L3449C80)).
+
+The overall design is mostly from Boog900 - I am simply implementing it.
+
+## Future
+There's plenty more work to be done after the database. Boog plans on handling P2P code after his current CCS, which means I could possibly work on these things in the future (in parallel with Boog's work):
+
+- RPC server (e.g. `get_info`)
+- Transaction-pool related (e.g. Dandelion++)
+- Application interface linking everything together (e.g. `./cuprated --option`)
+
+Most likely, the RPC server would be the next thing I would be working on.
+
+And there are things that are planned, but for the very distant future:
+- ZMQ support
+- Tor/i2p support: [Tor is quite feasible today](https://blog.torproject.org/announcing-arti), i2p less so
+- RandomX: Currently, there exists multiple (quite rough) `C/C++ <-> Rust` bindings but as RandomX is in active use (and will most likely be for the foreseeable future) another implementation or more realistically, a maintained "Rust"-like shim on-top would be nice
+- CryptoNight: Same as RandomX but less important as this is only used for legacy purposes
+- P2P encryption (preferably compatible with the proposal for [`monerod`](https://github.com/monero-project/monero/issues/7078))
+
+These points are laid out to showcase what else must/could be done for Cuprate to reach some level of parity with `monerod`.
+
+## Why
+Cuprate has an advantage in that it has an [8+ year old codebase](https://github.com/monero-project/monero) as reference - although we are starting with a blank canvas, we have a finished painting next to us, displaying all the very good, okay, and not-so-good parts.
+
+As such, we can focus on things other than making it work, notably: documentation, maintenance, and correctness.
+
+Other than documenting the [Monero protocol itself](https://monero-book.cuprate.org), we plan to write documentation for internal subsystems such that future Cuprate contributors/maintainers will be able to pick up easily where we left off. What this means for me and this CCS is that I'll be documenting how this database "layer" fits in with the rest of Cuprate, and answer all the "what does this do?", "how does this work?", "why was it done like this?" questions. If I were to continue working on Cuprate past this CCS, i.e. the RPC server, all RPC types would also be documented (and the internals as well) - the same goes for any future subsystems.
+
+Other notable projects following this pattern: [Tor](https://youtu.be/hdFL0kXu440?t=700), [Bitcoin](https://github.com/rust-bitcoin/rust-bitcoin), [Ethereum](https://github.com/rust-ethereum), [Zcash](https://github.com/ZcashFoundation/zebra).
+
+
+## Proposal
+I propose to work for 44 hours/week for 3 months.
+
+By the end of this proposal, Cuprate will have a working database. I believe 3 months is enough time to create and refine an implementation enough for usage.
+
+It is hard to separate large single implementations like this cleanly into goals/timeframes as usually many things get worked on at any given moment - although, there are 3 bigger milestones this CCS has:
+
+1. Internals: implementing the database and functions themselves
+2. API: cleanup of the interface and many other miscellaneous things for external usage
+3. Integration: slotting the database into Cuprate, and at least 3 months of work
+
+Milestone 3 is only to be paid out upon:
+- A complete database has been integrated into Cuprate
+- 3 months of work has been done
+
+This means if the database takes 428~ hours to complete, I will continue to work for 100~ more hours (most likely on the things listed in `Future`) to complete milestone 3.
+
+- Hours: 528
+- Rate: $45 USD/hour
+- XMR: $155 (20-day EMA, Kraken, 2024/01/15)
+- Total: 153 XMR

hinto-3.md

+---
+layout: cp
+title: hinto-janai full-time work on Cuprate (3 months)
+author: hinto-janai
+date: August 9, 2024
+amount: 221
+milestones:
+  - name: JSON RPC handlers
+    funds: 40% (88.4)
+    done: 25 December 2024
+    status: finished
+  - name: Binary/other RPC handlers
+    funds: 40% (88.4)
+    done: 25 December 2024
+    status: finished
+  - name: Other work
+    funds: 20% (44.2)
+    done: 4 November 2024
+    status: finished
+payouts:
+  - date: 12 November 2024
+    amount: 44.2
+  - date: 21 January 2024
+    amount: 176.8
+---
+
+## What
+[Cuprate](https://github.com/Cuprate/cuprate) is an alternative Monero node implementation.
+
+The next section that needs work is the RPC handlers. The design, interface, routing, types, and (de)serialization were completed in my previous CCS, see here:
+- Past CCS: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/456
+- RPC interface tracking issue: https://github.com/Cuprate/cuprate/issues/183
+- RPC book: https://architecture.cuprate.org/rpc/intro.html
+
+This CCS is for the handlers, i.e. the functions that turn requests into responses.
+
+Once the handlers are complete, Cuprate will have a working RPC stack that [mostly](https://architecture.cuprate.org/rpc/differences/intro.html) mirrors `monerod`.
+
+## Who
+I'm [hinto-janai](https://github.com/hinto-janai).
+
+## RPC handlers
+The 1st/2nd milestones are for the RPC handlers. This is the majority of the work.
+
+This includes:
+- JSON RPC handlers (methods behind `/json_rpc`)
+- Binary RPC handlers (binary endpoints, e.g. `/get_blocks.bin`)
+- Other handlers (other JSON endpoints, e.g. `/get_height`)
+
+The RPC handlers will most likely be in its own library/section, built on-top of the RPC libraries Cuprate has so far. The current RPC interface library ([`cuprate-rpc-interface`](https://github.com/Cuprate/cuprate/tree/main/rpc/interface)) allows for custom handlers, as in, the mapping of `request` -> `response` can be customized. The handler created in this CCS will be a standard implementation that (mostly) follows `monerod`'s behavior, i.e. request comes in, get some data from the database and such, return a response. Although, other implementations are possible, such as an RPC handler that caches blocks, as mentioned in [this meeting](https://github.com/monero-project/meta/issues/996#issuecomment-2086710102).
+
+Testing, [crate (library) documentation](https://doc.cuprate.org), and [architecture book](https://architecture.cuprate.org) sections will also be written.
+
+### Binary strings
+There are a few RPC methods that require further discussion before implementation in Cuprate, see the [binary strings proposal](https://github.com/monero-project/monero/issues/9422).
+
+If the above proposal finds consensus on future `monerod` behavior, this CCS will implement that behavior.
+
+If more time is required for the proposal, the related endpoints/methods will be left in a semi-unfinished state until behavior is agreed upon, where after Cuprate will implement that behavior.
+
+If the proposal does not move forward, Cuprate is planning to fallback to implementing `monerod`'s current behavior.
+
+## Other work
+The 3rd milestone is for any miscellaneous work that needs to be done for Cuprate, but also, these 2 concrete things:
+- Lints
+- Benchmarking
+
+I'd like to focus on these as:
+- If they're always pushed to the side, they'll never get done
+- I believe it's important to establish these early on in the project
+
+I started integrating lints & benchmarks into Cuprate last CCS, this CCS will finish integrating them for all the libraries I've written so far, and [other libraries](https://architecture.cuprate.org/appendix/crates.html) if time allows.
+
+The issues tracking the progress of these two can be found here:
+- https://github.com/Cuprate/cuprate/issues/207 (lints)
+- https://github.com/Cuprate/cuprate/issues/208 (benchmarks)
+
+## Funding
+I am asking for $65 + 0.05 XMR per hour for 480 hours at $158/XMR. This gives 221 XMR.

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

 ---
-layout: wip
+layout: cp
 title: j-berman full-time development (3 months)
 author: j-berman
 date: July 26, 2023
@@ -7,23 +7,21 @@ amount: 216 Monero
 milestones:
   - name: Month 1
     funds: 33% (72 Monero)
-    done:
-    status: unfinished
+    done: 21 September 2023
+    status: finished
   - name: Month 2
     funds: 33% (72 Monero)
-    done:
-    status: unfinished
+    done: 19 October 2023
+    status: finished
   - name: Month 3
     funds: 33% (72 Monero)
-    done:
-    status: unfinished
+    done: 18 November 2023
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 8 November 2023
+    amount: 72
+  - date: 2 December 2023
+    amount: 144
 ---
 
 ## What

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

+---
+layout: cp
+title: j-berman full-time development (3 months)
+author: j-berman
+date: December 18, 2023
+amount:  211 Monero
+milestones:
+  - name: Month 1
+    funds: 33% (70.3 Monero)
+    done: 23 February 2024
+    status: finished
+  - name: Month 2
+    funds: 33% (70.3 Monero)
+    done: 4 April 2024
+    status: finished
+  - name: Month 3
+    funds: 33% (70.4 Monero)
+    done: 1 May 2024
+    status: finished
+payouts:
+  - date: 4 March 2024
+    amount: 70.3
+  - date: 9 April 2024
+    amount: 70.3
+  - date: 14 May 2024
+    amount: 70.4
+---
+
+## What
+
+Work full-time 3 months on:
+
+- Continuing Seraphis wallet library work.
+  - Complete the async wallet scanner implementation using the Seraphis wallet lib.
+    - When I pointed this async scanner on my local machine to a remote `monerod` instance @selsta spun up, I observed a **~40% speed-up in scanning** over the current wallet2 scanner.
+    - Link to the draft PR that details all remaining TODO's in the PR description: https://github.com/UkoeHB/monero/pull/23
+    - This CCS proposal will not be complete until I complete all major TODO's from the PR linked above, and deliver a final version of the async scanner PR for review.
+  - Once I complete the async scanner, I plan to collaborate further with @jeffro256 @rbrunner7 @dangerousfreedom and the no-wallet-left-behind working group to work on whatever is next highest priority to get the Seraphis wallet lib ready for production.
+- Continue work integrating [full chain membership proofs](https://github.com/kayabaNerve/full-chain-membership-proofs/) into the Seraphis library (and therefore demonstrate how to integrate them into the core Monero repo). The goal is to construct and verify Seraphis transactions using full chain membership proofs, including a suite of unit tests and benchmarks.
+  - In my last CCS, I got an initial setup working to call full chain membership proof code written in Rust from a Monero repo C++ performance test. This was step 1-of-many toward the goal of constructing a full chain membership proof in a transaction using the Seraphis wallet lib.
+- Miscellaneous Monero work, debug issues, review PR's.
+  - Highest on my list right now is to review @vtnerd's p2p encryption implementation (source: https://github.com/monero-project/monero/pull/8996).
+
+## Who
+
+j-berman on github / jberman on matrix
+
+Past CCS's:
+- 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
+
+211 XMR
+
+480 hours, 0.16 XMR/hr + $48/hr, $172/XMR from coingecko

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

+---
+layout: cp
+title: j-berman full-time development (3 months)
+author: j-berman
+date: May 2, 2024
+amount:  376 Monero
+milestones:
+  - name: Month 1
+    funds: 33% (125.3 Monero)
+    done: 25 May 2024
+    status: finished
+  - name: Month 2
+    funds: 33% (125.3 Monero)
+    done: 10 July 2024
+    status: finished
+  - name: Month 3
+    funds: 33% (125.4 Monero)
+    done: 16 August 2024
+    status: finished
+payouts:
+  - date: 17 June 2024
+    amount: 125.3
+  - date: 17 July 2024
+    amount: 125.3
+  - date: 30 August 2024
+    amount: 125.4
+---
+
+## What
+
+Work full-time 3 months on:
+
+- Integrating [full-chain-membership proofs](https://ccs.getmonero.org/proposals/fcmp++-development.html) into Monero under RingCT.
+  - As part of this CCS, I will submit PR's to the core Monero repository that do the following:
+    - Implements the tree in C++ described in section 6.1 ([paper](https://github.com/kayabaNerve/fcmp-ringct/blob/develop/fcmp%2B%2B.pdf), [reference commit](https://github.com/kayabaNerve/fcmp-ringct/blob/221e8c0e155d5fe526080c6e56c6418e0433177d/fcmp%2B%2B.pdf))
+      - Implements the `grow` and `trim` algorithms (sections 6.1.1 and 6.1.2)
+    - Implements tree initialization with existing cryptonote outputs on boot (section 6.2.1)
+    - Implements growing the tree as the node syncs (section 6.2.2 and 6.2.3)
+    - Implements the transaction class containing FCMP's (part of sections 6.3 - 6.6)
+      - I will probably extend `cryptonote::transaction` to do this.
+  - The following tasks from the rest of section 6 are necessary to complete the integration; I'm happy to divide and conquer if someone wants to work on this as well:
+    - Implement transaction construction with FCMP's (sections 6.3 - 6.6)
+      - A pre-requisite for this is implementing the transaction class above.
+    - Implement transaction verification (section 6.7)
+    - Implement RPC route to return a path for outputs (section 6.9)
+    - Implement unifying the distribution of {coinbase, pre-RCT, RCT} outputs and use it to select decoys paths (section 6.10)
+    - Implement changes for multisig (section 6.11)
+- Continuing Seraphis wallet library work.
+  - My next task on this front is to bring the Serpahis lib async scanner into the current wallet API.
+    - To be clear, this is not implementing the Seraphis upgrade; it is bringing the Seraphis wallet **library**, which supports scanning today's blockchain, into the core Monero repository. This would speed up wallet scanning **today**, and is part of an effort to deprecate wallet2 and its technical debt, and replace it with the Seraphis lib ([source](https://github.com/seraphis-migration/wallet3/issues/64#issuecomment-2067030930)).
+    - The async scanner is currently under review ([source](https://github.com/UkoeHB/monero/pull/23))
+    - In the latest round of benchmarks, I observed scanning speed-ups of 50-60% with a clearnet remote node, 40-45% with a tor node, 25-35% with a local node, all running the **current chain** (not Seraphis).
+    - To be usable in the wallet API today, the following still needs to be implemented (I'm also happy to divide and conquer here):
+      - Pre-RCT index handling (needs [source](https://github.com/UkoeHB/monero/pull/23))
+      - 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))
+- Complete p2p SSL review ([source](https://github.com/monero-project/monero/pull/8996)).
+- Misc. review, debugging, etc.
+
+## Who
+
+j-berman on github / jberman on matrix / IRC
+
+Past CCS's:
+- 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
+
+376 XMR
+
+480 hours, 0.25 XMR/hr + $65/hr, $122/XMR from coingecko
+
+I'm requesting a siginificant raise from my past CCS (0.16 XMR/hr -> 0.25 XMR/hr, $48/hr -> $65/hr) because I believe I have demonstrated improved performance, and believe the recent donations to CCS proposals demonstrate the community is capable of paying strong Monero contributors market / above-market rates. I believe paying market / above-market rates for strong contributors is a stronger strategy for Monero to attract and retain strong talent.

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

+---
+layout: cp
+title: j-berman full-time development (3 months)
+author: j-berman
+date: August 26, 2024
+amount:  317 Monero
+milestones:
+  - name: Month 1
+    funds: 33% (105 Monero)
+    done: 14 October 2024
+    status: finished
+  - name: Month 2
+    funds: 33% (106 Monero)
+    done: 11 November 2024
+    status: finished
+  - name: Month 3
+    funds: 33% (106 Monero)
+    done: 12 December 2024
+    status: finished
+payouts:
+  - date: 20 October 2024
+    amount: 105
+  - date: 19 November 2024
+    amount: 106
+  - date: 12 January 2025
+    amount: 106
+---
+
+## What
+
+Work full-time 3 months on:
+
+- Integrating full-chain membership proofs++ into Monero under RingCT.
+  - As part of this CCS, I will prioritize and guarantee completion of the following in this PR: https://github.com/monero-project/monero/pull/9436
+    1. Trim the tree on reorgs and when popping blocks.
+    2. Key image migration.
+    3. Optimize tree building where possible.
+        - Multithreaded output conversion to leaves.
+        - Multithreaded hashing.
+        - Batched inversion.
+    4. Construct fcmp++ transactions.
+        - I anticipate updating `cryptonote::construct_tx_and_get_tx_key` for this, and not touching wallet2 in this proposal.
+        - By the end of this proposal, there will be a modular function wallets can use to construct fcmp++ txs, but I may not have an end-to-end functioning wallet that can construct fcmp++ txs implemented by the end of this proposal.
+    5. Verify fcmp++ transactions.
+    6. Consensus changes 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.
+  - Work together with @dangerousfreedom on full wallet scanning.
+  - The remaining integration tasks that I would also work on if time permits and someone else doesn't:
+    - Construct fcmp++ transactions in a fully functional wallet.
+      - Pre-requisites: modular function to construct fcmp++ transactions and full wallet scanning.
+    - Implement the RPC route for light wallets to query for paths in the curve trees tree.
+    - Wallet changes for background syncing.
+    - Multisig.
+- Continuing Seraphis wallet library work.
+  - Making it clear up front: I anticipate not making much progress on the Seraphis wallet library work in this CCS. I plan to prioritize fcmp++. If time permits, I would work on bringing the Seraphis wallet library to production.
+  - To be clear, working on the Seraphis wallet library is not implementing the Seraphis upgrade; it is bringing the Seraphis wallet library, which supports scanning today's blockchain, into the core Monero repository. This would speed up wallet scanning today, and is part of an effort to deprecate wallet2 and its technical debt, and replace it with the Seraphis lib ([source](https://github.com/seraphis-migration/wallet3/issues/64#issuecomment-2067030930)).
+  - Next I plan to resolve merge conflicts in the current open PR's, and open all piecemeal PR's to the core Monero release branch to prepare Monero daemons/wallets and reduce the size and scope of the async scanner PR.
+- Misc. review, debugging, etc.
+
+## Who
+
+j-berman on github / jberman on matrix / IRC
+
+Past CCS's:
+- 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
+
+317 XMR
+
+480 hours, 0.25 XMR/hr + $65/hr, $158/XMR from coingecko

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:
+    status: unfinished
+  - name: Month 4
+    funds: 25% (90 Monero)
+    done:
+    status: unfinished
+payouts:
+  - date: 4 February 2025
+    amount: 90
+  - date: 19 March 2025
+    amount: 90
+  - date:
+    amount:
+  - 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

jeffro256-full-time-2023Q3.md

 ---
-layout: wip
+layout: cp
 title: jeffro256 full-time development 2023Q3
 author: jeffro256
 date: May 30, 2023
@@ -7,23 +7,23 @@ amount: 147
 milestones:
   - name: Month 1
     funds: 33% (49.0)
-    done:
-    status: unfinished
+    done: 3 August 2023
+    status: finished
   - name: Month 2
     funds: 33% (49.0)
-    done:
-    status: unfinished
+    done: 7 September 2023
+    status: finished
   - name: Month 3
     funds: 33% (49.0)
-    done:
-    status: unfinished
+    done: 17 October 2023
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 16 August 2023
+    amount: 49
+  - date: 12 September 2023
+    amount: 49
+  - date: 3 November 2023
+    amount: 49
 ---
 
 ## What