selsta-7.md → selsta-7p.md

 ---
 layout: cp
-title: selsta part-time monero development (3 months)
+title: selsta part-time monero development (3 months) (7)
 author: selsta
 date: 5 November 2022
 amount: 135
@@ -44,7 +44,7 @@ selsta, I have been contributing to monero since around 2018 with over 595 merge
 
 - CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
 - GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
-- Previous CCS: https://ccs.getmonero.org/proposals/selsta-6.html
+- Previous CCS: https://ccs.getmonero.org/proposals/selsta-6p.html
 
 If funded I will provide monthly updates in the CCS comment section.
 

selsta-8.md → selsta-8p.md

 ---
 layout: cp
-title: selsta part-time monero development (3 months)
+title: selsta part-time monero development (3 months) (8)
 author: selsta
 date: 28 January 2023
 amount: 102
@@ -44,7 +44,7 @@ selsta, I have been contributing to monero since around 2018 with over 615 merge
 
 - CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
 - GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
-- Previous CCS: https://ccs.getmonero.org/proposals/selsta-7.html
+- Previous CCS: https://ccs.getmonero.org/proposals/selsta-7p.html
 
 If funded I will provide monthly updates in the CCS comment section.
 

selsta-9.md → selsta-9p.md

 ---
 layout: cp
-title: selsta part-time monero development (3 months)
+title: selsta part-time monero development (3 months) (9)
 author: selsta
 date: 1 May 2023
 amount: 117
@@ -44,7 +44,7 @@ selsta, I have been contributing to monero since around 2018 with over 628 merge
 
 - CLI contributions: https://github.com/monero-project/monero/pulls?q=is%3Apr+author%3Aselsta
 - GUI contributions: https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+author%3Aselsta
-- Previous CCS: https://ccs.getmonero.org/proposals/selsta-8.html
+- Previous CCS: https://ccs.getmonero.org/proposals/selsta-8p.html
 
 If funded I will provide monthly updates in the CCS comment section.
 

spirobel_robust_modular_wallet_rpc.md

