boog_3_months_cuprate.md

+---
+layout: cp
+title:  Boog900 full time work on Cuprate (3 months)
+author: Boog900
+date: January 27, 2024
+amount: 190
+milestones:
+  - name: The PeerSet + Routing methods excluding D++
+    funds: 54 XMR
+    done: 15 June 2024
+    status: finished
+  - name: D++ Routing method + Network Initialisation
+    funds: 54 XMR
+    done: 15 June 2024
+    status: finished
+  - name: The Block Downloader + Syncer
+    funds: 54 XMR
+    done: 15 June 2024
+    status: finished
+  - name: P2P Documentation
+    funds: 28 XMR
+    done: 18 July 2024
+    status: finished
+payouts:
+  - date: 20 June 2024
+    amount: 162
+  - 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
+Cuprate's P2P layer and syncing. While doing this I will also expand [monero-book](https://monero-book.cuprate.org), which I created during my last CCS, 
+with the P2P types, message encoding and message flows (handshakes etc).
+
+# 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/405).
+
+# What
+
+As well as continuing to lead coordination of Cuprate, I will also be an active maintainer for monero-rs, during the past few months
+I have been reviewing and merging PRs and have released a new version: [ v0.20.0 ](https://github.com/monero-rs/monero-rs/releases/tag/v0.20.0)
+
+For this CCS I will be working on getting Cuprate's P2P layer into a working state.
+
+Currently Cuprate's P2P has:
+
+- Levin header decoding/ encoding
+- Every P2P message decoding/ encoding
+- Handshakes.
+- Rough individual peer message routing.
+- A P2P address book.
+
+What I will be doing:
+
+## Hardening Individual Peer Message Routing
+
+Individual peer message routing needs to be hardened, currently we don't do any checks the data received is the data we
+asked for, we should be doing these checks in the connection task before handing the message to the rest of Cuprate.
+
+## The PeerSet
+
+The `PeerSet` is the structure that holds all currently connect peers on a certain network, it will have methods to get
+peers by direction (Inbound, Outbound) or by a custom strategy, e.g a load balancing algorithm. This structure is then
+used by the different routing methods.
+
+## All The Routing Methods
+
+The routing methods are how the rest of Cuprates interact with the P2P network. The goal is to have there be one end point
+that the rest of Cuprate can send requests to. This end point will need to be made up of multiple `tower::Services` for the different
+routing methods (broadcast to all, etc).
+
+I will also be creating the Dandelion++ routing method, which will handle keeping the current d++ state, selecting out peers to route to and
+keeping track of stem routes. It won't handle all of D++ as that requires knowledge of the tx-pool, but it will handle all the routing
+side.
+
+## Network Initialisation
+
+I will make the network initialisation code, to start the network and return the end point that requests can be sent to.
+
+## The Block Downloader
+
+The block downloader will be a `futures::Stream` that will handle finding the chain with the most PoW from the `PeerSet` and will download
+this chain from the peer(s), giving the downloaded blocks back to the caller to then verify and add to our chain.
+
+## The Syncer 
+
+The syncer will handle synchronisation after falling behind, it will use [the block downloader](#the-block-downloader) and
+the consensus service I created for my last CCS. It will get the blocks from the downloader, verify them and then
+giving them to the database*.
+
+*the database will not be worked on for this CCS, see [hinto's CCS](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/422).
+
+If this CCS and [hinto's CCS](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/422) are accepted then when both are complete Cuprate will
+be able to sync, verify and store the blockchain.
+
+## Documentation
+
+There are already documents describing the [levin header format](https://github.com/monero-project/monero/blob/master/docs/LEVIN_PROTOCOL.md) and [epee binary format](https://github.com/monero-project/monero/blob/master/docs/PORTABLE_STORAGE.md).
+I will be documenting the format of each P2P message (how they are encoded, the fields) and successful message flows: handshakes, syncing etc. 
+
+# Why
+
+I believe that having an alternative node is needed to help to protect against implementation issues like [this one](https://github.com/monero-project/monero/pull/9013) I found during my
+last CCS.
+
+Having an accessible P2P library and documentation will make it easier for devs to build software that needs to interact with the P2P network.
+
+# Milestones
+
+1. The PeerSet + Routing methods excluding D++
+2. D++ Routing method + Network Initialisation
+3. The Block Downloader + Syncer
+4. Documentation
+
+# Funding
+
+I am asking for $45/hr for 50hrs/week for 3 months at $142/XMR this gives 190 XMR

boog_3_months_cuprate_2.md

+---
+layout: cp
+title:  Boog900 full time work on Cuprate (3 months)
+author: Boog900
+date: June 28, 2024
+amount: 215
+milestones:
+  - name: Month 1
+    funds: 71 XMR
+    done: 4 September 2024
+    status: finished
+  - name: Month 2
+    funds: 72 XMR
+    done: 29 October 2024
+    status: finished
+  - name: Month 3
+    funds: 72 XMR
+    done: 6 January 2025
+    status: finished
+payouts:
+  - 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).
+
+# Who
+
+I am [Boog900](https://github.com/Boog900), you can see my last CCS [here](https://ccs.getmonero.org/proposals/boog_3_months_cuprate.html).
+
+# What
+
+Cuprate is very close to having an alpha binary ready. During my last CCS I created a test binary with the components
+we currently have to test a full sync, a full sync with this binary wasn't achieved due to a few issues discovered, which have since
+been fixed, however timings up to the height (~2,300,000) we did reach are promising for Cuprate's performance.
+
+This proposal will be for 3 months work on Cuprate while continuing coordination of the Cuprate project and also being an active maintainer
+for monero-rs.
+
+My main plan is to work towards what is needed to achieve a working alpha binary that can sync, stay synchronized, handle reorgs and
+participate in transaction propagation. 
+
+This will include:
+
+### Blockchain service
+
+The blockchain service is what will keep the blockchain's state, handle incoming blocks, decide when to re-org, etc. It will use
+the consensus and database services created in previous CCS proposals (https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/405 & https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/422).
+
+### Tx Pool
+
+The transactions in the txpool will be stored in a separate database from where the blockchain is stored, using the same database abstraction. 
+I will work on the txpool tables and the service that will handle txpool requests from other parts of Cuprate.
+
+Hinto, as apart of their CCS, has already began work here. Although Hinto's CCS includes a small note about completing the persistent transaction 
+pool: `The persistent transaction pool will be finished within this CCS`, I will be taking over from where hinto has left off as the exact 
+transactions pool tables are yet to be decided and the transaction pool service is heavily tied in to other areas I will be working on. 
+
+### Peer Protocol Request Handler
+
+The peer protocol request handler is what is given to `cuprate-p2p`, it is used to handle requests for blocks/transactions and other chain data.
+In our test binary I created a mock request handler that just doesn't respond to requests, this lead to pretty unstable connections, with the other
+components here though I will be able to create a working request handler.
+
+### Other Tasks
+
+There are other smaller things that need to be worked on for Cuprate to be ready for an alpha binary, mainly bug fixes and leftover TODOs.
+
+# Milestones
+
+Unlike my previous CCS proposals, I am basing milestones on hours worked instead of completed work. 
+
+There are a few reasons for this. The exact work needed is likely to change as we get closer to an alpha binary, for example, bugs that need
+fixing may come up. It also brings the proposal closer to the average full-time developer proposal.
+
+Although doing milestones based on time requires more trust, we are doing weekly [Cuprate meetings](https://github.com/monero-project/meta/issues/1028) 
+where I am, and will be reporting progress.
+
+# Funding
+
+I am asking for $55/hr for 50 hrs/week for 3 months at $166/XMR. This gives 215 XMR.
+
+This is a raise over my last CCS ($45 -> $55), I believe this is justified given my past work.  

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
 amount: 130
 milestones:
-  - name: Bp++ eprint peer review
+  - name: Bp++ eprint peer review CCS part
     funds: 130
-    done:
-    status: unfinished
+    done: 6 March 2024
+    status: finished
+  - name: Bp++ eprint peer review GenFund part
+    funds: ~$14000
+    done: 29 March 2024
+    status: finished
 payouts:
-  - date:
-    amount:
+  - date: 7 March 2024
+    amount: 130
+  - date: 7 April 2024
+    amount: 101
 ---
+
 ## Bulletproofs++ Peer Review
 
 This CCS will provide funding for the first step towards Bulletproofs++ implementation in Monero. (and also the planned Seraphis upgrade). Bulletproofs+ were added in the latest [Network Upgrade](https://www.getmonero.org/2022/04/20/network-upgrade-july-2022.html). They reduce the typical transaction size by ~5-7% and improve typical verification performance by ~5-7%, making every transaction lighter and faster. Bulletproofs++ claims to significantly improve upon this (e.g. ~27% smaller than Bp+).
 
 ## Scope / Deliverables
 
-A full peer review of the eprint version [[link]](https://moneroresearch.info/index.php?action=resource_RESOURCEVIEW_CORE&id=83&browserTabID=) of the paper. Note that at the time of writing this proposal, the paper is not yet published in a peer-reviewed conference/journal.
+A full peer review of the eprint version [[link]](https://eprint.iacr.org/archive/2022/510/20230717:163509)  of the paper. 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 recommendations, notes, weaknesses, and issues (if any) of the BP++ paper touching on:
 - The soundness, completeness, and zero knowledge portions of the paper.
-- Efficiency. Aggregation. Batching. MPC compatibility.
+- Efficiency* Aggregation. ~~Batching. MPC compatibility.~~ 
 - Making sure it fits neatly and completely into the place that BP+ currently sits by checking the correctness of proofs.
 
+## Out of scope
+
+- Multiparty computation. There are no specific protocols presented for this, and no corresponding security model of proofs of security.
+- Batch verification. While the preprint mentions that BP++ supports batch verification, it provides no details on the corresponding algebra.
+- Multi-asset transactions. The preprint discusses multi-asset transactions in the context of its protocols, but these are not required for range proofs.
+- Optimized binary range proofs. The protocol proposed for optimized binary range proofs has only an informal and vague security proof that is insufficient to assert the claims of the corresponding theorem.
+
 ## Funding
 
-- $16,500 + 20% buffer = $19800 gives 130XMR @ 152.30USD
+The latest version of the paper is now greatly expanded. CypherStack has given a new quote for this paper of $32,000. Core will decide how the shortfall is handled.
+
 - Funds are released by Core to a third party and converted. 
-- $16,500 will be paid directly to [CypherStack](https://cypherstack.com/).
+- $32,000 will be paid directly to [CypherStack](https://cypherstack.com/).
 - Excess XMR after conversion will be donated to the next Bp++ CCS.
 - Any shortfalls from volatility will be paid by the Monero General Fund.

busyboredom-standalone-acceptxmr.md

@@ -3,17 +3,31 @@ layout: wip
 title: Standalone AcceptXMR
 author: busyboredom
 date: February 31, 2023
-amount: 14
+amount: 44
 milestones:
-  - name: Maintenance
+  - name: Dockerize AcceptXMR
     funds: 14
+    done: 5 July 2024
+    status: finished
+  - name: Wordpress Plugin
+    funds: 10
+    done:
+    status: unfinished
+  - name: Maintenance 1 year
+    funds: 20
     done:
     status: unfinished
 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.

cypherstack-gbp-security-proofs.md

+---
+layout: cp
+title: Generalized Bulletproofs Security Proofs
+author: Cypher Stack
+date: April 4, 2024
+amount: 200
+milestones:
+  - name: Funded
+    funds: 200
+    done: 11 April 2024
+    status: finished
+  - name: Completed
+    funds: 0
+    done: May 6th, 2024
+    status: finished
+payouts:
+  - date: 11 April 2024
+    amount: 200
+---
+
+Hello everyone, Diego "rehrar" Salazar here on behalf of [Cypher Stack](https://cypherstack.com/). We've recently [made a proposal to review the general Seraphis paper](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/441). After some discussion with MRL, including at an official MRL meeting, it was decided that while all parties do want this done eventually, there are perhaps some more immediate wins available for Monero's privacy tech, particularly in the form of Generalized Bulletproofs (GBP).
+
+To summarize what it is, why it's important, and what work will be done, I post a blurb from Dr. Aaron Feickert, Cypher Stack's on-staff cryptographer:
+
+```
+"Full-chain membership proofs are a construction being proposed for future Monero protocol upgrades. These proofs can be used to replace ring signatures (used in the current Monero protocol) and membership proofs (used in the proposed Seraphis protocol) to improve privacy.
+
+The proofs use a technique called curve trees that in turn rely on a Bulletproofs arithmetic circuit protocol. However, to meet technical requirements, the arithmetic circuit protocol needs to be modified to handle Pedersen vector commitments in a specific way. The modification, called generalized Bulletproofs, was informally described, but completely implemented, in a curve trees proof-of-concept implementation by one of its authors.
+
+In collaboration with Firo and Luke Parker, we've already done a more thorough documentation of generalized Bulletproofs to aid future implementation. To our knowledge, however, the technique has never been proven secure.
+
+Cypher Stack proposes to develop security proofs for generalized Bulletproofs. The goal is to produce a modified Bulletproofs arithmetic circuit protocol security proof that accommodates the generalized Bulletproofs technique and shows the required properties of perfect completeness, perfect special honest-verifier zero knowledge, and computational witness-extended emulation. This will mirror the existing proof of Theorem 4 in the Bulletproofs preprint.
+
+We stress that it is not known if the generalized Bulletproofs technique readily admits such a security proof. As such, this is a research proposal that has a nontrivial risk of failure. Should the research be successful, Cypher Stack will produce a report containing the proof. Should it fail, Cypher Stack will produce a report containing any relevant information that may be useful for other researchers."
+```
+
+A few things I (rehrar) want to emphasize on this quote.
+
+1. There is a non-negligible chance of failure to produce a satisfying proof. If this happens, the proposal is not considered a failure, and our deliverable changes to a report for future research.
+2. Much of this work will be directly applicable and cross-over with Seraphis in the future. So it's not a distraction that will delay things, in that sense.
+
+Cypher Stack asks for a total of 200 XMR to complete the review. We add a 10% volatility buffer, bringing the total up to 220 XMR. We aim to complete the review within 1.5 calendar (actual hours are not 1.5 months of man hours, but we have other work for other clients as well) months of the proposal being funded.
+
+EDIT: We have been asked during the community and MRL meetings to remove the volatility buffer and receive the entirety of the money up front to simplify things and get this merged faster. The original proposal above remains in its original state for posterity purposes, but the proposal has changed to reflect the new terms. The new total is 200 XMR to be paid out as soon as the proposal is merged and fully funded.

cypherstack-sarang-triptych-research.md

 ---
-layout: wip
+layout: cp
 title: Triptych research and optimizations
 author: Cypher Stack
 date: April 8, 2021
@@ -32,6 +32,10 @@ payouts:
     amount:
 ---
 
+### Proposal closed
+
+The remaining funds (12.65XMR) have been donated to the General Fund.
+
 THIS PROPOSAL HAS BEEN CHANGED FROM TRIPTYCH RESEARCH OPTIMIZATIONS TO TRIPTYCH MULTISIG RESEARCH AFTER A MEETING WITH THE MONERO DEVS ON APRIL 21, 2021.
 
 ## Brief Intro

dangerousfreedom-2023-09.md

 ---
-layout: fr
+layout: cp
 title: dangerousfreedom - wallet work
 author: DangerousFreedom
 date: September 17, 2023
 amount: 64 
 milestones:
   - name: deliver of proposed demonstrator and wallet functions
-    funds: 64 
-    done:
-    status: unfinished
+    funds: 56
+    done: 30 March 2024
+    status: finished
 payouts:
-  - date:
-    amount:
+  - date: 10 April 2024
+    amount: 56
 ---
 
+## Note amount wasn't updated properly so there is 8 XMR left over from this proposal.
+
 ## What and Why ?
 
 The end goal is twofold:

dangerousfreedom-seraphis_wallet_until_regtest.md

+---
+layout: wip
+title: dangerousfreedom - seraphis wallet work until regtest
+author: DangerousFreedom
+date: March 30, 2024
+amount: 80.64
+milestones:
+  - name: deliver of proposed demonstrator of a wallet in a regtest
+    funds: 80.64
+    done:
+    status: unfinished
+payouts:
+  - date:
+    amount:
+---
+
+## What and Why ?
+
+Since we have now a basic demonstrator of a wallet using a mock ledger, my next goal is to have it on a real ledger. Many components are well developed for that goal like the enote_scanner from @jberman with @SNeedlewoods modifications and the serialization functions from @jeffro256 to enable write/reading transactions into a block in a blockchain file. So the idea is to put all the components together and finish developing the remaining ones in order to have a functional (local) regtest.
+
+The tasks I can foresee for that goal are:
+
+- Review @ghostway's KeyContainer to get it into its final form
+- Have a working MockLedger that correctly handles legacy and seraphis enotes.
+- Have a prototype of a wallet that loads a legacy wallet, derive a seraphis wallet from that and create seraphis transactions (both using Grootle proofs and FCMP) using legacy enotes.
+- Create the basic functions to mine blocks and send enotes to an user.
+- Save/Load the blocks into the blockchain using a LMDB database. 
+- Make sure to have a basic wallet working on a LMDB regtest database capable of doing basic functions like loading the wallet keys and its enote/history, transferring, visualizing and making knowledge proofs on enotes.
+
+There are many intermediary tasks that would be necessary to do that I am not fully aware of now.
+
+## Who?
+
+- I did [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/298), [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/344), [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/377) and [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/409) previous works.
+
+I propose to work for 42 USD per hour, 20h per week, for 12 weeks (or until we have a functional seraphis wallet in regtest), which makes 80.64 XMR considering 125 USD/XMR.

erciccione-website5.md

 ---
-layout: wip
+layout: cp
 title: "ErCiccione: 3 more months part time work on Getmonero.org (April-June) + Holiday"
 author: erciccione
 date: 11 April 2021

escapethe3ra-monero-observer-2023-q4.md

 ---
-layout: fr
+layout: cp
 title: escapethe3RA Monero Observer maintenance (2023 Q4)
 author: escapethe3RA
 date: Oct 12, 2023
@@ -7,23 +7,19 @@ amount: 39
 milestones:
   - name: October
     funds: 13
-    done:
-    status: unfinished
+    done: 1 November 2023
+    status: finished
   - name: November
     funds: 13
-    done:
-    status: unfinished
+    done: 1 December 2023
+    status: finished
   - name: December
     funds: 13
-    done:
-    status: unfinished
+    done: 1 January 2024
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 7 January 2024
+    amount: 39
 ---
 
 # What

escapethe3ra-monero-observer-2024-q1.md

+---
+layout: cp
+title: escapethe3RA Monero Observer maintenance (2024 Q1)
+author: escapethe3RA
+date: Jan 19, 2024
+amount: 36
+milestones:
+  - name: January
+    funds: 12
+    done: 31 January 2024
+    status: finished
+  - name: February
+    funds: 12
+    done: 29 February 2024
+    status: finished
+  - name: March
+    funds: 12
+    done: 31 March 2024
+    status: finished
+payouts:
+  - date: 9 April 2024
+    amount: 36
+---
+
+# What
+
+I will continue to maintain *Monero Observer* (https://monero.observer) for the next 3 months (2024 Q1): January, February and March.
+
+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*
+- 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/As Needed: publish the *MO Cypherpunk Transmission Report*
+- Monthly (1st): publish the *MO Blitz Report*
+- As Needed: housekeeping (revise and update reports)
+- As Needed: outreach (engage with the community on Matrix, XMPP, email)
+- 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 2250 x daily MO stories/reports (https://monero.observer/stories)
+- published 1087 x on demand MO Community Messages (https://.monero.observer/tag/community)
+- published 25 x monthly MO Blitz reports (https://monero.observer/tag/blitz)
+- published 81 x weekly Monero Dev Activity Reports (https://monero.observer/tag/dev)
+- published 86 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 24 x on demand Monero Workgroup Meeting Log Summaries & uploaded 195 meeting logs to MO (https://monero.observer/tag/logs/)
+- published 17 x on demand MO Cypherpunk Transmission reports (https://monero.observer/tag/CT)
+- added 305 x on demand MO Resources (https://monero.observer/resources)
+- posted 295 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 MO Community Messages, Monero Dev Activity Report, XMR TA Report, MO Artistic Saturday, and Cypherpunk Transmission initiatives (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 MO XMR Stats section (https://monero.observer/stats/)
+- added MO Resources section (https://monero.observer/resources/)
+- added MO Calendar section (https://monero.observer/tag/calendar/)
+- added MO Blacklist section (https://monero.observer/blacklist/)
+- added multiple RSS feeds (https://monero.observer/rss/)
+- started self-hosting a terminal-based git server containing the MO UI source code (https://monero.observer/monero-observer-self-hosted-git-server/)
+- created a hidden service for MO (https://monero.observer/monero-observer-new-server-hidden-service/)
+- other project improvements (https://monero.observer/changelog/)
+ 
+# Proposal
+
+I will work for 25 hours per week over 3 months at a rate of 0.12 XMR / hour. At ~$160 / XMR (21 daily EMA) this makes 36 XMR (0.12 * 100 * 3).

escapethe3ra-monero-observer-2024-q2.md

+---
+layout: cp
+title: escapethe3RA Monero Observer maintenance (2024 Q2)
+author: escapethe3RA
+date: Apr 11, 2024
+amount: 48
+milestones:
+  - name: April
+    funds: 16
+    done: 2 May 2024
+    status: finished
+  - name: May
+    funds: 16
+    done: 1 June 2024
+    status: finished
+  - name: June
+    funds: 16
+    done: 1 July 2024
+    status: finished
+payouts:
+  - date: 18 May 2024
+    amount: 16
+  - date: 17 June 2024
+    amount: 16
+  - date: 16 July 2024
+    amount: 16
+---
+
+# What
+
+I will continue to maintain *Monero Observer* (https://monero.observer) for the next 3 months (2024 Q2): April, May and June.
+
+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/As Needed: publish the *MO Cypherpunk Transmission Report*
+- Monthly (1st): publish the *MO Blitz Report*
+- As Needed: housekeeping (revise and update reports)
+- As Needed: outreach (engage with the community on Matrix, XMPP, emails)
+- As Needed: make sure the website is live and working as expected (server maintenance, billing, etc)
+- 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 2438 x daily MO stories/reports (https://monero.observer/stories)
+- published 1181 x on demand MO Community Messages (https://.monero.observer/tag/community)
+- published 28 x monthly MO Blitz reports (https://monero.observer/tag/blitz)
+- published 93 x weekly Monero Dev Activity Reports (https://monero.observer/tag/dev)
+- published 98 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 25 x on demand Monero Workgroup Meeting Log Summaries & uploaded 235 meeting logs to MO (https://monero.observer/tag/logs/)
+- published 17 x on demand MO Cypherpunk Transmission reports (https://monero.observer/tag/CT)
+- added 320 x on demand MO Resources (https://monero.observer/resources) & 16 x Blacklist items (https://monero.observer/blacklist)
+- posted 336 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.16 XMR / hour. At $127 / XMR (21 daily EMA) this makes 48 XMR (0.16 * 100 * 3).

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