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

+---
+layout: cp
+title: Continuation of Core Monero Concepts - A Series of Animated Explainers
+author: VOSTOEMISIO
+date: October 3, 2023
+amount: 37
+milestones:
+  - name: Random X and Understanding the significance of ASIC resistance
+    funds: 18
+    done: 26 June 2024
+    status: finished
+  - name: Nodes and why every Monero enthusiast should consider running one.
+    funds: 18
+    done: 8 April 2024
+    status: unfinished
+payouts:
+  - date: 30 April 2024
+    amount: 18
+  - date: 16 July 2024
+    amount: 18
+---
+
+_Note: this proposal has been awarded 36 XMR from [New Animated Videos](https://ccs.getmonero.org/proposals/savandra-videos-for-monero.html)_
+
+Hey all!
+
+Thank you for the amazing reception and feedback of our first ccs-proposal and the Tail Emission video. We've seen a lot of excitement and engagement with over 7,000 accumulated views in just the initial days.
+
+Our vision is to keep diving deeper into Monero's complex and sometimes tricky and misunderstood features, translating them into short, engaging, and most importantly, understandable animated videos. Here's what we suggest to cover in this proposal:
+
+• Random X: Understanding the significance of ASIC resistance
+
+• Breaking down the how-to and the rationale for P2Pool.
+
+• Nodes: Why every Monero enthusiast should consider running one.
+
+• Fungibility: Explaining its essence in the context of Monero.
+
+Quality & Timeline: 
+
+As we've showcased in our recent work, we promise high-quality output, similar to our Tail Emission video ( https://youtu.be/sRwSqM0YBto?si=vAFA7iRUWAvaV5Wi ). In this proposal, we are committing to an accelerated timeline and we aim to finalize and release one video per month. Therefore, we aim to wrap up the entire series in just 4 months after proposal’s approval. However, acknowledging the potential for unforeseen challenges, we request an additional 2 months as a buffer, making the total proposed timeline 6 months. We estimate each video to be approximately 2 minutes in length.
+
+Budget & Collaboration: 
+
+Given the scope, we propose 18 XMR per video, a total of 72 XMR for the entire series, broken down across milestones. As with our first video, we will collaborate with Xenu, sharing 5 XMR per video of the funds with him. This collaboration ensures the technical soundness of our scripts and storyboards, guaranteeing that each video is not only engaging but also accurate. As always, we are open to adjustments based on feedback and the evolving requirements of the project.
+
+Open Source & Community:
+
+Post-completion, all materials and animations will be open-sourced for the community's further use and reference.
+We're eager to dive deep and clarify these essential Monero concepts with everyone. Your feedback, suggestions, and enthusiasm drive us, and we're all ears for what you have to say.
+
+//VOSTO
+
+ www.vostoemisio.com
+
+2CA8 85AC 923F 07A3 3656 8425 83F1 9CFF 27BE A177
+
+

VOSTOEMISIO-FCMP-Animated-Explainer.md

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

VOSTOEMISIO-TailEmission-Concept-Video.md

+---
+layout: cp
+title: VostoEmisio Animated Tail Emission Core Concept Video
+author: VOSTOEMISIO
+date: May 12, 2023
+amount: 9
+milestones:
+  - name: Complete Script
+    funds: 3
+    done: 26 September 2023
+    status: finished
+  - name: Complete Look and feel
+    funds: 3
+    done: 26 September 2023
+    status: finished
+  - name: Complete Video
+    funds: 3
+    done: 26 September 2023
+    status: finished
+payouts:
+  - date: 6 November 2023
+    amount: 9
+---
+
+Hey everyone!
+
+Since this is my first CCS proposal, I thought I'd give you a quick intro to who we are:
+
+I run a marketing company in the traditional space. Here, we work under the name "VostoEmisio,". We've already done some work for Monero and other privacy-centric projects. Our journey began in early 2022 when we helped Rucknium revamp the logo and branding for these two projects:
+https://bchmempool.cash/
+https://beta.redteam.cash/
+
+This year, we won the Monerokon 3 Design Proposal (www.monerokon.com), and we're currently working on brand refreshing and marketing for Firo: https://forum.firo.org/t/fcs-proposal-firo-3-month-trial-marketing-contract/2905/4
+
+However, we haven't had the chance to show off our skills in motion assets and animation yet. As a long-time Monero user, I find it frustrating when browsing crypto-Twitter and seeing basic misconceptions like "infinite supply," "can't scale," and "dynamic block size???" still being spread, particularly by the uninformed "BTC maxis."
+
+So, I propose that we create an animation series featuring short (1 min or so), ELI5-style explainer videos that break down the key concepts of how Monero works in a simple and digestible way that could easily be shared every time we, the community, face misleading comments. I suggest we start with one video and, if the result is satisfactory, create more based on the community's preferred topics.
+
+### Promise and assurances:
+
+- With the budget for this proposal, we're confident we can deliver quality on par with this example: https://www.youtube.com/watch?v=pYOSfEgF32Y&ab_channel=XPLAI
+- Completion expiry date set to 4 months post-approval for this proposal
+- Open-sourcing the project materials after completion
+
+If that sounds good to you all, I'd be happy to jump into the details and start working on the script and storyboard. I would like to start with ( as our name vosto emisio also springs from), the tail emission concept. 
+
+Regarding the budget, we're not sure, but we're willing to try this out for 9 XMR for the first video. We can adjust the amount up or down after we see how the first project goes since this would be our first official collaboration with the community. I believe this project will take about a month to complete, maybe a bit longer since this is our first time working with the community.
+
+Any questions or thoughts?
+
+
+    

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

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

adrelanos-debian-package.md

 ---
-layout: wip
+layout: cp
 title: "Monero Debian Package Repository for 2 years"
 amount: 73
 author: Patrick Schleizer
@@ -11,19 +11,19 @@ milestones:
     status: finished
   - name: "Monero Debian Package Maintenance 2021"
     funds: 25% (18 XMR)
-    done:
-    status: unfinished
+    done: 31 December 2021
+    status: finished
   - name: "Monero Debian Package Maintenance 2022"
     funds: 25% (18 XMR)
-    done:
-    status: unfinished
+    done: 13 March 2023
+    status: finished
 payouts:
   - date: 18 February 2021
     amount: 37
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 21 March 2022
+    amount: 18
+  - date: 21 May 2023
+    amount: 18
 ---
 
 ### Importance to the Monero Community

anhdres-monero-garden.md

+---
+layout: wip
+title: Monero Garden
+author: anhdres
+date: September 30, 2022
+amount: 71
+milestones:
+  - name: Texts and structure done
+    funds: 30
+    done: 31 May 2024
+    status: finished
+  - name: Illustrations and animations done
+    funds: 30
+    done:
+    status: unfinished
+  - name: Website up
+    funds: 11
+    done: 31 May 2024
+    status: finished
+payouts:
+  - date: 18 June 2024
+    amount: 41
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+# Monero Garden
+
+## The idea
+
+The Monero Garden would initially be a website available at [monero.garden](https://anhdr.es), that worked as a clean and friendly space to start someone's Monero journey. Is a resource I wished many times existed when I told someone about Monero. The naming has two reasons: it acts as a Monero kindergarten of sorts, the starting point of your education, where you learn without any dread; but also as a real garden, with paths you can graciously take and effortlessly stroll at your own pace while discovering new things on the way.
+
+Its language, both visual and writing, should be approachable for a 11 year old and above. Trying my best to keep it clean of technical wording, yet making it engaging for an adult as well. It's a difficult balance but I think it's worth pursuit it.
+
+I want to try a different approach to the rest of Monero content I've seen so far, kind of a Choose Your Own Adventure book, where the questions that pop inside the reader's head guide the consumption of the material, and not presenting (if possible) information that wasn't felt the need for. The aim is *relevancy*, which should maximize retention and engagement.
+
+I believe that the pre-adolescents are specially important to talk to. They are starting their financial life earlier and earlier, the boundaries of *real money* and *virtual money* are going to be as dilluted as ever, so if they find Monero soon enough, they could be a strong agent of change and help avoid the dystopian version of that merge. Believe it or not, we (I'm older than 40 now) are not the future anymore. Luckily we're still the present, so there's a lot we can do!
+
+## Layout
+
+Overall, it's design should mimic children picture books. Their design is not accidental. They display images and succinct text on almost every page, which don't work in a redundant way, but complement each other. Clean, minimal background and bold, colorful illustrations. A consistent character design and color palette. If needed to reinforce a concept, the illustrations could be short animations.
+
+At the start page, the visitor would be faced with three choices. In my interactions with newcomers, those three I've noticed are the main starting points of everyone's Monero path:
+
+- How to use Monero.
+
+- Why to use Monero.
+
+- How Monero works.
+
+Each choice would take the visitor to a different path, of increasing length. According to my notes, *how to use it* is the shortest and *how it works* the longest. The way I envision it, besides navigation and a general menu, each page would have four elements:
+
+- The illustration
+
+- The short, bold statement.
+
+- A longer, yet brief explanation of the statement above.
+
+- An option to expand the topic if interested, like footnotes or links to outside sources to explore.
+
+## Scope
+
+To me, making it a website is the most effective initial form. It's big and clean, and can be accessed almost everywhere. For obvious reasons to this community, it should also be accesible via Tor and i2p. **So a working, fully functional website with those three content branches is the scope of this proposal.**
+
+The nature of the idea makes it very versatile to use as basis for a book in both physical and electronic forms, a series of animated, narrated videos, or even an app. These formats are outside of the scope of this proposal but if the material is good enough to engage people I think all those mediums would have their merits.
+
+The initial material would be in English, but obviously I see the appeal of having it translated in as many languages as possible, since it's particularly targeted towards newcomers.
+
+## Rights
+
+I plan to release this material with either a [Creative Commons BY-NC-SA  license](https://creativecommons.org/licenses/by-nc-sa/4.0/) that allows anyone to obviously access it for free (it's a website) but also create derivative works, translate it, or distribute it freely, as long as credit is mantained and it's not exploited commercially.
+
+## Budget
+
+Based on my experience, I think this first stage will take roughly 3 months. I plan to allocate 4 hrs per day to this project. At an hourly rate of 40 USD, that's 4 hrs x 60 working days = 9600 USD.
+
+I'd also need help with the technical aspects of setting up the server and different access. For what I could gather, it would take a 20 hours of work, which at the same rate of 40 USD/h amounts to 800 USD.
+
+At the current XMR price of 145 USD/XMR, it would be 71 XMR.
+
+I plan to pay domain, hosting, and other small expenses out of that budget. If the traffic were so big it demanded a considerable investment, I'd consider either open a new request for funds, or looking into other possible solutions that wouldn't cause any extra cost for the community.
+
+## Relevant information about me
+
+I've worked as creative director, illustrator, copywriter, and animator for the past 15 years. You can take a look at some of my commercial work at [Sloop Studio](https://www.sloopstudio.tv/).
+
+In the Monero world, I've been in the community since 2017, since then I've worked alongside with @m2049r and @Baltsar in [Monerujo](https://www.monerujo.io/), doing content, communications, support, and UX. One example would be [the articles explaining features or concepts behind Monero.](https://anhdres.medium.com/)
+
+I've worked alongside @serhack in both [Mastering Monero](https://masteringmonero.com/) and [serhack.me](https://serhack.me/), doing all the illustrations.
+
+Worked with @rehrar on designs for [Cypher Market](https://www.cyphermarket.com/) and [Cypher Stack](https://cypherstack.com/). Also materials for @msvblab's [Monero Devices](https://shop.monerodevices.com/). As well as designs for several Monero-related projects and individuals.
+
+Hosted the short lived [El Monero](https://www.youtube.com/channel/UCNvrbeVzrszpN7vQnMoCTVA/videos) podcast together with @rottenwheel, and gave out a few [public](https://youtu.be/s8RPE5AIB-A) [talks](https://youtu.be/78zcD7yWQ0E) and [interviews](https://youtu.be/Cx7XkZxXOKM) introducing Monero to the Spanish-speaking public.
+
+On a related note, I've made the illustrations for the newest [Tails](https://tails.net) redesign and I keep working closely on their support materials.
+
+That's pretty much all I can think of right now, be sure to ask away!

binarybaron-unstoppableswap.md

 ---
-layout: wip
+layout: cp
 title: "XMR BTC Atomic Swaps Desktop GUI"
 author: binarybaron
 date: October 1, 2021
@@ -7,35 +7,35 @@ amount: 52
 milestones:
   - name: "Working Prototype of GUI"
     funds: 45
-    done:
-    status: unfinished
+    done: 6 February 2022
+    status: finished
   - name: "Tor & Rendezvous Protocol Integration"
     funds: 4
-    done:
-    status: unfinished
+    done: 7 May 2022
+    status: finished
   - name: "Infrastructure maintenance (October - November)"
     funds: 1
     done: 30 November 2021
     status: finished
   - name: "Infrastructure maintenance (December - January)"
     funds: 1
-    done:
-    status: unfinished
+    done: 31 January 2022
+    status: finished
   - name: "Infrastructure maintenance (February - March)"
     funds: 1
-    done:
-    status: unfinished
+    done: 31 March 2022
+    status: finished
 payouts:
   - date: 6 December 2021
     amount: 1
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 3 February 2022
+    amount: 1
+  - date: 8 February 2022
+    amount: 45
+  - date: 2 April 2022
+    amount: 1
+  - date: 18 May 2022
+    amount: 4
 ---
 
 # What

boog_2_months_cuprate.md

+---
+layout: cp
+title: Boog900 full time work on Cuprate, the Rust Monero node (2 months)   
+author: Boog900
+date: August 03, 2023
+amount: 130
+milestones:
+  - name: Consensus rules up to RingCT
+    funds: 53 XMR
+    done: 27 October 2023
+    status: finished
+  - name: All Consensus rules up to present
+    funds: 53 XMR
+    done: 10 January 2024
+    status: finished
+  - name: Consensus Rules document
+    funds: 24 XMR
+    done: 10 January 2024
+    status: finished
+payouts:
+  - date: 5 November 2023
+    amount: 53
+  - date: 26 January 2024
+    amount: 77
+---
+
+Cuprate is a WIP Rust Monero node that SyntheticBird45 started back in Feburary, I joined the project not 
+long after that, but sadly me and SyntheticBird have not been able to spend much time on it. Even more sad 
+is that recently SyntheticBird decided to stop working on Cuprate for personal reasons that I will not get 
+into here.
+
+This CCS is to support me working on Cuprate full time for the next 2 months, In this time I will complete 
+the transaction/ block verification. While doing this, I will also create a `consensus rules` document, which 
+will document all of Moneros consensus rules from genesis to the current rules.
+
+# Why
+
+Currently, Monero only has one node written in C/C++, many would see this as an issue.
+Having only one implementation makes us more vulnerable to implementation bugs, having
+another node will help us to spot and fix these issues.
+
+monerods code is also a bit of a mess, as many devs who have worked on it would agree. Cuprate
+is a fresh start and is built with modularity in mind which will lead to a cleaner and easier
+to understand codebase.
+
+Having a `consensus rules` document will make it easier for developers to build software to interact
+with Monero. It will also make it easier to spot potential issues with consensus rules.
+
+# Who
+
+I am [Boog900](https://github.com/boog900), the current, and now solo, maintainer of Cuprate.
+
+# Design
+
+For an overview of the design see [here](https://github.com/Cuprate/cuprate/blob/main/misc/DESIGN.md)
+
+# What Has Been Done
+
+## P2P
+
+The peer-to-peer code is mostly complete; I have implemented levin headers, the epee binary format and all p2p messages.
+I have also done the p2p address book, individual peer request routing, handshakes and pruning calculations.
+
+## Blockchain Data
+
+I made a PR to monero-serai adding decoding/encoding/hashing of legacy transactions and blocks so this is complete.
+
+## Consensus Checks
+
+There is still a lot to do here, but monero-serai has already done verifying for bulletproofs(+) and CLSAG.
+My PR to monero-serai also contained an unverified MLSAG verify function and a WIP Borromean range proofs
+function.
+
+## Database
+
+The initial database abstraction is complete, and we have defined the tables (we have copied monerod for
+the moment). We have also created the methods to add and get blocks and transactions from the database.
+
+Still to-do: We need to investigate the database schema for optimizations.
+
+# Tasks
+
+We need to implement/ get ready for production verifying for MLSAG, borromean range proofs and V1 ring signatures, there are other 
+checks we need to do, but these are the big ones. As Monero does not have a protocol document, we will have to go through monerod 
+to find every check it performs and do them in Cuprate.
+
+Cuprates consensus checks will be grouped together in a single location, so they are clear and not spread around the codebase,
+they will also reference the `consensus rules` document at every check. If some checks are done elsewhere, for example some are done at
+deserialization, we will either duplicate the check or, if its expensive, we will put a comment referencing the check and the
+`consensus rules` in the single location.
+
+We also need to create bindings for Moneros legacy CryptoNight POW algorithms and select a Random-X binding. There is a Rust 
+Random-X implementation, which we plan to implement as an option, but we won't enforce it as it lacks review/ usage.
+
+As our P2P/ database code still needs some work, we will be using monerods RPC interface to test the code.
+
+*All code produced for this CCS will be licensed under MIT.*
+
+### Milestones
+
+1. ###### All Consensus rules up to RCT
+   Implement verification for transactions and blocks before RCT.
+2. ###### All Consensus rules up to present
+   Implement verification for all transactions and blocks.
+3. ###### Creation of the `consensus rules` document
+
+
+# Funding
+
+I am asking for $45/hr for 50hrs/week for 2 months at $148/XMR this gives 130 XMR

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: cp
+title: Bulletproofs++ Peer Review
+author: Monero Research Lab
+date: March 22, 2023
+amount: 130
+milestones:
+  - name: Bp++ eprint peer review CCS part
+    funds: 130
+    done: 6 March 2024
+    status: finished
+  - name: Bp++ eprint peer review GenFund part
+    funds: ~$14000
+    done: 29 March 2024
+    status: finished
+payouts:
+  - 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://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.~~ 
+- 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
+
+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. 
+- $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

+---
+layout: wip
+title: Standalone AcceptXMR
+author: busyboredom
+date: February 31, 2023
+amount: 44
+milestones:
+  - 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.
+
+## Summary
+I would like to create a standalone, dockerized, AcceptXMR-based payment gateway with wordpress
+support.
+
+AcceptXMR ([demo](https://busyboredom.com/projects/acceptxmr),
+[docs](https://docs.rs/acceptxmr/latest/acceptxmr/),
+[repo](https://github.com/busyboredom/acceptxmr/)) is a payment gateway library (or crate, in rust
+lingo) I wrote as a hobby project and have made available to the community. While my library serves
+its purpose well, I understand that most merchants are not programmers therefor cannot use
+AcceptXMR.
+
+This proposal aims to make AcceptXMR usable for anyone capable running a docker container and
+installing a wordpress plugin.
+
+## Why AcceptXMR
+Lots of reasons!
+* View pair only, no hot wallet.
+* Subaddress based (as opposed to the older integrated addresses).
+* Pending invoices can be stored persistently, enabling recovery from power loss.
+* Ignores transactions with non-zero timelocks.
+* Zero-conf works out of the box.
+* No local node, wallet RPC, or block explorer needed. Just pick a public remote node.
+
+And of course, I am already intimately familiar with it.
+
+## How It'll Happen
+I will dedicate a portion of my weekends (you can expect about 10 hours a week on average) to
+completing the following milestones. There will be some weeks with more progress and others with
+less, but that's the average I'll be aiming for.
+
+### Dockerize AcceptXMR
+_14 XMR from xmrSale's abandoned funding._
+
+This is the largest milestone. I'll be taking the webserver and frontend work you see in my demo,
+cleaning it up significantly to bring it up to production standards and dockerizing it for easy
+setup. I will also provide documentation on how to perform that setup.
+
+### Wordpress Plugin
+_10 XMR from xmrSale's abandoned funding._
+
+Wordpress is popular, and it has a plugin system that supports custom payment gateways. I will write
+a wordpress plugin for the freshly dockerized AcceptXMR implementation. I will also provide
+documentation on how to use the plugin.
+
+### Maintenance for 1 Year
+_20 XMR total, with 6 XMR coming from xmrSale's abandoned funding and the remaining 14 XMR coming
+from this CCS proposal._
+
+Both rust and monero have rapidly changing ecosystems. Left alone, my work would likely be out of
+date by the end of the year due to breaking changes in my library's dependencies if nothing else.
+Keeping AcceptXMR up-to-date and functional is something I currently do for free, but building out a
+full standalone gateway adds overhead. For this reason, I've bookmarked 20 XMR for maintenance for 1
+year from the funding date.
+
+I am hesitant to provide target dates for first  two milestones above, but I have been maintaining
+AcceptXMR for over a year now and I don't plan on ghosting on it now.
+
+## Stretch Goals / Future work
+I'm not promising any of the following happens, but I'm putting it here to let the community know
+it's on my radar and I want to do it if I get the opportunity:
+* TOR support for the daemon RPC connection.
+* A no-JS frontend. I have an example with this implemented on github, but I'll have to clean it up
+a bit and integrate it into the new dockerized setup.
+* ZMQ support as a more performant alternative to polling the remote node.
+
+## Prerequisites
+Before I start work on this CCS, I'll need to wrap up changes I'm making with v0.12.0 of AcceptXMR.
+I'm not charging for that work, I'm just disclosing here that I need to resolve the issues in that
+milestone before I start work on this CCS.
+
+## License
+AcceptXMR is dual-licensed under the MIT and Apache 2.0 licenses. I am not planning on changing the
+license. It will always be under a permissive license.
+
+## About Me
+Busyboredom is _not_ an anonymous alias, you can see my minimally-redacted resume on my personal
+website [busyboredom.com](https://busyboredom.com).
+
+Proposal Expiration: January 1st, 2025.
+
+Note: This CCS was originally intended to be funded entirely by the 30 XMR leftover from the abanoned
+xmrSale project. At the request of the community, I have extended my maintenance commitment and
+increased the maintenance budget by 14 XMR. This change allows CCS donors to act as a final check on
+whether this proposal goes forward.

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.

ccs_test_update.md

+---
+layout: cp
+title: "Do they know its CCSmas time again?"
+author: plowsof
+date: December 25th 2023
+amount: 0.069
+milestones:
+  - name: 3+ months of transaction fees
+    funds: 0.069 XMR
+    done: 28 December 2023
+    status: finished
+payouts:
+  - date:
+    amount: 0.069
+---
+
+## Update 
+
+We're back! here is a brief summary of events before we get testing:
+
+- After the [CCS wallet was drained](https://github.com/monero-project/meta/issues/916) a Vote was held to determine if luigi [should continue as an escrow](https://github.com/monero-project/meta/issues/935).
+- Feedback obtained from the community determined how the new CCS wallet would be created/used in a secure manner;
+    - A new, single-purpose, air-gapped laptop was purchased (bluetooth/wifi disabled).
+    - The OS is Debian, and FeatherWallet will be used to sign and transport transaction files (via QR codes)
+	- Special thanks to tobtoht of FeatherWallet who worked tirelessly to push out a new version with convenient air-gapped signing capabilities, and every community member who offered feedback on how to best move forward.
+- The exact amount stolen + 21 XMR extra was sent to the General Fund ([X](https://twitter.com/WatchFund/status/1732391070216908886) / [nitter](https://nitter.net/WatchFund/status/1732391070216908886))
+- The machine where the drained wallet resided is being [forensically anaylised](https://github.com/monero-project/meta/issues/923) to determine if it was compromised. 
+- Luigi will escrow a temporary wallet until the [31st March 2024](https://github.com/monero-project/meta/issues/935#issuecomment-1867257410). 
+
+We must now begin to prepare for a 'post March 31st CCS' and wish everyone a merry RandomX'mas and a happy new year! 
+
+## Milestone 1
+
+Lets test the new CCS wallet by raising approx ~$12.16 / 0.069XMR to subsidise transaction fees for several hundred consolidations/payouts for the next 3 months. 

cryptogrampy-hotshop-dev.md

+---
+layout: cp
+title: HotShop Point of Sale
+author: cryptogrampy
+date: April 7, 2022
+amount: 18
+milestones:
+  - name: Milestone 1 - Create and publish payment code, perform basic payment generation and verification on deployed webapp
+    funds: 0
+    done: 29 May 2022
+    status: finished
+  - name: Milestone 2 - Create and publish draft Point of Sale user interface for feedback
+    funds: 8
+    done: 29 May 2022
+    status: finished
+  - name: Milestone 3 - Create finalized Point of Sale interface, create install and deployment instructions, publish freely available version
+    funds: 10
+    done: 27 May 2023
+    status: finished
+payouts:
+  - date: 1 June 2022
+    amount: 8
+  - date: 7 June 2023
+    amount: 10
+---
+
+HotShop - a browser-based, ephemeral, no-server point of sale
+
+**who**
+Hello, it's me, your great-grandfather CryptoGrampy.  You might know me on Twitter as @CryptoGrampy or from my work on the Monerod-on-Termux Android script, the Android PocketNode(tm), the Monero Drag n' Drop Electron app or from Friday morning bridge club in the cafeteria.
+
+**what is this**
+Monero is really lacking in the physical Point of Sale department. Let's fix that. 
+
+The HotShop will be a simple to use webapp with a simple aesthetic and UI similar to Kasisto (RIP) and POS.cash that can be accessed from just about any web browser (on mobile or desktop) with a slight amount of user customization (company name/image, etc). 
+
+You will be able to hit HotShop.cryptogrampy.com, enter your payment details, type in the desired XMR (optionally USD if you allow that API request) amount... a QR code and address will display, and the UI will update (payment confirmation progress as well) immediately when someone has paid the correct amount. 
+
+No hosting, private spend keys, personal servers/VPS's or payment gateways will be required. The app will be able to be added to any free web host- Github pages, etc and available for anyone to use because the magic happens in your browser (you'll be able to self-host it if you want) Users will need provide the app with their primary and view keys (no spend key involved!) on the client side (this info does NOT get sent to the server) and they will specify a remote Monero node of their choice.
+
+The tech stack will be something like: Monero-Javascript, Vue3, and Typescript.
+
+You'll be able to set this up at a garage sale, coffee shop, with your friends, etc and generate fresh/unused payment addresses displayed as QR codes.  In the settings, you'll set your desired number of confirmations (or do zero conf!), point it at a remote Monero node of your choice, and be able to collect payments and immediately validate that they were received/watch them as they get confirmed.  
+
+You'll be able to bookmark a link on your phone/browsers that contain all of the credentials necessary to start up the POS or have a QR code on a card containing a special link in your wallet... Just scan it with any device- your friend's phone, the library computer, the ipad at your store, and Boom! you have an instant Point of Sale.
+
+**Who does this benefit? Why do I need this when I can just use a mobile wallet?**
+- I think the physical Point of Sale situation is still pretty lacking in Monero
+- No existing wallets have good Point of Sale tech or UI
+- Perhaps you're in a situation where you can't have a wallet app on your phone/desktop but want to receive/validate payment
+- Perhaps you're in a situation where you want to be able to accept payments, but are worried about someone stealing your device or spend key wallet
+- An ephemeral point of sale that sort of lives on a QR code or bookmark in your phone sounds really cool
+- Maybe your mobile wallet is 1000000 blocks behind and want to IMMEDIATELY accept and verify a payment
+- Don't you want to make 100% sure your buddy at the bar *actually* sent those funds?  It's better than a static payment address.
+
+Also... Need yet another payment gateway?  The code for this will be written in a clean way that could be used in a NodeJS server or as a different front end implementation via simple exposed methods for instantiating the gateway, creating new payment requests and verifying payments.  If I have enough time, I will publish this portion of the code separately, and ideally as an npm library.  
+
+**what does this not do**
+- It's not going to keep track of payments that occurred before you hit the website (it's not going to be a full wallet).  It will sync at the latest block height to have the ability to immediately begin accepting payments
+- It's not going to keep track of prices, photos and items you have for sale in your store
+
+**potential reach ideas**
+- CSV export of tx's that occur in a session
+- Vending machine exploration
+- Pin code lock/unlock
+- Display past tx's within the session in a pleasant way
+- Local browser storage of user data
+- Importing prices/items via github repo json files
+- TOR support
+- Payment completion callback (provide a POST endpoint to receive completed payment data)
+
+**milestones**
+1st milestone - Coding up the basic payment portion in a nice/clean way, publishing a mostly bug-free, minimal version for testing user setting import and payments
+2nd milestone - Publish first draft of the POS interface (will be responsive), getting feedback from testers
+3rd milestone - Publish functioning POS to Github pages, etc, create documentation/video demo for use and self-hosting  
+
+**amount**
+I estimate that this will take about 4 to 5 weeks of mostly full time work and I am asking for 18 XMR. 
+
+**expiration**
+I will be working on this in the evenings and weekends but expect to have this complete within 4-8 months.

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: cp
+title: dangerousfreedom - wallet work
+author: DangerousFreedom
+date: September 17, 2023
+amount: 64 
+milestones:
+  - name: deliver of proposed demonstrator and wallet functions
+    funds: 56
+    done: 30 March 2024
+    status: finished
+payouts:
+  - 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:
+
+1) Get started with a basic variant to handle transactions both in legacy and seraphis: since a blockchain is made of blocks and blocks are made of transactions, we probably need a class to handle node queries smoothly between the classes `transaction` and `SpTxSquashedV1`. Hopefully this will generate discussions and start paving the way for future works about reading/writing data from/in the blockchain (1/4 of total time).
+
+2) Make a basic but broad demonstrator of the seraphis_wallet by: opening a wallet, make mock transactions, make transaction proofs, show enotes and balance, close wallet. A lot of work has been done in this direction but they are not yet fully organized. So the goal is to have this basic but organized demonstrator capable of doing that (3/4 of total time).
+
+I would work on the following tasks:
+- Create the `TransactionVariant = tools::variant<transaction, SpTxSquashedV1>` to handle similar methods of these classes.
+- Create unit_tests with legacy and seraphis transactions to test these methods.
+- Create basic functions for wallet initialization, program flow and terminal handling.
+- Create the basic components of a seraphis_wallet (basically the wallet needs to load/save the `KeyContainer`, `EnoteStore` and `TransactionHistory` components). 
+- Create basic function to fill `EnoteStore`.
+- Use mock transactions like `construct_tx_for_mock_ledger_v1` to create txs.
+- Add entries to `TransactionHistory` when a transaction creation is attempted.
+- Create terminal functions to show enotes and provide knowledge proofs.
+- Close/save wallet and make sure it loads everything when reopened.
+
+All the efforts will be documented and made public on the seraphis_wallet group. Unit_tests will be provided whenever possible.
+
+
+## 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) and [this](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/377) previous works.
+
+I propose to work for 40 USD per hour, 20h per week, for 12 weeks (or until I finish all the tasks), which makes 64 XMR considering 150 USD/XMR.