+---
+layout: cp
+title: Robust and modular wallet-rpc library
+date: Sep 10, 2024
+author: Spirobel
+amount: 100
+milestones:
+  - name: Deved + prepayment for first month
+    funds: 20 XMR
+    done: 9 October 2024
+    status: finished
+  - name: First month
+    funds: 30 XMR
+    done: 23 December 2024
+    status: finished
+  - name: Second month + value commitment
+    funds: 50 XMR
+    done: 19 February 2025
+    status: finished
+payouts:
+  - date: 16 October 2024
+    amount: 20
+  - date: 28 February 2025
+    amount: 80
+---
+
+# Robust and modular wallet-rpc library
+
+## Who
+
+**Spirobel**
+
+References:
+
+#### found and reported a "pay what you want" vulnerability in AcceptXMR
+
+https://x.com/spirobel/status/1672479215512588288
+
+https://github.com/busyboredom/acceptxmr/issues/64
+
+#### open sourced a Patreon like tool for Monero
+
+https://x.com/spirobel/status/1595949928634667008
+
+https://github.com/spirobel/monero-discourse-subscriptions
+
+#### open sourced a merchant focused wallet-rpc
+
+https://x.com/spirobel/status/1596299822516285440
+
+https://github.com/spirobel/monerochan-merchant-rpc
+
+
+#### implemented a Monero Browser wallet extension
+
+https://www.youtube.com/watch?app=desktop&v=4DLcsQ45zoE
+
+Contact: twitter.com/spirobel
+
+## What
+
+Result: A robust and modular wallet-rpc library, implemented in Rust with WebAssembly (WASM) as the primary target. This library aims to provide a flexible foundation for Monero wallet functionality. The deliverable for this proposal will be:
+
+1. the first part of the wallet-rpc library that can sync transactions and works reliably with remote nodes.
+2. A checkout flow built with this library. This is meant to be used, not just to demonstrate the features.
+3. Detailed documentation for the library, the relationship between nodes and wallets during the syncing process and a guide on how to use this to implement monero payment gateways.
+
+### Implementation
+
+list of initial tasks:
+
+- create function to turn address and private viewkey into viewpair
+- create function to scan transaction with sub functions
+- verify that there is no timelock present
+- calculate transaction amount
+- clarify responsibility of burning bug prevention for the caller
+
+- implement transaction fetching and storage
+- implement burning bug prevention in the checkout flow
+- write unit tests, document and publish the library
+- implement UI for the checkout flow
+
+this task list is not exhaustive and subject to change
+
+## Why
+
+As discussed as far back as two years ago: https://github.com/seraphis-migration/strategy/issues/2
+The wallet2 Monero library is a 15k lines CPP file. The official monero repo does not contain a deliverable that is easily linkable from other programs. Every project that is a wallet or contains wallet-like functionality (payment processors, hardware wallets, point of sale terminals) needs to implement its own wrapper to expose a C ABI.
+
+This results in collectively wasted hours and headaches. It increases supply chain risk and makes building things with Monero harder. As a result, projects get more expensive, take longer or don't happen at all.
+
+This library aims to counteract the issues and limitations of wallet2.cpp by directly targeting wasm.
+Using wasm as the main target means that this library is forced to be implemented in a way that meets the expectations outlined here: https://github.com/seraphis-migration/strategy/issues/1
+
+The benefits of this approach:
+
+### 1. It will be easily linkable
+
+WASM is a very constrained target. There is no garbage collection and multi threading. Getting code to run there means having to write it in a way that is easy to interact with from any language and in any environment.
+
+### 2. It will be more robust
+
+The current monero wallet-rpc is at times unresponsive, because its concurrency mixes the responses of the local rpc with the network interacting with the node. More details in the [monero-playground repository](https://github.com/spirobel/monero-playground). The WASM target constraints ensure that this library decouples the concurrency and networking from the wallet code. The result will be more robust.
+
+### 3. It will be more flexible and not tied to any platform / target
+
+Wallet code deals with the most sensitive data. It should not have unnecessary dependencies or bloat. To give a practical example: monero currently vendors a 4000 lines of code [logging library](https://github.com/monero-project/monero/blob/master/external/easylogging%2B%2B/easylogging%2B%2B.cc) that introduces a dependency on signals. The WASM target constraint means that things like that can't and wont be introduced into this library.
+
+## Milestones and Timeline
+
+value commitment:
+
+The 3 deliverables outlined in the **What** section are the promised outcome of this proposal. Any time left over from the time commitment will be used to further advance the road map. The value commitment is due for the milestone of the second month.
+
+time commitment:
+
+- 100 hours per month for two months (100 hours total)
+- Compensation: 50 XMR per month (100 XMR total)
+- Total compensation: 100 XMR
+
+## Future Roadmap
+
+The next step on the road map is to add transaction building and signing functionality to the library and migrate [the browser wallet](https://www.youtube.com/watch?v=4DLcsQ45zoE) to it.
+
+My endgame is to **remove all friction from the privacy enabled web shopping experience**. Currently most **Monero shoppers** have to copy and paste addresses from the tor browser into their wallets. This opens the door to unnecessary opsec failures, as it is easy to get confused and intimidated by long strings of random numbers.
+
+**A core part of staying private and safe online is to compartmentalize identities.** Qubes OS made some advancements in improving the UX of this activity by coloring different windows that are tied to different identities in a unique way.
+
+The reality is, that installing a different operating system is a large ask for the average person. At the same time we need to onboard as many people as possible to these habits, so we can operate safely in the crowd.
+
+The other venue of attack is **using the browser for compartimentalization.** And before anybody complains: no this does not involve untrusted javascript frontend code.
+
+There is a big difference between a browser wallet and web wallet. A web wallet is a flawed experiment that is borderline custodial, as it runs wallet code inside the context of a website. This is not to be confused with a browser wallet.
+**A browser wallet runs trusted code as a compartmentalized, constrained program inside of a sandbox.**
+
+There is a massive opportunity here to reduce friction by making it easy to separate online identities. The TOR browser currently enables the use of one separate TOR circuit for each tab. **Imagine we have one monero address per tab that is used for login and to send and receive payments.** It makes it much harder to mess up.
+
+One last concern that comes up is that there might be zero day exploits in the browser, as it exposes a potentially larger attack surface. This can be mitigated by making the wallet a multisignature wallet and **using a second device like an android phone or a monero seedsigner to authorize every transaction.**
+This means two devices need to be compromised to capture funds, which is unlikely.

staff91-Translation and review of GUI Wallet, monero-site, Monero Means Money (subtitles) and Sound Money, Safe Mode (subtitles) to Italian.md

 ---
-layout: wip
+layout: cp
 title: Translation and review of GUI Wallet, monero-site, Monero Means Money (subtitles) and Sound Money, Safe Mode (subtitles) to Italian.
 author: staff91
 date: November 18, 2020
@@ -20,6 +20,12 @@ payouts:
     amount:
 ---
 
+## Proposal Closure
+
+The remaining funds (28 XMR) have been donated to the General Fund.
+
+---
+
 # About this Proposal
 
 Translation and review of the [GUI Wallet](https://translate.getmonero.org/projects/monero/gui-wallet/), [monero-site](https://translate.getmonero.org/projects/getmonero/monero-site/), [Monero Means Money (subtitles)](https://translate.getmonero.org/projects/community/monero-means-money/) and [Sound Money, Safe Mode (subtitles)](https://translate.getmonero.org/projects/community/sound-money-safe-mode-subtitles/) to Italian.

syntheticbird_cuprate_arti_2_months.md

+---
+layout: wip
+title: SyntheticBird Cuprate Arti integration and development (2 months)
+author: SyntheticBird
+date: March 9, 2025
+amount: 52.5
+milestones:
+  - name: April
+    funds: 50% (26 XMR)
+    done:
+    status: unfinished
+  - name: May and completion of Arti integration
+    funds: 50% (26.5 XMR)
+    done:
+    status: unfinished
+payouts:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+# Who
+
+I am [SyntheticBird](https://github.com/SyntheticBird45), Cuprate contributor.
+
+# What
+
+Cuprate is currently in alpha version and a lot of features are planned on the roadmap up to beta phase. One of the features present on this roadmap, and that was [originally presented when announcing Cuprate](https://github.com/Cuprate/cuprate/blob/fc9b077d946fe8b7746c45ae8b299a87b2014cbf/readme.md?plain=1#L57), is native support for Tor network. This CCS proposal intend to fulfill this milestone.
+
+I will work for an estimated 2 months, from April to end of May, on Cuprate with the goal of implementing native Tor support into `cuprated` through the `arti-client` crate and other miscellaneous improvements.
+At the end of this CCS, testers will be able to:
+- Bootstrap Tor network within Cuprate or use Tor system daemon.
+- Use Tor for outbound clearnet connections.
+- Natively connect to onion monero nodes.
+- Generate an onion service for accepting inbound Tor connections.
+
+# Tasks
+
+The planned set of tasks to complete can be found at this Github gist: https://gist.github.com/SyntheticBird45/4c554d3c1e7ae6f8d237d7dd49c2d2f0
+
+It is subject to change but overall the required work can be separated into 3 categories:
+
+### 1. Alternative network integration into P2P components.
+
+Currently, Some P2P components have limited support for alternative network rules. This will require modifying `AddressBook`, `Connector`, `HandshakeBuilder`, `cuprate-dandelion` crate and `cuprated`'s dandelion implementation, and others to be *anonymization-network-aware*. After this work, we will define a new `NetworkZone` called `Tor` to connect to onion monero nodes.
+
+### 2. Implementation of Arti and Tor Daemon support
+
+Implementing `arti-client` inside `cuprated` and `cuprate-p2p{-*}`. Configurations, initialization, bootstrapping and launching onion services if requested. System tor daemon will also be supported.
+
+### 3. Documentation
+
+Update [Architectural book](https://architecture.cuprate.org) and [User book](https://user.cuprate.org/)
+
+# Additional work
+
+In the event that all guaranteed items are completed before the 2 months, I will spend my remaining time assisting (Issues, PRs and Reviews) on whatever is agreed is highest priority, or working on the following items:
+
+- Custom Allocator support (Performance improvements for Musl based linux distributions and potentially minor improvements on other OSs)
+- SOCKS5 proxy support for p2p
+- Fjall database integration
+- Related documentation
+
+# Milestones
+
+### 1. First month
+
+26 XMR
+
+### 2. Second Month and completion of main tasks
+
+26.5 XMR
+
+# Licensing
+
+All the works completed under this CCS will be delivered to the [`Cuprate/cuprate.git`](https://github.com/Cuprate/cuprate) github repository. This work will follow the current repository licensing:
+- All work inside `/binaries` is licensed under `AGPL-3.0-only`.
+- The rest of the root and crates are licensed under `MIT`.
+
+For more information about the Cuprate github organization, please [visit the organization page](https://github.com/Cuprate)
+
+# Funding
+
+I will be working 30 hours per week during 8 weeks at 45\$/hr - 205\$/XMR.
+30×8=240 | 240×45=10800 | 10800÷205=52.5
+
+Total: 52.5 XMR

tipxmr.live.md

 ---
-layout: wip
+layout: cp
 title: "tipxmr.live - a non-custodial livestream donation service for OBS"
 author: AlexAnarcho and hundehausen
 date: September 16, 2020
@@ -7,25 +7,47 @@ amount: 72
 milestones:
   - name: Milestone 1 - Basic setup of webpack with monero javascript and react
     funds: 2% (1.44 XMR)
-    done:
-    status: unfinished
+    done: 17 March 2022
+    status: completed
   - name: Milestone 2 - Working Prototype with implemented WASM wallet and front-end mockups
     funds: 48% (34.56 XMR)
-    done:
-    status: unfinished
+    done: 21 December 2024
+    status: completed
   - name: Milestone 3 - Finished product and launch of serivce
     funds: 50% (36 XMR)
-    done:
-    status: unfinished
+    done: 21 December 2024
+    status: completed
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 17 March 2022
+    amount: 1.44
+  - date: 12 February 2025
+    amount: 70.56
 ---
 
+## Proposal deprecation / Repurposing of funds (21st Dec, 2024)
+
+AlexAnarcho and hundehausen shared a [candid update](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/524#note_27732) regarding progress of TipXMR. Exerpt below:
+
+>We were young and naive and thought "how hard can it be to code this up" - harder than we thought it turned out.         
+>
+>We had very high standards, trying to use WASM wallets on the client-side where no info is leaked to the hoster of the TipXMR service, but this lead to a high barrier - which in turn lead to us never shipping anything   
+>
+>[...]    
+>
+>We are okay to deprecate the TipXMR CCS proposal and pass our collected funds on to this XMRChat proposal.
+
+The remaining funds from:
+
+* Milestone 2 - Working Prototype with implemented WASM wallet and front-end mockups (34.56XMR)
+* Milestone 3 - Finished product and launch of serivce (36XMR)
+
+Will be rewarded to https://xmrchat.com/ - [source](https://github.com/sa8ab/xmrchat)
+
+Who instead of implementing a WASM wallet to not share view keys with the service host have performed the following tasks deemed to be of the same value/importance:
+
+* Integrated monero-lws to handle multiple streamer view-keys.
+* extra misc. features such as a personal donation page with comments attatched.    
+
 # CCS Proposal: tipxmr.live - a non-custodial livestream donation service for OBS
 
 

tobtoht-2024Q1.md

 ---
-layout: wip
+layout: cp
 title: "tobtoht full-time feather + core development (3 months)"
 author: tobtoht
 date: 1 Jan 2024
@@ -7,17 +7,17 @@ amount: 170
 milestones:
   - name: 240 hours
     funds: 50% (85)
-    done:
-    status: unfinished
+    done: 14 March 2024
+    status: finished
   - name: 240 hours
     funds: 50% (85)
-    done:
-    status: unfinished
+    done: 20 August 2024
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 9 April 2024
+    amount: 85
+  - date: 4 September 2024
+    amount: 85
 ---
 
 ### What

tobtoht-2024Q3.md

+---
+layout: cp
+title: "tobtoht full-time feather + core development (3 months)"
+author: tobtoht
+date: 20 Aug 2024
+amount: 179
+milestones:
+  - name: 240 hours
+    funds: 50% (89.5)
+    done: 8 Octoboer 2024
+    status: finished
+  - name: 240 hours
+    funds: 50% (89.5)
+    done: 20 December 2024
+    status: finished
+payouts:
+  - date: 15 October 2024
+    amount: 89.5
+  - date: 13 January 2025
+    amount: 89.5
+---
+
+### What
+
+- work on issues/ideas reported by users
+- [maintain](https://github.com/feather-wallet/feather/blob/master/MAINTENANCE.md) and [improve](https://featherwallet.org/ideas/) feather
+- upstream useful patches to monero core
+- test and review pull requests (GUI/core)
+- help out where I can
+
+My primary focus for this period will be [reproducible/bootstrappable fcmp++ builds](https://github.com/monero-project/monero/pull/9440) (core) and finishing work on [multisig support](https://github.com/feather-wallet/feather/commit/f944b6e6f78a29abe910b8f1d5d88b7c783553d6) (feather).
+
+### Who
+
+Hi, I'm tobtoht. I am an active contributor to the Monero ecosystem since April 2018. Currently, I maintain Feather Wallet and contribute to the core codebase.
+
+Previous CCS: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/428
+
+### Proposal
+
+Work for 480 hours at a rate of €45/h + 0.05 XMR/h. At €139 / XMR (14 day EMA) this makes 179 XMR.
\ No newline at end of file

v1docq47-monerokon-and-monerotopia-voiceover-and-working-on-xmr.ru.md

@@ -44,6 +44,8 @@ payouts:
     amount: 7.13
 ---
 
+_Note: Overfunding of 0.050719957895 XMR from this proposal has been awarded to [v1docq47 2024](https://ccs.getmonero.org/proposals/v1docq47-monerotopia-2024-voiceovers-and-working-on-xmr.ru.html)_
+
 # Introduction
 
 Due to [disallow on posting new CCS to translate](https://github.com/monero-project/meta/issues/732) on ccs.getmonero.org, I redid [my previous CCS proposal](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/329) and removed the translate part of the work.

v1docq47-monerokon-part-2-and-monerotopia-2023-voice-over-and-working-on-xmr.ru.md

@@ -42,6 +42,8 @@ payouts:
     amount: 21.6
 ---
 
+_Note: Overfunding of 0.008456194953 XMR from this proposal has been awarded to [v1docq47 2024](https://ccs.getmonero.org/proposals/v1docq47-monerotopia-2024-voiceovers-and-working-on-xmr.ru.html)_
+
 # Introduction
 
 Hi, everyone! [v1docq47](https://t.me/v1docq47) is here!

v1docq47-video-creation-and-translations-into-russian-(february-july-2022).md

@@ -44,6 +44,8 @@ payouts:
     amount: 10.5
 ---
 
+_Note: Overfunding of 5.296349910952 XMR from this proposal has been awarded to [v1docq47 2024](https://ccs.getmonero.org/proposals/v1docq47-monerotopia-2024-voiceovers-and-working-on-xmr.ru.html)_
+
 # Introduction
 
 Hello, my dear followers, colleagues, and friends!