selsta-3.md → selsta-3p.md

 ---
 layout: cp
-title: selsta part-time monero development (3 months)
+title: selsta part-time monero development (3 months) (3)
 author: selsta
 date: 7 Oct 2021
 amount: 75
@@ -45,7 +45,7 @@ selsta, I have been contributing to monero since around 2018 with over 470 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-2.html
+- Previous CCS: https://ccs.getmonero.org/proposals/selsta-2p.html
 
 If funded I will provide monthly updates in the CCS comment section.
 

selsta-4.md → selsta-4p.md

 ---
 layout: cp
-title: selsta part-time monero development (3 months)
+title: selsta part-time monero development (3 months) (4)
 author: selsta
 date: 12 Jan 2022
 amount: 95
@@ -45,7 +45,7 @@ selsta, I have been contributing to monero since around 2018 with over 500 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-2.html
+- Previous CCS: https://ccs.getmonero.org/proposals/selsta-3p.html
 
 If funded I will provide monthly updates in the CCS comment section.
 

selsta-5.md → selsta-5p.md

 ---
 layout: cp
-title: selsta part-time monero development (3 months)
+title: selsta part-time monero development (3 months) (5)
 author: selsta
 date: 18 Apr 2022
 amount: 75
@@ -44,7 +44,7 @@ selsta, I have been contributing to monero since around 2018 with over 525 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-4.html
+- Previous CCS: https://ccs.getmonero.org/proposals/selsta-4p.html
 
 If funded I will provide monthly updates in the CCS comment section.
 

selsta-6.md → selsta-6p.md

 ---
 layout: cp
-title: selsta part-time monero development (3 months)
+title: selsta part-time monero development (3 months) (6)
 author: selsta
 date: 30 July 2022
 amount: 110
@@ -44,7 +44,7 @@ selsta, I have been contributing to monero since around 2018 with over 572 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-5.html
+- Previous CCS: https://ccs.getmonero.org/proposals/selsta-5p.html
 
 If funded I will provide monthly updates in the CCS comment section.
 

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: wip
-title: selsta part-time monero development (3 months)
+layout: cp
+title: selsta part-time monero development (3 months) (9)
 author: selsta
 date: 1 May 2023
 amount: 117
@@ -15,15 +15,15 @@ milestones:
     status: finished
   - name: July
     funds: 33% (39 XMR)
-    done:
-    status: unfinished
+    done: 13 August 2023
+    status: finished
 payouts:
   - date: 8 June 2023
     amount: 39
   - date: 6 July 2023
     amount: 39
-  - date:
-    amount:
+  - date: 16 August 2023
+    amount: 39
 ---
 
 ## What
@@ -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.
 

seraphis-ongoing-support.md

@@ -12,6 +12,14 @@ milestones:
 payouts:
 ---
 
+### Deadline update: July 1, 2025
+
+Prior to the deadline, the proposer MUST provide regular updates on their progress as per the CCS rules.
+
+If the provided updates/progress (or lack thereof) is unsatisfactory, all remaining funds **can be** relinquished either before or after the deadline.
+
+The community will then seek another person/team to take over. If this cannot be accomplished within a reasonable timeframe, the funds will be repurposed or reallocated to a similar proposal (subject to community consensus).
+
 ## Intro
 
 Hi all, I [closed out](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/369#note_21022) my previous [Seraphis Library Work 2 CCS](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/369) after consuming all the hours. There are additional tasks I would like to work on. For background on this CCS, please see the links in the previous sentence.

serhack-monero-integrations-part-3.md

@@ -24,6 +24,14 @@ payouts:
     amount:
 ---
 
+### Deadline update: July 1, 2025
+
+Prior to the deadline, the proposer MUST provide regular updates on their progress as per the CCS rules.
+
+If the provided updates/progress (or lack thereof) is unsatisfactory, all remaining funds **can be** relinquished either before or after the deadline.
+
+The community will then seek another person/team to take over. If this cannot be accomplished within a reasonable timeframe, the funds will be repurposed or reallocated to a similar proposal (subject to community consensus).
+
 ### What?
 
 I am [SerHack](https://serhack.me), the author of [Mastering Monero](https://masteringmonero.com) and security engineer; I am one of the maintainers for [Monero integrations](https://monerointegrations.com) project. The project aims to provide a set of payment gateways and libraries (coded mainly in PHP, at the time of writing) for merchants and developers. As you might find on Github, the payment gateways are not in any third party companies, then no data is sent to any other website beside yours.
@@ -67,4 +75,12 @@ I would like to expand more this section since it is a subject close to my heart
 
 ### Costs
 
-If milestones are not modified, I'll ask 11 XMR (~700 euros) - fixed price.  
\ No newline at end of file
+If milestones are not modified, I'll ask 11 XMR (~700 euros) - fixed price.  
+
+### Proposal transfer
+
+This proposal will be transferred to recanman who will enjoy an exclusivity period of 5 months to show reasonable progress in completing this proposal. They will receive payments for completed milestones directly.
+
+SerHack: https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/402#note_22039
+
+>To consider the CCS completed, all the issues mentioned in the CCS must be completed: recanman will need to push changes to monero-integrations repositories and after reviewing the PRs, I'll close the issues.

soloptxmr-mj-endor-2022.md

@@ -42,6 +42,14 @@ payouts:
     amount:
 ---
 
+### Deadline update: July 1, 2025
+
+Prior to the deadline, the proposer MUST provide regular updates on their progress as per the CCS rules.
+
+If the provided updates/progress (or lack thereof) is unsatisfactory, all remaining funds **can be** relinquished either before or after the deadline.
+
+The community will then seek another person/team to take over. If this cannot be accomplished within a reasonable timeframe, the funds will be repurposed or reallocated to a similar proposal (subject to community consensus).
+
 # What
 The goal is to create open-source software that aids people mining Monero with excess solar power in the most profitable way. It will accommodate for issues such as:
 

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: cp
+title: "tobtoht full-time feather + core development (3 months)"
+author: tobtoht
+date: 1 Jan 2024
+amount: 170
+milestones:
+  - name: 240 hours
+    funds: 50% (85)
+    done: 14 March 2024
+    status: finished
+  - name: 240 hours
+    funds: 50% (85)
+    done: 20 August 2024
+    status: finished
+payouts:
+  - date: 9 April 2024
+    amount: 85
+  - date: 4 September 2024
+    amount: 85
+---
+
+### What
+
+- work on issues/ideas reported by users
+- work on tasks listed on the [ideas](https://featherwallet.org/ideas/) page and [MAINTENANCE.md](https://github.com/feather-wallet/feather/blob/master/MAINTENANCE.md)
+- upstream useful patches to monero core
+- test and review pull requests (GUI/core)
+- help out where I can
+
+My primary focus for Q1 2024 is practical multisig UX.
+
+### 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://ccs.getmonero.org/proposals/tobtoht-feather-dev-2023-3.html
+
+### Proposal
+
+Work for 480 hours at a rate of €45/h + 0.05 XMR/h. At €148 / XMR (14 day EMA) this makes 170 XMR.

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

tobtoht-2025Q1.md

+---
+layout: wip
+title: "tobtoht full-time feather + core development (3 months)"
+author: tobtoht
+date: December 20, 2024
+amount: 150
+milestones:
+  - name: 240 hours
+    funds: 50% (75)
+    done: 2 February 2025
+    status: finished
+  - name: 240 hours
+    funds: 50% (75)
+    done:
+    status: unfinished
+payouts:
+  - date: 24 February 2025
+    amount: 75
+  - date:
+    amount:
+---
+
+### 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
+- [help maintain](https://github.com/monero-project/monero/pulls?q=is%3Apr+label%3A%22build+system%22+author%3Atobtoht) monero core's build system and CI
+- test and review pull requests (GUI/core)
+- upstream useful patches to monero core
+- help out where I can
+
+I want to start off the year by clearing out a good chunk of the small-to-medium size issue/feature backlog for Feather. At the same time, making sure [pending build system PRs](https://github.com/monero-project/monero/issues/9631) for Monero core get reviewed and merged, particularly everything we need for FCMP++. 
+
+After that, I want to continue efforts to add multisig support to Feather by evaluating kaya's FROST-inspired multisig implementation as a more robust replacement for wallet2's implementation. A related [audit](https://ccs.getmonero.org/proposals/monero-serai-wallet-audit.html) is expected to conclude in March.
+
+### 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/492
+
+### Proposal
+
+Work for 480 hours at a rate of €50/h + 0.05 XMR/h. At €190 / XMR (14 day EMA) this makes 150 XMR.

tobtoht-feather-dev-2023-1.md

 ---
-layout: wip
+layout: cp
 title: "Continued Feather Wallet development (3 months)"
 author: tobtoht
 date: 15 Feb 2022
@@ -15,15 +15,15 @@ milestones:
     status: finished
   - name: Third month
     funds: 33% (48 XMR)
-    done: 
-    status: unfinished
+    done: 20 July 2023
+    status: finished
 payouts:
   - date: 10 May 2023
     amount: 47
   - date: 9 June 2023
     amount: 47
-  - date:
-    amount:
+  - date: 26 July 2023
+    amount: 48
 ---
 
 This proposal is for 3 months of full time Feather Wallet development.

tobtoht-feather-dev-2023-3.md

+---
+layout: cp
+title: "Continued Feather Wallet development (3 months)"
+author: tobtoht
+date: 20 Jul 2023
+amount: 146
+milestones:
+  - name: First month 
+    funds: 33% (48.6 XMR)
+    done: 19 October 2023
+    status: finished
+  - name: Second month
+    funds: 33% (48.6 XMR)
+    done: 9 December 2023
+    status: finished
+  - name: Third month
+    funds: 33% (48.7 XMR)
+    done: 2 January 2024
+    status: finished
+payouts:
+  - date: 5 November 2023
+    amount: 48.6
+  - date: 5 January 2024
+    amount: 97.3
+---
+
+
+This proposal is for 3 months of full time Feather Wallet development.
+
+### What
+
+- work on issues/ideas reported by users
+- work on tasks listed on the [ideas](https://featherwallet.org/ideas/) page and [MAINTENANCE.md](https://github.com/feather-wallet/feather/blob/master/MAINTENANCE.md)
+- upstream useful patches to monero core
+- test and review pull requests (GUI/core)
+- help out where I can
+
+As always, I heavily prioritize user feedback when deciding what to focus on.
+
+### 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/376
+
+Progress updates are posted to #feather:monero.social and /r/FeatherWallet.
+
+### Proposal:
+
+Work for 40 hours per week for the next 3 months at a rate of €45/h. At €148 / XMR (14 day EMA) this makes 146 XMR.

utxobr-monero-k8s-operator.md

 ---
-layout: wip
+layout: cp
 title: Monero Kubernetes Operator
 author: Ciro S. Costa (utxobr)
 date: May 3, 2021
@@ -30,6 +30,9 @@ payouts:
     amount:
 ---
 
+## Proposal closure / Repurposing of funds (1st Jan, 2025)
+
+All remaining funds (22.86XMR) will be repurposed or reallocated to a similar proposal (subject to community consensus).
 
 ## Brief Intro