ofrnxmr-totw3.md

+---
+layout: wip
+title: ofrnxmr support, docs, site, meta++ (totw pt3)
+author: ofrnxmr
+date: July 31, 2024
+amount: 168
+milestones:
+  - name: Aug 2024
+    funds: 14 XMR
+    done: 23 September 2024
+    status: finished
+  - name: Sep 2024
+    funds: 14 XMR
+    done: 31 January 2025
+    status: finished
+  - name: Oct 2024
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Nov 2024
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Dec 2024
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Jan 2025
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Feb 2025
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Mar 2025
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Apr 2025
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: May 2025
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Jun 2025
+    funds: 14 XMR
+    done:
+    status: unfinished
+  - name: Jul 2025
+    funds: 14 XMR
+    done:
+payouts:
+  - date: 28 September 2024
+    amount: 14
+  - date: 25 February 2025
+    amount: 14
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+Welcome back. Hopefully I still have your ear.
+
+I'd like to take a moment to express gratitude towards all of my anonymous supporters. I see you, and I thank you for everything you've helped me with thus far. I wouldn't be here without you. If this proposal is merged, I will likely be good through til 2026.
+
+This may not seem as abnormal as I'd have liked. The title is what it is, but the proposal is intended to cover contributions to Monero proper. It was requested that I open a new MR instead of editing the [old one](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/444).
+
+- 14xmr/mth includes 20-25hrs/wk on customer support, docs, site, ccs, assisting devs, and attempting to take over the world:
+  - 3xmr/mth work with core devs, community devs, researchers, and other contributors to test or advise on features, issues, community projects etc.
+  - 3xmr/mth #monero-support: Lead the support channel & provide hands on support to users
+  - 3xmr/mth #monero-docs: Maintain¹ (or help to maintain) monero-docs repo and/or assist plowsof, 321bob321 and others with content
+  - 2xmr/mth #monero-site: Maintain¹ (or help to maintain) monero-site repo and/or assist plowsof, hardenedsteel and others with content
+  - 2xmr/mth #monero-community: Assisting CCS proposers (and plowsof) with relations/logistics
+  - 1xmr/mth take over the world: dedicate time to dealing with "meta" stuff. There is quite a bit of unfinished business (on and off repo) that needs to be tackled
+  - donate to others
+
+The above amounts are estimates. Actual distribution may vary.
+
+¹ Maintain = handle merges
+
+Terms:
+- 12 Months @ 168xmr total
+- Estimated 20-25 hr/wk
+
+Rate:
+- 1 XMR = 1 XMR
+
+Payout structure: 
+- 12 monthly milestones
\ No newline at end of file

ofrnxmr_basicswap.md

+---
+layout: wip
+title: "ofrnxmr feat BasicSwapDEX - take over the world pt 2"
+author: ofrnxmr
+date: 12 August 2024
+amount: 1685
+milestones: 
+  - name: M0-O (ofnxmr, 1st month)
+    funds: 20 XMR
+    done: 3 September 2024
+    status: finished
+  - name: M0-Y (80xmr bounties, 3 months)
+    funds: 80 XMR
+    done: 28 September 2024
+    status: finished
+  - name: M0-F (~0-160hrs, 1st month)
+    funds: 40 XMR
+    done: 4 September 2024
+    status: finished
+  - name: M0-B (~0-160hrs, 1st month)
+    funds: 55 XMR
+    done: 4 September 2024
+    status: finished
+  - name: M1-O (ofrnxmr, 2nd month)
+    funds: 20 XMR
+    done: 17 October 2024
+    status: finished
+  - name: M1-F (~160-320hrs, 2nd month)
+    funds: 40 XMR
+    done: 17 October 2024
+    status: finished
+  - name: M1-B (~160-320hrs, 2nd month)
+    funds: 55 XMR
+    done: 17 October 2024
+    status: finished
+  - name: M2-O (ofrnxmr, 3rd month)
+    funds: 20 XMR
+    done: 30 November 2024
+    status: finished
+  - name: M2-F (~320-480hrs, 3rd month)
+    funds: 40 XMR
+    done: 30 November 2024
+    status: finished
+  - name: M2-B (~320-480hrs, 3rd month)
+    funds: 55 XMR
+    done: 30 November 2024
+    status: finished
+  - name: M3-O (ofrnxmr, til completion)
+    funds: 100 XMR
+    done:
+    status: unfinished
+  - name: M3-F - Frontend GUI v3.0.0 - v5.0.0+ (prepaid, ~6 months)
+    funds: 320 XMR
+    done: 19 January 2025
+    status: finished
+  - name: M3-B - Backend v0.13 - v0.15+ (prepaid, ~6 months)
+    funds: 410 XMR
+    done: 19 January 2025
+    status: finished
+  - name: M4 - Delivery of 1.0 (postpaid, ~3 months)
+    funds: 190 XMR
+    done:
+    status: unfinished
+    milestones: 
+  - name: M5 - 1yr maintenance (ongoing)
+    funds: 240 XMR
+    done:
+    status: unfinished
+payouts:
+  - date: 14 September 2024
+    amount: 115
+  - date: 28 September 2024
+    amount: 80
+  - date: 23 October 2024
+    amount: 115
+  - date: 6 December 2024
+    amount: 115
+  - date: 6 February 2025
+    amount: 730
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+Welcome ladies and gentleman, kids and pets.
+
+Lets skip the intro.
+
+  BasicSwapDEX is, as far as I know, Monero's only Bidirectional Atomic swap service, and the only one that allows swapping monero with coins not named Bitcoin (such as Litecoin). 
+
+  BasicSwapDEX has been mainnet for a while now, but is a beta / POC. With this CCS I hope empower and steward BasicSwapDex to production quality software within ~1 year. Some milestones are to be paid to ofrnxmr in advance. I'm also requesting that some funds be escrowed by the CCS Coordinator.
+	 
+##### M0/M1/M2 = accelerate work / probation.
+- M0 paid at funding. To be paid to ofrnxmr to distribute as follows:
+  - M0 = 80xmr to ofrnxmr to pay for bounties / extra help, and/or bonuses to backend/frontend devs
+  - M0/M1/M2 = 20xmr/month (60xmr/3months) to ofrnxmr
+  - M0/M1/M2 = 40xmr/160hrs (120xmr/3mths) to BasicSwap Team - Frontend
+  - M0/M1/M2 = 55xmr/160hrs (165xmr/3mths) to BasicSwap Team - Backend
+
+##### M3-O - Paid end of month 4
+  - 100xmr
+    
+##### M3-F - Frontend GUI v3.0.0 - v5.0.0+
+- Paid start of month 4
+  - 240xmr earmarked for frontend development (paid out by ofrnxmr as work is completed, 40xmr/160hr)
+  - 80xmr to ofrnxmr to pay for bounties / extra help, and/or bonuses to frontend devs
+
+##### M3-B - Backend v0.13 - v0.15+
+- Paid start of month 4
+  - 330xmr earmarked for backend development (paid out by ofrnxmr as work is completed: 55xmr/160hr)
+  - 80xmr to ofrnxmr to pay for bounties / extra help, and/or bonuses to backend devs
+
+##### M4 - Delivery of 1.0
+- Paid after M3 is completed to satisfaction, and 1.0 is shipped 
+  - 80xmr for frontend dev(s)
+  - 110xmr for backend dev(s)
+
+##### M5 = Maintenance
+- Payout in Month 13 at the earliest, to be redistributed on a monthly basis 
+  - 8xmr to backend devs
+  - 8xmr to frontend devs
+  - 4xmr to ofrnxmr
+
+#### Scope (wherever technically possibly)
+- **_M0/M1/M2 = Catchup work. Begin preparing for M3 milestones._**
+  - [Some things yet to be completed](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/457#note_24394)
+- **_M3-F - Frontend GUI v3.0.0 - v5.0.0+_**
+  - CEX-like UI and UX (aside from speed)
+    - Orderbook
+    - Market depth
+    - Order types ie. Market, limit, stop, trailing, profit taker
+  - Private orderbook UI
+  - Overall UI and UX updates
+    - Mobile friendly
+    - Better notifications
+    - Improve / simplify in progress and historical bid details
+  - Historical swap exports
+  - Drop _reliance_ on centralized price APIs
+  - Add wallet (rpc) functionality to the wallets themselves
+  - Ability to use external wallets to take offers
+  - Include new GUI interfaces to match new backend functionalities
+- **_M3-B - Backend v0.13 - v0.15+_**
+  - Secure the backend
+  - Better code reviews
+  - Fix and enhance user APIs
+  - Add provider / swapper APIs
+  - Web frontend APIs
+  - Enable swaps between incompatible coins. [Example: XMR <> FIRO]
+  - Integrations of atomic protocals such as those from BCH and ETH
+  - Disconnect SMSG from Particl blockchain
+  - Create and use a local price oracle
+  - Bridge orderbooks from other services such as Samourai 
+  - EVM wallet compatibility
+  - Necessary changes to enable frontend features
+- **_M4 - Delivery of 1.0_**
+  - M3-X Completed to satisfaction
+  - Ship 1.0 installation packages as (example), a Flatpak, appimage
+- **_M5 - 1yr Maintenance_**
+  - Addressing concerns in an efficient manner
+  - Continued improvement of the codebase
+
+The scope of work is quite large. You can follow Particl dev report (going back to January) for current, ongoing and planned work, which is ever evolving.
+
+Should any part of this CCS fail, I may choose to redirect remaining funds to fork the project or to acquire devs willing/able to complete it.
+
+In the event of total failure, all unused funds will be donated to a 2/3 multisig (The elusive "jetfund") with the COMMUNITY Coordinator and 1 other [TBD] party, to be used **as the community decides**....Though, im ofrnxmr. I'm not _fill in name of scammer_. I will see this through to completion.
+
+##### Coverage
+- M0/M1/M2 = Month 0-3
+- M3-O = Month 4-12
+- M3-X = Month 4 'til Completion of M3-X milestones (target = ~6 months)
+- M4 = Completion of M3-X milestones til the later of completion of M4 or Month 13
+- M5 = 12 Months. Earliest payouts may begin is the later of completion of M4 or Month 13
+
+**This CCS allows the Monero Community to lead the space to a goal of having a FOSS, trustless, unregulatable, P2P, decentralized, liquid economy, with _0 platform fees, 0 dev taxes_ and _0 targets_.**
+
+**I would hope (and assume) that non-monero communities who are under constant threat for having cypherpunk ideals (_cough_ BTC, BCH, ETH, and whoever else shares our ideals) will also support and donate to this endeavor.**

oneiric-kovri-june-aug-2018.md

+---
+layout: cp
+title: "oneiric: June-August part-time Kovri junior developer"
+author: oneiric
+date: June 7, 2018
+amount: 21
+milestones:
+  - name: Milestone 1 - 1st 16h
+    funds: 13.33% (3.6 XMR)
+    done:
+    status: finished
+  - name: Milestone 2 - 2nd 16h
+    funds: 13.33% (3.6 XMR)
+    done:
+    status: finished
+  - name: Milestone 3 - 3rd 16h
+    funds: 13.33% (3.6 XMR)
+    done:
+    status: finished
+  - name: Milestone 4 - 4th 16h (higher rate)
+    funds: 30% (8.1 XMR)
+    done:
+    status: finished
+  - name: Milestone 5 - 5th 16h (higher rate)
+    funds: 30% (8.1 XMR)
+    done:
+    status: finished
+payouts:
+  - date: September 6, 2018
+    amount: 10.8 XMR
+  - date: December 7, 2018
+    amount: 16.2 XMR
+---
+Who
+Hello Monero community, I'm oneiric, and I've been working on Kovri since December 2017.
+
+This is my first FFS proposal to the community, and I intend to make many more (if the community will have me). I'm in it for the long haul. Privacy is incredibly important to me, and I want to do everything I can to help Kovri and Monero. These projects are some of the strongest tools the common person will have in achieving freedom and financial privacy.
+
+What
+I am submitting this proposal to continue work with anonimal on bringing Kovri to release and integration, and to be funded as a part-time junior developer.
+
+Contributions:
+
+Over the past few months, I have collaborated with anonimal, rehrar, and others to make contributions to Kovri.
+
+Identity: use Boost DateTime when creating router keys: replace sprintf and C date functions with Boost DateTime when creating router keys
+Build: fix mingw warnings: resolve Windows compiler warnings
+Configuration::ListParameter unit-tests: unit-tests for class used to parse Kovri configuration
+SSU: support IP address size for peer test packets: get and set IP address size for SSU peertest packets
+Build: fix Doxygen build: small CMake fix for building Doxygen documentation
+AddressBook: Container for host-address entry: first attempt at a container class for an AddressBook hostname-address pair
+AddressBook + HTTP Proxy: store only unique subscription addresses
+AddressBook: add address to file I/O refactor + add exception handling: change how addresses are added to storage, and throw on filesystem errors
+HTTPMessage: refactor jump service parser + add test-cases: change how the HTTP proxy handle jump service requests, and add unit-tests. One of my first contributions, and required a large amount of collaboration with anonimal (many thanks).
+IdentityEx: lowerbounds check on buffer creation: bounds check on the supplied buffer, ensure it is large enough to hold a serialized IdentityEx class
+Standing on the shoulders of giants:
+
+Assistant for Kovri Project Management
+Create End-User Kovri documentation
+rehrar's 2018 Q1 Kovri proposal
+anonimal's Kovri Full Time Development funding thread
+Proposal for Kovri Dev
+MILESTONES & PROPOSAL
+Milestones
+In collaboration with anonimal:
+
+Create an enhanced form of the Kovri testnet
+Integrate Kovri testnet with live tests
+Write tests for 100% coverage on new and existing stable code
+Remaining 0.1.0-alpha release milestones
+Other tasks anonimal assigns
+Compensation & Time Estimates
+Amount: 27 XMR (0.225 XMR/hour * 40 hours + 0.45 XMR/hour * 40 hours)
+
+The amount I am requesting is based on similar FFS proposals, and average base-pay for a junior developer.
+
+In order for the community to get to know my work, I am willing to give a discounted (50%) rate for the first 40 hours (1 month @ 10 hours/week) of paid work.
+
+The goal is to complete the milestones by DefCon 26, whatever it takes.
+
+Any time more than 10 hours/week, I will volunteer to achieve the stated goals.
+
+To get an idea of my dedication to accomplishing these goals, average time spent on Kovri in April-May was ~50-60 hours/week.
+
+Let's Discuss
+I am new to the project and community, and welcome feedback on this proposal.
\ No newline at end of file

plowsof-ccs-coordinator-2.md

+---
+layout: cp
+title: "CCS Coordinator"
+author: plowsof
+date: April 20th 2023
+amount: 69
+milestones:
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 27 June 2023
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 20 August 2023
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 16 October 2023
+    status: finished
+payouts:
+  - date: 19 July 2023
+    amount: 23
+  - date: 12 September 2023
+    amount: 23
+  - date: 3 November 2023
+    amount: 23
+---
+
+# Who?
+
+Hello, plowsof here, I show up and try to be helpful. My [previous proposal](https://ccs.getmonero.org/proposals/plowsof-com-rel.html) happened, 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).
+    - It has recently came to my attention that there is a seldom enforced CCS rule where "If it's not funded or finished by a certain time, the funds can be released to other proposals or the General Fund.. This keeps things moving along in a timely fashion.", one of my tasks will be to gather support for enforcing this rule where applicable.
+- 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.
+
+# Funding
+
+20hr/week - 40 eur/hr with XMR at 145EUR (MA20 @ Kraken) gives 72 but i like 69 better so 23 XMR/milestone bringing the total requested amount to 69XMR. Maximum of 1 milestone can be claimed per month. Price fluctuation after moving to funding will have no effect.
+Consider this proposal expired in the event of my untimely death / unheard of for >5 months / have not claimed all payouts in 12 months. If expired - all remaining unclaimed funds are to be donated to other CCS proposals.

plowsof-ccs-coordinator-3.md

+---
+layout: cp
+title: "CCS Coordinator"
+author: plowsof
+date: October  20th 2023
+amount: 69
+milestones:
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 14 January 2024
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 14 January 2024
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 17 March 2024
+    status: finished
+payouts:
+  - date: 28 January 2024
+    amount: 46
+  - date: 16 April 2024
+    amount: 23
+---
+
+# 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, 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.
+
+# Funding
+
+20hr/week - 40 eur/hr with XMR at 144EUR (MA20 @ Kraken) gives 72.420 but i like 69 better so 23 XMR/milestone bringing the total requested amount to 69XMR. Maximum of 1 milestone can be claimed per month. Price fluctuation after moving to funding will have no effect.
+Consider this proposal expired in the event of my untimely death / unheard of for >5 months / have not claimed all payouts in 12 months. If expired - all remaining unclaimed funds are to be donated to other CCS proposals.

plowsof-ccs-coordinator-4.md

+---
+layout: cp
+title: "CCS Coordinator"
+author: plowsof
+date: March 29th 2024
+amount: 80.07
+milestones:
+  - name: 2 meetings + hours worked
+    funds: 26.69 XMR
+    done: 2 June 2024
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 26.69 XMR
+    done: 2 June 2024
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 26.69 XMR
+    done: 5 September 2024
+    status: finished
+payouts:
+  - date: 24 June 2024
+    amount: 26.69
+  - date: 24 June 2024
+    amount: 26.69
+  - date: 28 September 2024
+    amount: 26.69
+---
+
+# 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), 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
+
+20hr/week - 40 eur/hr with XMR at 126EUR (MA20 @ Kraken) gives 20 * 13 * (40/126) = 80.5 but i like 80.07 better so 26.69 XMR/milestone bringing the total requested amount to 80.07XMR. Maximum of 1 milestone can be claimed per month. Price fluctuation after moving to funding will have no effect.
+Consider this proposal expired in the event of my untimely death / unheard of for >5 months / have not claimed all payouts in 12 months. If expired - all remaining unclaimed funds are to be donated to other CCS proposals.

plowsof-com-rel.md

+---
+layout: cp
+title: "CCS Coordinator (3 months)"
+author: plowsof
+date: 29 October 2022
+amount: 69
+milestones:
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 31 December 2022
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 31 January 2023
+    status: finished
+  - name: 2 meetings + hours worked
+    funds: 23 XMR
+    done: 11 March 2023
+    status: finished
+payouts:
+  - date: 4 January 2023
+    amount: 23
+  - date: 2 February 2023
+    amount: 23
+  - date: 23 March 2023
+    amount: 23
+---
+
+# 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).
+    - It has recently came to my attention that there is a seldom enforced CCS rule where "If it's not funded or finished by a certain time, the funds can be released to other proposals or the General Fund.. This keeps things moving along in a timely fashion.", one of my tasks will be to gather support for enforcing this rule where applicable.
+- 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.
+
+# Who?
+
+I voluntarily took on this role for a few weeks (several months ago) and detailed my progress [here](https://www.reddit.com/r/Monero/comments/uj0lyu/what_i_did_last_week_plowsof/). Soon after, I 'retired'. Since then, i've been doing this role at half capacity. A member of Core has seen value in my contributions and asked me to make this CCS and also provide some other work around the ecosystem which i would be unable to do consistently without being sponsored by the community. 
+
+My other contributions include:
+
+- Monero GUI Packager - from v0.18.1.0 every GUI installer for windows is packaged by one of my scripts. I've also automated the creation of the .zip and .tar.bz2 files for selsta, so instead of 'copy and pasting files' they can focus on important tasks for release. A public version to create the installer is [here](https://github.com/plowsof/monero-gui-exe)
+- Merged PR's in (a really minor bug fix)[Monero GUI](https://github.com/monero-project/monero-gui/pulls?q=is%3Apr+is%3Amerged+author%3Aplowsof) and [Monero Site]( https://github.com/monero-project/monero-site/pulls?q=is%3Apr+is%3Amerged+author%3Aplowsof+)
+- Self-hosted wishlists, examples at [monerujo](https://funding.monerujo.app/) [monerochan.art](https://www.monerochan.art/) and [XMR.radio](https://xmr.radio/)
+later on i created a multi-coin version. examples at [Rucknium.me](https://rucknium.me/donate/) and [ofrnxmr](https://getwishlisted.xyz/ofrnxmr/)
+- General Fund twitter bot, that tweets every donation received https://nitter.it/watchfund
+- Daily updated list of public ZMQ servers [here](https://github.com/plowsof/listen_for_zmq/blob/main/zmq_list.md) for [xmrvsbeast](https://xmrvsbeast.com/p2pool/monero_nodes.html)
+- [monerodevs.org](http://www.monerodevs.org/) - 'handmade feel' to put it nicely, also needs updating.
+- Set up [MoneroResearch.info](https://moneroresearch.info/) with Rucknium
+- I provide tech support / post PSA's when needed on Reddit at https://www.reddit.com/user/KnowledgeMurky9635 
+
+# Milestones
+Some concrete areas to be judged on will be my ability to obtain decisions (yes / no / change this) from the community in 1 month or less by organising at least 2 meetings per month and gathering feedback.    
+Monthly reports will detail what i've been doing in terms of checking up on the WIP list / working with people at the ideas stage / helping where i am able to.    
+As for the liaising with Core part, if at any point they are not satisfied, then this proposal can be terminated with immediate effect (no payout for 'work done' either)
+
+# Funding
+20hr/week - 40 eur/hr with XMR at 147EUR (MA20 @ Kraken) gives 23 XMR/milestone bringing the total requested amount to 69XMR. Maximum of 1 milestone can be claimed per month. Price fluctuation after moving to funding will have no effect.
+Consider this proposal expired in the event of my untimely death / unheard of for >5 months / have not claimed all payouts in 12 months. If expired - all remaining unclaimed funds are to be donated to other CCS proposals.

plowsof_6_ccs_coordinator.md

+---
+layout: wip
+title: plowsof CCS Coordinator 
+author: plowsof
+date: April 1, 2025
+amount: 72.60
+milestones:
+  - name: Month 1
+    funds: 24.2
+    status: unfinished
+    done:
+  - name: Month 2
+    funds: 24.2
+    status: unfinished
+    done:
+  - name: Month 3
+    funds: 24.2
+    status: unfinished
+    done:
+payouts:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+# 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) [again](https://ccs.getmonero.org/proposals/ccs-coordinator-5-plowsof.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)
+
+
+## Proposal
+Work for 25 hours per week over the next 3 months (from April to end of June 2025) at a rate of 45€ / hour. At 201.72€ / XMR (90-day EMA) this makes ~72.60 XMR.

pwrcycle-Defcon_Monero_Party_2019.md

+---
+layout: cp
+title: "Defcon Monero Party 2019"
+author: pwrcycle
+date: March 11, 2019
+amount: 57
+milestones:
+  - name: Prepare to throw the party
+    funds: 57
+    done: June 19, 2019
+    status: finished
+payouts:
+  - date: June 19, 2019
+    amount: 57 XMR
+
+---
+### Proposal ###
+This proposal is to throw another Monero Party on Augutst 10th, 2019, Saturday night at Defcon 27 in Las Vegas, Nevada, USA. 
+I have an agreement with a club at a Defcon hotel where we will provide DJs for the night and anyone with a Defcon Badge or Monero Badge gets in free +1 guest.
+
+### Importance to the Monero Community ###
+
+Defcon is a hacker convention which promotes the principles of privacy and open source, which align with the Monero project. Exposing hackers to Monero is an excellent opportunity to gain real users and developers to the project. The party gives the opportunity for contributers to the project and the village an opportunity to interact with Defcon attendees outside the official bounds of the con.
+In 2017 there was a small gathering funded by Defcon attendees in a small suite.
+In 2018 there was an official Monero Village at Defcon and a larger suite party.
+
+The funds would go toward:
+1. Hiring DJ (DJs from the hacker community bring more hackers to the event) $1500 ($300/DJ)
+2. Creating Monero medallions, (as we have done the past 2 years #BadgeLife) $800 ($8.00/Medallion)
+3. Glowsticks, candy, party trinkets, signs, stickets, etc. $500
+4. Drinks (anything money not spent will be used to buy drinks to be given to Monero Badge holders) $200
+
+Links:
+2017 Announcement: https://np.reddit.com/r/Monero/comments/6mmebi/defcon_monero_party/
+2018 Announcement: https://www.reddit.com/r/Monero/comments/8v2lz2/defcon_monero_party_2018/
+2019 Question: https://www.reddit.com/r/Monero/comments/azah46/should_we_do_a_defcon_monero_party_again_this_year/
+
+Expiration date: June 1, 2019

r4v3r23-anonero-v1.md

+---
+layout: wip
+title: ANONERO version 1.0
+author: r4v3r23
+date: April 12, 2024
+amount: 199.265
+milestones:
+  - name: Inital payment
+    funds: 20% (39.853 XMR)
+    done: 29 April 2024
+    status: finished
+  - name: Payment for first test build
+    funds: 40 % (79.706 XMR)
+    done: 23 March 2025
+    status: finished
+  - name: Payment for completion
+    funds: 40 % (79.706 XMR)
+    done:
+    status: unfinished
+payouts:
+  - date: 29 April 2024
+    amount: 39.853
+  - date: 3 April 2025
+    amount: 79.706
+  - date:
+    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).
+
+# Who
+
+ANONERO project, creators of the security & privacy focused Monero wallets ANON & NERO.
+
+# What
+
+
+Migrating our codebase to Android's native language Kotlin with Jetpack Compose UI. 
+
+When we first started the project, we bootstrapped development by using a combination of xmrwallet's Java code and Flutter. This allowed for fast interations and great UI performance, but as the app grew with more advanced features, the Native <> Java <> Flutter layers proved to be a bottleneck.
+
+Now that we have a working Proof of Concept alpha wallet, and are much more familiar with the Monero codebase, we've decided to move the app to a new framework that's better suited to our feature set. This will give us a solid, stable codebase and make future developement much easier.
+
+As part of our commitment to privacy & security and using the latest features, ANONERO has contributed to Monero, directly and indirectly, in various ways:
+
+ 1) First fully airgapped DIY HWW cold storage solution: https://monero.town/post/223593
+ 
+ 2) First working implementation of background sync via view-keys
+
+ 3) Helped identify, debug, and fix issue where Polyseed was failing to build on 32-bit Android: https://github.com/tevador/polyseed/issues/5
+
+ 4) Helped identify, debug, and test fix for the DNS leak when using onion nodes: https://github.com/monero-project/monero/pull/8849
+ 
+ 5) Helped discover bug where key images weren't being passed by signed tx payload: https://github.com/monero-project/monero/pull/9049
+ 
+ 6) Discovered background sync bug which caused all cached blocks to be erased: https://github.com/monero-project/monero/pull/8619#issuecomment-1808920063
+ 
+ 7) Helped test tobtoht's upcoming [Polyseed](https://github.com/tevador/polyseed) patch to monero core
+ 
+ 8) Worked with tobtoht to improve offline-signing UX
+ 
+We'll continue to adopt and test new features and upstream fixes to core if/when they arise during the CCS.
+
+# Proposal
+
+Instead of guesstimating work hours and giving an hourly rate, we are asking for an amount that will guarantee funding for the entire wallet rewrite. 
+
+Monerujo's Sidekick project raised 181.15 XMR, and seeing as we addressed the community's concerns by shipping the feature fully airgapped using animated QR codes, we are asking the community to match that amount, plus 10% for misc things like hosting, documentation, website improvement etc for a total of 199.265 XMR.  
+
+For the past year and a half we relied on our small community to help fund us, and now that we've proven we can deliver, we are requesting 20% upfront to start development:
+ 
+- Milestone 1:  39.853 XMR (20%) paid upfront upon funding
+  
+- Milestone 2:  79.706 XMR (40%) paid upon release of first test build (corresponding to v0.5)
+
+- Milestone 3:  79.706 XMR (40%) paid upon final feature-complete release
+
+Progress will be posted on our repo http://git.anonero.io (onion redirect) and we will begin open testing as soon as we can.
+
+CCS will expire one year from date of first payout and funds can be send to the General Fund.

randybrito-locha-mesh.md

+---
+layout: cp
+title: "[Monero Aligned] Locha Mesh, a resilient long-range radio mesh network"
+author: "Randy Brito (@randybrito | @rdymac | @btcven)"
+date: 19 January 2020
+amount: 150
+milestones:
+  - name: Month 1
+    funds: 50 XMR
+    done: 24 May 2020
+    status: finished
+  - name: Month 2
+    funds: 50 XMR
+    done: 24 May 2020
+    status: finished
+  - name: Month 3
+    funds: 50 XMR
+    done: 20 July 2020
+    status: finished
+payouts:
+  - date: 26 May 2020
+    amount: 100
+  - date: 20 July 2020
+    amount: 50
+---
+
+### What
+
+Advance the development of the Locha Mesh open-source software and hardware (https://github.com/btcven/locha) to enable private transactions broadcasting and sync without Internet over a resilient decentralized censorship-resistant mesh network using encrypted long-range radio communications.
+
+
+### Who & Why
+
+I’m Randy Brito, the founder of http://BitcoinVenezuela.com and co-founder CEO of Locha Mesh (@Locha_io).
+
+At Locha Mesh we are creating the open-source software and hardware for real mesh network devices that will enable secure and private communications and transactions without Internet. The Locha Mesh will also enable access to censorship-resistant websites and information, without people having to post their Internet IP address or SIM card which is linked to their identity, so communications could be completely private.
+
+The firmware that runs on the hardware, the hardware specification itself for creating your DIY Locha Mesh device, the mobile app and other software can be found in our GitHub organization, hosted by the non-profit Bitcoin Venezuela (https://github.com/btcven).
+
+What we've been doing at Bitcoin Venezuela for Monero over the years:
+
+- I've recommended the use of Monero in Venezuela for years due to its privacy features.
+- Bitcoin Venezuela's prices API have been showing the real market XMRVEF rate for years (used by CakeWallet). Latest version 2.0 has also been showing XMRVES and keeping historical of both (https://api.bitcoinvenezuela.com/v2/historical/?pair=XMRVEF).
+- I own MoneroVenezuela.com and MoneroVenezuela.org since 2016 to keep these domain names away from scammers trying to steal from Venezuelans.
+
+
+### How does the Locha Mesh help Monero?
+
+We are creating the software and hardware (our own boards and also the specification for a DIY version of it) for anyone to be able to connect to the Locha Mesh to transmit data securely and privately. So the Locha Mesh will enable what we intend to be an alternative communication channel for syncing nodes without having to go through the over-controlled censorable traditional Internet infrastructure.
+
+In the past two years people have tried to transmit Bitcoin transactions over long-range radio, but they've been using hardware that is very limited, closed-source, and also on licensed bands that need the operator to get a Government license to be able to transmit. We at Locha Mesh are creating a real high-bandwidth open mesh network, using license-free bands, that is capable of handling not only block headers and transactions (which are very small in size) but also block sync and other more useful features, like the IPv6 support so services can run inside the Locha Mesh.
+
+
+### This Proposal and Milestones
+
+Monthly pay: 50 xmr (or ~$3,500.00 USD)
+
+This monthly pay covers the cost of two full-time developers working on the Locha Mesh core code.
+
+Total: 150 XMR
+
+Milestones:
+- Improve documentation for Monero developers who want to contribute to Locha Mesh code (first month).
+- Improve documentation on how to build a DIY version of the Locha Mesh devices for developers to join efforts (1-2 months).
+- Monero will be mentioned in the backers sections at https://github.com/btcven/locha home of the Locha Mesh open-source project, also at the documentation website when it is published, and whenever opportunities arise on social media (1-2 months).
+- Work with Monero Outreach to promote Locha Mesh and the support from Monero, as well as translate documentation into other languages (3 months).
+- Demo of the Turpial devices sending messages over a radio mesh network (3 months).
+
+Payments: 3 payments of 50 XMR (or ~$3,500.00 USD), one for each month (paid in XMR)
+
+This proposal can be reviewed in a month by month basis, and terminated at any given month if the Monero community agrees on that.
+
+
+### In the long term
+
+When previous milestones have been achieved and thanks to the contributions of the Monero community we would have been able to get closer to a deployment-ready state, these are some of the tasks we could work on that could be added in future proposals.
+
+Future Roadmap:
+- Research of what would be needed to be able to `submit_transaction` of an off-line `signed_monero_tx` file using gateways to reach the Monero network
+- Details of the finished revision of the Turpial hardware that will be the production-ready device
+- The Locha Mesh working as a production-ready product for private messaging over a decentralized mesh network of long-range radio devices
+- The implementation of `submit_transaction` of an off-line `signed_monero_tx` file using Turpial devices or DIY versions to reach gateways in the Locha Mesh
+- Synchronizing a Monero node over the Locha Mesh
+- Open-sourcing the hardware of the Turpial device. We could do this, but it would need a substantial amount so we are able to cover the costs of the ongoing development of the Locha Mesh for a couple years at least, if raised development of both the software and hardware would not need to depend on VC money
+
+
+### Where to follow progress
+
+Regular updates will be shared by myself and the development team (changelogs) with features that have been finished and worked on each month (at least monthly) in our Twitter: @Locha_io , the updates section at GitHub (https://github.com/btcven/locha) with the Locha Mesh's core features being implemented, and our website: https://locha.io
+
+
+### Contact
+
+Randy Brito: randy@locha.io | contacto@bitcoinvenezuela.com
+
+GPG: 637E 773C F6DD EE8F 009F 8461 6930 CFE7 0FA4 130C
+
+If you prefer ProtonMail: bitcoinvenezuela@protonmail.com

rating89us-1.md

+---
+layout: cp
+title: rating89us part-time Monero GUI UI/UX development (3 months)
+author: rating89us
+date: 30 June 2021
+amount: 48.31
+milestones:
+  - name: July
+    funds: 33% (16.10 XMR)
+    done: 15 August 2021
+    status: finished
+  - name: August
+    funds: 33% (16.10 XMR)
+    done: 15 September 2021
+    status: finished
+  - name: September
+    funds: 33% (16.11 XMR)
+    done: 30 November 2021
+    status: finished
+payouts:
+  - date: 6 December 2021
+    amount: 48.31
+---
+
+## What
+
+Hi, everyone! I am rating89us and this is my first CCS proposal. I have been doing voluntary (unpaid) contributions to Monero GUI on my free time since 2020, adding new UI elements, improving UX and fixing bugs. While Monero GUI has improved a lot during the last years, there is still a lot of work to be done. I'm really motivated in making Monero GUI easy to use by anyone.
+
+Some things I want to work on:
+-	General: add tooltips where still necessary, improve displaying of wallet > accounts hierarchy, discreet mode (hide amounts/balances on all pages); implement tip of the day popup; implement user onboarding popups when the wallet is opened for the first time
+-	LeftPanel: redesign synchronization progress bars, Socks5 proxy/TOR icon
+- Send: display "All" amount as a label with close button
+-	Address book: user avatars, sorting
+-	Transactions: amount filtering, sent/received filtering, historical fiat price
+-	Settings: create a dedicated page to synchronization process, redesign Node page, add "change restore height" menu item
+-	Merchant: redesign merchant page, UI/UX for tablets/smartphones
+-	Wizard: redesign hardware wallet page, create a dedicated page to seed and restore height
+-	Accessibility: add description/navigation for UI elements (support screen readers for visually impaired users)
+-	White theme: improve color contrast of UI elements
+-	Upgrade FontAwesome icons to last version
+-	Android: test and improve UI/UX for tablets/smartphones
+-	Test and review UI/UX pull requests
+-	Update text and screenshots of Monero GUI guides (pdf guide and getmonero.org user guides)
+
+## Who
+
+rating89us, I have been contributing voluntarily to Monero GUI since 2020 with over 77 merged commits. 
+
+Here is a list of my previous merged commits on Monero GUI:
+- Pull requests: https://github.com/monero-project/monero-gui/pulls?page=1&q=is%3Apr+author%3Arating89us+is%3Aclosed
+- Commits: https://github.com/monero-project/monero-gui/commits?author=rating89us
+
+If funded I will provide monthly updates in the CCS comment section.
+
+## Proposal
+
+Work for 20 hours per week over the next 3 months (from Mid July to Mid October) at a rate of 38€/hour. At 188.75€/XMR on Kraken (14-day EMA) this makes 48.31 XMR.

rehrar-36c3-expenses.md

+---
+layout: cp
+title: rehrar to 36C3
+author: rehrar
+date: October 17, 2019
+amount: 58.65
+milestones:
+  - name: Payout to purchase the things
+    funds: 58.65
+    done: October 11, 2019
+    status: finished
+payouts:
+  - date: October 11, 2019
+    amount: 58.65
+---
+
+Heyo everyone. Welcome back to another edition of "rehrar asks for money to do Monero related things". In this episode, rehrar wants to go back to C3. So I guess this one is called rehrar to C3 2: Return of Jafar.
+
+Basically, similar to last year, I want to go help at 36C3. Last year I was the MC, did general coordination, and helped to run the floor and speeches, as well as giving a few speeches on my own.
+
+The costs to send me to Leipzig is as follows:
+
+Flight	1700
+
+Hotel	630
+
+Incidentals	565
+
+Ticket	140
+
+For a total of 3035. 
+
+Converted to XMR (With a 10% buffer):
+58.65 XMR.
+
+IF the community thinks I would be of value to go to C3, then let's get this tagged and bagged. Thanks all!

rehrar-defcon-reimburse-2019.md

+---
+layout: cp
+title: Defcon 2019 Volunteer Reimbursement
+author: rehrar
+date: May 20, 2019
+amount: 137
+gitlab_url: "https://repo.getmonero.org/monero-project/ccs-proposals/merge_requests/69"
+milestones:
+  - name: Person 1 paid
+    funds: 24.5 XMR
+    done: June 18, 2019
+    status: finished
+  - name: Person 2 paid
+    funds: 22.5 XMR
+    done: June 18, 2019
+    status: finished
+  - name: Person 3 paid
+    funds: 10.9 XMR
+    done: June 18, 2019
+    status: finished
+  - name: Person 4 paid
+    funds: 28.2 XMR
+    done: June 18, 2019
+    status: finished
+  - name: Person 5 paid
+    funds: 27.4 XMR
+    done: June 18, 2019
+    status: finished
+  - name: Scholarships paid
+    funds: 23.5 XMR
+    done: July 9, 2019
+    status: finished
+payouts:
+  - date: June 18, 2019
+    amount: 24.5 XMR
+  - date: June 18, 2019
+    amount: 22.5 XMR
+  - date: June 18, 2019
+    amount: 10.9 XMR
+  - date: June 18, 2019
+    amount: 28.2 XMR
+  - date: June 18, 2019
+    amount: 27.4 XMR
+  - date: July 9, 2019
+    amount: 23.5 XMR
+---
+
+What's up everyone? Your friendly neighborhood rehrar here.
+
+Let's talk about Defcon. Remember Defcon? Biggest hacker conference in the world. Taking place in Las Vegas, NV, USA, early this August? Well, last year Monero's village was a hueg success, and we were constantly full with people willing and eager to learn. This year, they've approved us for another village, and have given us a bigger space! Woohoo!
+
+A lot of planning a preperation has already been taking place on Taiga, #monero-defcon in IRC, and in #monero-community where we have biweekly Defcon meetings. What's been most recently discussed is the need that we have to get some key volunteers there to make this village a success. These roles are:
+
+- 2 A/V people, one for running sound, and the other for recording video. Reason: The Defcon people didn't do a fantastic job last year, and the videos turned out very underwhelming in terms of quality. So we want to do it ourselves this year.
+
+- Floor manager/MC, or someone to make sure everything runs smoothly once the village is set up, the presentations start on time, and a point of contact for all non-Defcon related stuff.
+
+- Full time volunteer, or someone that will be spending the majority of their time manning some of the informational tables at the start. Believe me, last year these tables got A LOT of traffic, and we were able to talk to tons and tons of people. Having someone there full-time would be awesome.
+
+- Michael. There's no other way to say it, but Michael's organic connections in the space are the reason we can put on a village, both last year and this year. He is Defcon's official contact for our village, and his presence is greatly required.
+
+We consider these the absolute must-haves in order for this village to funtion and be as successful (if not more) than last year. We are requesting for all expenses paid (flight, hotel, incidentals, Defcon cost) for these five people, who have already been chosen. They are ajs and midipoet, myself, sarang, and Michael respectively).
+
+BUT we would also like to fund FOUR $500 scholarships for four part time volunteers to lower the barrier to Vegas for a few volunteer that are willing to spend the majority of their time making Monero a success. It was very nice to have many helping hands last year. Very needed.
+
+The total value for all of these things is **$11645,** which is about on par for last year (plus the scholarships), and this comes out to **137 XMR** while using a $85/XMR (small buffer built in from current price of $87.5).
+
+To quote last year's proposal: "To protect the privacy of different people's potential location that they will be traveling from, the breakdown of travel costs are not given, but can be provided to the Core Team upon request." The individual costs for anonymized volunteer attendees can be viewed in the milestones tab.
\ No newline at end of file

rehrar-help-out.md

+---
+layout: wip
+title: rehrar help the project
+author: rehrar
+date: June 29, 2024
+amount: 75
+milestones:
+  - name: Month 1
+    funds: 25
+    done: 23 August 2024
+    status: finished
+  - name: Month 2
+    funds: 25
+    done:
+    status: unfinished
+  - name: Month 3
+    funds: 25
+    done:
+    status: unfinished
+payouts:
+  - date: 26 August 2024
+    amount: 25
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+# Who, what, when, where?
+
+Hi, I'm Diego "rehrar" Salazar. I run [Cypher Stack](https://cypherstack.com), and me and my team make [Stack Wallet](https://stackwallet.com). I also did work for the core team once upon a time.
+
+I was recently approached my luigi, of the current core team about retaking on some of my old duties. There's a lot of opportunity for improvement in the non-dev areas of the project, and not always enough hands to get it done. It was agreed upon that, were this to happen, this would be done through the CCS rather than through Core as before. This moves me from being accountable to core, to accountable to the community.
+
+A quick summary of what I'd be working on (requested by luigi):
+- Presiding over and helping along a Monero Website Workgroup to merge requests, keep it up to date, and do odds and ends of design and development
+- Facilitating moderator relationships and fostering community in relevant social platforms
+- Being a leader in the Monero Community workgroup and helping that along as needed
+- Keeping a finger on the "pulse of the community" in the various chat rooms and platforms (Telegram, Discord, IRC, Matrix, Reddit, etc.)
+- Assisting plowsof as needed in CCS work (working under him for various tasks if needed)
+- Aiding and assisting in event work as needed
+- Utilizing my "soft skills" as needed elsewhere on the project.
+
+# Why?
+There's lots of non-dev stuff to do, and not so many people to do it. I am capable and willing.
+
+# How long? How much?
+
+75 XMR for three months for half time work. Possibility of renewal depending on community sentiment.
+
+# Deliverables
+I will do all of the above in the beginning section, and give a monthly report to the community on what's been done, and tasks accomplished. The primary metric I will rate myself on though, is how big of a help I am to luigi in terms of taking workload off of his shoulders.
+
+# COI
+My company Cypher Stack does occassional work for Monero in the form of the following:
+- Dan "pigeons" Miller who helps with infrastructure work is employed by Cypher Stack. We typically do anywhere from 5-10 hours a month for Monero here. We are currently doing this work pro bono.
+- Cypher Stack's cryptographer, Aaron Feickert, does occassional research work for Monero. This is funded either by the CCS, or the new Research Fund that has been funded by the CCS.
+- I own and operate Stack Wallet, an open-source, multicoin wallet, of which Monero is supported.
+- I and all of my employees do occassional work for other clients, many of them in the privacy or crypto sphere. Several of them privacy coins themselves.
\ No newline at end of file

rehrar-sarang-2019-wcc.md

 ---
-layout: fr
+layout: cp
 title: World Crypto Con for rehrar and Sarang
 author: rehrar
 date: July 17, 2019
@@ -7,17 +7,17 @@ amount: 30
 milestones:
   - name: Payout rehrar
     funds: 13.4
-    done:
-    status: unfinished
+    done: 23 August 2019
+    status: finished
   - name: Payout sarang
     funds: 16.6
-    done:
-    status: unfinished
+    done: 23 August 2019
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 23 August 2019
+    amount: 13.4
+  - date: 23 August 2019
+    amount: 16.6
 ---
 
 What up everyone, it's your boy rehrar.

research-post-quantum-monero.md

+---
+layout: cp
+title: Research post-quantum strategies for Monero
+author: Insight
+date: May 20, 2020
+amount: 576
+milestones:
+  - name: Initial payout
+    funds: 100% (576 XMR)
+    done: 14 July 2020
+    status: finished
+  - name: Identify and document existing vulnerabilities in Monero
+    funds: 0% (0 XMR)
+    done: September 2020
+    status: finished
+  - name: Research Monero-compatible post-quantum cryptography methods
+    funds: 0% (0 XMR)
+    done: September 2020
+    status: finished
+  - name: Communicate and Educate
+    funds: 0% (0 XMR)
+    done: October 2020
+    status: finished
+payouts:
+  - date: 14 July 2020
+    amount: 576
+---
+![](https://raw.githubusercontent.com/insight-decentralized-consensus-lab/monero_quantum_resistance/master/images/dual_logos.png)
+# Identifying practical post-quantum strategies for Monero
+
+## Motivation:
+Monero transactions created between 2014 and 2020 utilize cryptographic mechanisms that were not designed to be private or secure against quantum computers. Algorithms that could theoretically circumvent several of Monero's security and privacy features are already known, such as [Shor's algorithm](https://ieeexplore.ieee.org/document/365700/) (which [breaks security](https://scialert.net/fulltext/?doi=jas.2005.1692.1712) based on the discrete logarithm problem) and [Grover's algorithm](https://arxiv.org/abs/quant-ph/9605043) (which could be used to [forge blocks](https://www.mitre.org/sites/default/files/publications/17-4039-blockchain-and-quantum-computing.pdf)). 
+
+Let us define a hypothetical “practical” quantum computer as any device that enables an adversary to effectively circumvent some security expectation provided by cryptographic mechanisms. This is not defined by some magic number of qubits or any particular configuration; it refers to the **capability** to leverage methods such as Fourier fishing, Grover's algorithm, or Shor's algorithm with enough complexity to tackle modern cryptography. **Speculation on whether practical quantum computers will ever exist, and when they might arrive, is outside the scope of this cryptography research proposal.**
+
+There are several ways that a sophisticated quantum adversary might access funds and sensitive information that would otherwise be cryptographically obfuscated:
+
+- **Deriving private keys from public keys**: A quantum adversary that has obtained your public wallet address can derive your private key. This enables them to learn your entire (past and subsequent) transaction history, and steal any current/future funds by forging a transaction from you to themselves.
+- **Deriving private keys from key images**: A quantum adversary can also break the privacy of some features for every transaction already recorded on the ledger, by using key images to derive transaction private keys.
+- **Deobfuscating the transaction graph**: Each ring signature references several (currently 11) past outputs, only one of which is truly being spent. Deobfuscation refers to analyzing the true flow of funds to eliminate the privacy provided by ring signatures and stealth addresses. Graph matching analyses are already parallelizable on traditional computers, and may be easier for quantum computers.
+- **Consensus mechanism & blockchain immutability**: Monero's proof-of-work algorithm ([RandomX](https://github.com/tevador/RandomX)) involves chaining several (currently 8) operations by a VM, designed like a one way function (such that the input to produce a given output can only be found by brute force). We will evaluate whether this approach can be exploited by quantum computers leveraging methods such as Fourier fishing or Grover's algorithm. The potential ability to forge blocks with a specific hash would defeat blockchain immutability, however this can be mitigated with the addition (i.e. concatenation) of post-quantum hash functions and checksums.
+
+**Retroactive deanonymization puts today's Monero users at the hands of tomorrow's [quantum or classical] adversaries.** If practical quantum computers that can break Monero's encryption arrive at any point in the future, then users' lifelong transaction history willl become public for ingestion by the AdTech industry, stalkers, criminals, and governments. It is irrelevant which party publishes a de-anonymized copy of the Monero blockchain first - the universal evaporation of privacy is irreversible.
+
+Thankfully, cryptographers have developed several post-quantum security and privacy schemes that may be adaptable to Monero. Promising techniques include [zero-knowledge lattice cryptography](https://eprint.iacr.org/2019/747.pdf)  based on the [shortest vector problem](https://en.wikipedia.org/wiki/Lattice_problem#Shortest_vector_problem_(SVP)). Methods such as [hash-based ring signatures](https://eprint.iacr.org/2019/567.pdf), [GLYPH](https://eprint.iacr.org/2017/766.pdf) (Schnorr-like lattice-based signature scheme), and the cohort of [NIST post-quantum](https://csrc.nist.gov/news/2019/pqc-standardization-process-2nd-round-candidates) candidates were all designed to enable security in a post-quantum world. The [quantum resistant ledger](https://theqrl.org/) is of particular interest due to its extensibility, immutability, and RandomX integration - however no privacy features are currently implemented. Other designs for [anonymous post-quantum cryptocash](https://eprint.iacr.org/2017/716.pdf) have been considered, and the [Halo](https://eprint.iacr.org/2019/1021.pdf) recursive zero-knowledge proving system offers plausible post-quantum security. Each approach has its own benefits, drawbacks, and space/time complexity - our research recommendations will take into account these practical considerations in addition to theoretical compatibility.
+
+**This research will (1) study and simulate the threats listed above to assess Monero's vulnerability to quantum computers, (2) evaluate post-quantum cryptography scheme candidates to create a roadmap for hardening Monero against quantum adversaries, and (3) openly communicate the results for a variety of audiences.**
+
+The advent of powerful quantum computers will wreak havoc on almost every aspect of our digital infrastructure. Access to sound money (which requires privacy) is a fundamental human right and should be considered a high priority for hardening against quantum adversaries. To our knowledge, there are currently no plausibly post-quantum anonymous currencies in use today, meaning that only short-to-intermediate term financial privacy is available with current technology. The first coin to implement long-term post-quantum privacy features will be in a strong position for adoption, even long before quantum computers arrive.
+
+>"A post-quantum world would destroy Amazon, Wells Fargo, Visa, and most world governments. But there's no reason it has to also destroy Monero." 
+>
+> _Surae Noether_
+
+## Overview:
+
+R & D Institution: Insight
+
+Funding Institution: Monero CCS
+
+Duration: 3 months (June - August 2020)
+
+Contributors:
+
+- Researcher in Residence: Adam Corbo
+  - Decentralized Consensus Fellow at Insight
+  - Developed open-source proof-of-concept quantum PoW miner
+  - Expertise translating academic/mathematics research into code 
+  - 2 years of experience in quantum information theory and computation at UC Berkeley
+  - [GitHub](https://github.com/hamburgerguy/), [Twitter](https://twitter.com/adamryancorbo/), [LinkedIn](https://www.linkedin.com/in/adam-corbo/)
+- Principal Investigator: Mitchell Krawiec-Thayer
+  - Head of Research, Developers in Residence at [Insight](http://www.insightconsensus.com/)
+  - Data Science for Monero Research Lab
+  - Quantum classes & calculations during PhD (in context of spectroscopy research)
+  - [GitHub](https://github.com/mitchellpkt/), [Twitter](https://twitter.com/Mitchellpkt0), [LinkedIn](https://www.linkedin.com/in/mitchellpkt/), [Medium](https://medium.com/@mitchellpkt)
+- Other Insight contributors
+  - Code & documentation reviewers will be assigned as milestones near completion.
+  - Additional thanks to office staff, accounting, etc for creating a productive workspace.
+
+## Project Roadmap:
+
+### Phase 1: Identify and document existing vulnerabilities in Monero
+
+The first phase of this problem will focus on identifying which of Monero's security features are susceptible to quantum adversaries. We'll look for vulnerabilities to known tools such as Shor's algorithm (which can find discrete logarithms is polynomial time, breaking the DL problem), Grover's algorithm (which produces a quadratic speedup when searching for inputs that map to a particular output for any black box function), and Fourier fishing in conjunction with the Deutsch-Josza algorithm (which can potentially be used in taking advantage of Monero's proof of work method in bounded-error quantum polynomial time).
+
+Some vulnerabilities are already known, for example that cryptography based on elliptic curve and the discrete logarithm problem can be made insecure using Shor's algorithm. We will examine Monero's protocol for other examples of security based on problems that are computationally intractable for classical computers and easy for quantum computers. Some current privacy features are thought to be quantum resistant (such as Monero's masked amounts) and we will cautiously verify their security against our algorithmic adversarial toolkit.
+
+**Phase 1 deliverables:** 
+
+-  Formally enumerate adversary model capabilities: Shor's algorithm, Grover's algorithm, Fourier fishing, etc.
+-  Enumerate Monero mechanisms of interest: ring signatures, bulletproofs, stealth addresses, asymmetric cryptography, consensus mechanism, etc.
+-  Systematically assess the impacts of each algorithm on each mechanism, completing this table: 
+
+|                     | Monero mechanism 1 | Monero mechanism 2 | ... |
+|---------------------|--------------------|--------------------|-----|
+|  Shor's algorithm   |  Plausibly secure  | Plausibly secure   | ... |
+|  Grover's algorithm | Irrelevant         | **VULNERABLE** | ... |
+| Fourier Fishing     | Plausibly secure   | Irrelevant         | ... |
+| ...                 | ...                | ...                | ... |
+
+### Phase 2: Research Monero-compatible post-quantum cryptography methods
+
+After locating and documenting Monero's quantum vulnerabilities, we will identify alternative cryptographic schemes that mitigate these weaknesses. Known post-quantum systems will be examined for Monero-compatibility (see Appendix 1 for a list of potentially relevant literature to be analyzed). In addition to interoperability, we will note practical considerations related to verification time, signature/proof size, and implementation. If there are no known solutions for mitigating a particular vulnerability, we will note the constraints necessary for developing a unique solution.
+
+There are three broad categories of implications, which are not mutually exclusive:
+
+- Deanonymization (knowing more about others' transactions than you should)
+- Theft (being able to move others' funds)
+- Mining speedup (obtaining valid nonces paradigmatically faster)
+
+Vulnerable privacy features will be given highest priority, since retroactive deanonymization poses a threat to today's Monero users, whereas theft and mining are not an issue until quantum computers scale past a distant threshold. Mining vulnerabilities are the lowest priority, since switching consensus mechanisms is easier than implementing new cryptographic schemes. 
+
+It's important to note that many current post-quantum cryptography candidates require large proofs and significant computational resources, and will thus not be suitable for immediate deployment. For this reason, understanding broad strategies and their tradeoff will be more useful than specific implementations. Thankfully, consumer device capabilities increase over time, and researchers continue to discover new faster/smaller proving systems, so these practical barriers are temporary. 
+
+**Phase 2 deliverables:** List of vulnerabilities, following this format when possible:
+
+> Monero's **[component]** is vulnerable to **[impact]** by a hypothetical adversary that can leverage **[algorithm]**. In general, the solution must meet **[requirements]**. Current relevant methods include **[cryptosystem]** which would require **[migration process]** and has **[tradeoffs]** that would prevent implementation until **[device bandwidth/resource threshold]** is widely available.
+
+### Phase 3: Communicate and Educate
+
+Throughout this entire project, the community will receive updates during the weekly #monero-research-lab meetings. During phase 3 however, several specific documents (the key deliverables from this research) will be freely published: 
+
+**Phase 3 deliverables:** 
+
+1. **User-friendly writeup:** This community-facing writeup will provide an approachable explanation of how hypothetical quantum computers may impact Monero, and possible future mitigations. The writeup should minimize FUD and provide the context that these vulnerabilities apply to almost all cryptocurrencies (not only Monero).
+
+2. **Technical documentation:** An MRL position paper to distill key information for (current and future) researchers and developers. The writeup should formally describe vulnerabilities, and highlight potential strategies and solutions, noting their tradeoffs. Code snippets may be included if appropriate for pedagogical purposes or clarity.
+
+3. **Non-technical 1-pager:** An ELI5 / TL;DR summary will be provided for journalists, Monero Outreach, etc. This blurb will discuss risks and myths with no technical jargon, with key takeaways that a broad audience will appreciate.
+
+Results and updates will be also disseminated via Twitter threads, Reddit posts, and Breaking Monero videos. 
+
+# Resources
+
+*Updated 2020-05-20: Based on discussion in #monero-community earlier today, we are moving forward with option #2 below (pre-payment to mitigate volatility risks). The original text is left below for transparency & context.*
+
+The team tackling this project consists of one full-time researcher dedicated solely to this proposal (Adam), along with mentoring and writing by Mitchell (5-15 hr/wk), input from the Director of Security, and internal editors/reviewers. We intend to execute this research initiative over a twelve week period between June - August 2020 for 37500 USD.
+
+Insight's bills and employees' salaries are dollar-denominated, so we must minimize exposure to volatility risk. We are open to three different approaches, and will let the community choose how to proceed:
+
+1. If payouts can only be received after the work is completed, we will need to add a volatility buffer (see [TL;DR explanation](https://twitter.com/Mitchellpkt0/status/1252720219644063745), and [open source code](https://github.com/Mitchellpkt/volatility_analysis/blob/master/volatility_analysis.ipynb)). Based on the last 2 years of data, and a 4-month window (1 month of fundraising + 3 months of reseearch), a 35% buffer provides a 80% statistical confidence of receiving sufficient payout. Thus the CCS goal would include an extra 4375 USD per month
+2. If the funds can be released at the beginning of the research period, then no buffer is necessary. *Update:* If any of the three milestones are not completed within 12 months, 1/3 of the project value will be converted to XMR and returned to the general fund. (i.e. Insight would refund XMR worth 12500 USD for *each* missing milestone).
+3. Some mutually-trusted third party could escrow the funds in fiat form (to eliminate volatility risk), and pay Insight upon satisfactory work.
+
+# Appendix 1 - Literature
+
+Here is relevant literature that will be reviewed and annotated for utility to Monero. List compiled by Dr. Brandon Gooddell
+
+- Liu, Joseph K., Victor K. Wei, and Duncan S. Wong. 'Linkable spontaneous anonymous group signature for ad hoc groups.' Australasian Conference on Information Security and Privacy. Springer, Berlin, Heidelberg, 2004.
+- Zhang, Huang, et al. 'Anonymous post-quantum cryptocash.' International Conference on Financial Cryptography and Data Security. Springer, Berlin, Heidelberg, 2018.
+- Torres, Wilson Abel Alberto, et al. 'Post-quantum one-time linkable ring signature and application to ring confidential transactions in blockchain (lattice RingCT v1. 0).' Australasian Conference on Information Security and Privacy. Springer, Cham, 2018.
+- Groth, Jens, and Markulf Kohlweiss. 'One-out-of-many proofs: Or how to leak a secret and spend a coin.' Annual International Conference on the Theory and Applications of Cryptographic Techniques. Springer, Berlin, Heidelberg, 2015.
+- Chopra, Arjun. 'GLYPH: A New Instantiation of the GLP Digital Signature Scheme.' IACR Cryptology ePrint Archive 2017 (2017): 766.
+- Unruh, Dominique. 'Post-quantum security of Fiat-Shamir.' International Conference on the Theory and Application of Cryptology and Information Security. Springer, Cham, 2017.
+- Okamoto, Tatsuaki, et al. 'New realizations of somewhere statistically binding hashing and positional accumulators.' International Conference on the Theory and Application of Cryptology and Information Security. Springer, Berlin, Heidelberg, 2015.
+- Lu, Xingye, Man Ho Au, and Zhenfei Zhang. '(Linkable) Ring Signature from Hash-Then-One-Way Signature.' 2019 18th IEEE International Conference On Trust, Security And Privacy In Computing And Communications/13th IEEE International Conference On Big Data Science And Engineering (TrustCom/BigDataSE). IEEE, 2019.
+- Backes, Michael, et al. 'Ring signatures: Logarithmic-size, no setup—from standard assumptions.' Annual International Conference on the Theory and Applications of Cryptographic Techniques. Springer, Cham, 2019.
+- Yang, Rupeng, et al. 'Efficient lattice-based zero-knowledge arguments with standard soundness: construction and applications.' Annual International Cryptology Conference. Springer, Cham, 2019.
+- Esgin, Muhammed F., et al. 'MatRiCT: Efficient, Scalable and Post-Quantum Blockchain Confidential Transactions Protocol.' Proceedings of the 2019 ACM SIGSAC Conference on Computer and Communications Security. 2019.
+- Torres, Wilson Alberto, et al. 'Lattice RingCT v2. 0 with Multiple Input and Multiple Output Wallets.' Australasian Conference on Information Security and Privacy. Springer, Cham, 2019.
+- Ruffing, Tim, and Giulio Malavolta. 'Switch commitments: A safety switch for confidential transactions.' International Conference on Financial Cryptography and Data Security. Springer, Cham, 2017.
+- Zhang, Huang, et al. 'Anonymous post-quantum cryptocash.' International Conference on Financial Cryptography and Data Security. Springer, Berlin, Heidelberg, 2018.
+- Zhang, Huang, et al. 'Implementing confidential transactions with lattice techniques.' IET Information Security 14.1 (2019): 30-38.
+- [http://www.fields.utoronto.ca/talks/Toward-More-Secure-Quantum-Future](http://www.fields.utoronto.ca/talks/Toward-More-Secure-Quantum-Future)
+

revuo-monero-maintenance-2024-q3.md

+---
+layout: cp
+title: Revuo Monero maintenance (2024 Q3)
+author: rottenwheel
+date: June 3, 2024
+amount: 8
+milestones:
+  - name: July
+    funds: 3
+    done: 2 August 2024
+    status: finished
+  - name: August
+    funds: 3
+    done: 5 September 2024
+    status: finished
+  - name: September
+    funds: 2
+    done: 1 October 2024
+    status: finished
+payouts:
+  - date: 12 August 2024
+    amount: 3
+  - date: 10 September 2024
+    amount: 3
+  - date: 2
+    amount: 7 October 2024
+---
+
+# What
+
+I will maintain Revuo Monero (https://www.revuo-xmr.com/) for the next 3 months (2024 Q3): July, August and September. There is a chance I may skip one week to tend to real life issues, in such case, next issue will just cover 2 weeks instead of 1.
+
+Tasks:
+
+- Daily/weekly: search, curate, structure and post new reports/stories.
+- As Needed: outreach (engage with the community on Matrix, XMPP, emails).
+- As Needed: make sure the website is live and working as expected (server maintenance, billing, etc.)
+
+# Who
+
+rottenwheel, I joined the Monero community some time in 2017 by jumping into IRC, attending some Workgroup meetings, volunteering at the Monero village at DEFCON 28 in 2019 (https://redlib.zaggy.nl/r/Monero/comments/cqegma/monero_village_defcon_2019_report/), participating in community events and being involved with other community-driven, smaller projects.
+
+As a proof of work for this specific proposal, I have, since January 2022 until now, written almost 200 issues, 195 of which were published in current Revuo's self-hosted website. That does not take into account the following enhancements.
+
+Up to this point, all efforts behind Revuo Monero's comeback after Diego "rehrar" Salazar was let go and Revuo Monero's publication was paused for a few months, include but are not limited to:
+
+- Light/dark theme with a toggle button (mostly in CSS/HTML, minimizing the reliance in JavaScript as much as possible; site loads everything just fine in Tor browser with strict security mode on.)
+- Support and Source Code sections added.
+- RSS and Support icons.
+- Google fonts removed.
+- Twitter and Nostr profiles set up and posting new issues every week automatically. Twitter: https://nitter.poast.org/revuoxmr; Nostr: https://primal.net/p/npub1tn8spk9zhxrctg2qym3gj8r7eq2wk6z3phrl8304wc54vt9qam4qvzw6jx
+
+# Proposal
+
+I will publish weekly issues (4 per month) at a rate of $100 / issue. At $157.5 / XMR this makes 8 XMR (~7.6++) (100 * 4 * 3 = $1200) to be split in 3 monthly milestones. Rounding current 7.6++ XMR to 8 XMR to cover for price votatility between Work In Progress phase and progressive milestone(s) payouts.
\ No newline at end of file

revuo-monero-maintenance-2024-q4.md

+---
+layout: cp
+title: Revuo Monero maintenance (2024 Q4)
+author: rottenwheel
+date: September 2, 2024
+amount: 8.5
+milestones:
+  - name: October
+    funds: 3
+    done: 1 November 2024
+    status: finished
+  - name: November
+    funds: 3
+    done: 28 November 2024
+    status: finished
+  - name: December
+    funds: 2.5
+    done: 26 December 2024
+    status: finished
+payouts:
+  - date: 12 November 2024
+    amount: 3
+  - date: 6 December 2024
+    amount: 3
+  - date: 12 January 2025
+    amount: 2.5
+---
+
+# What
+
+I will maintain Revuo Monero (https://www.revuo-xmr.com/) for the next 3 months (2024 Q4): October, November and December. There is a chance I may skip one week to tend to real life issues, in such case, next issue will just cover 2 weeks instead of the usual 1.
+
+Tasks:
+
+- Daily/weekly: search, curate, structure and publish new issues.
+- As Needed: outreach (engage with the community on Matrix, XMPP, e-mails, social media, Workgroup channels).
+- As Needed: make sure the website is live and working as expected (server maintenance, billing, etc.)
+- As Needed: cover code enhancements/fixes expenses, sysadmin consultations and additional Revuo tools/services for the community. 
+
+# Who
+
+rottenwheel, I joined the Monero community some time in 2017 by jumping into IRC, attending some Workgroup meetings, volunteering at the Monero village at DEFCON 28 in 2019 (https://redlib.zaggy.nl/r/Monero/comments/cqegma/monero_village_defcon_2019_report/), participating in community events and being involved with other community-driven, smaller projects.
+
+As a proof of work for this specific proposal, I have, since January 2022 until now, written almost 200 issues, 195 of which were published in current Revuo's self-hosted website. That does not take into account the following enhancements.
+
+Up to this point, all efforts behind Revuo Monero's comeback after Diego "rehrar" Salazar was let go and Revuo Monero's publication was paused for a few months, include but are not limited to:
+
+- Light/dark theme with a toggle button (mostly in CSS/HTML, minimizing the reliance in JavaScript as much as possible; site loads everything just fine in Tor browser with strict security mode on.)
+- Support and Source Code sections added.
+- RSS and Support icons.
+- Google fonts removed.
+- Twitter and Nostr profiles set up and posting new issues every week automatically. Twitter: https://nitter.poast.org/revuoxmr; Nostr: https://primal.net/p/npub1tn8spk9zhxrctg2qym3gj8r7eq2wk6z3phrl8304wc54vt9qam4qvzw6jx
+
+**New**: Revuo Calc, a moner.ooo fork that had its original code shrunk by half (# of total lines), improved upon and it offers 2 versions, adjusted according visitor's browser settings: JavaScript-free front and JavaScript-friendly front; think of Tor users and clearnet users. The cherry on top? Its own subdomain hidden service as well. See: https://calc.revuo-xmr.com/ // Source code: https://github.com/rottenwheel/moner.ooo/ 
+
+# Proposal
+
+I will publish weekly issues (4 per month) at a rate of $120 / issue. Using MA10 - Moving Average 10 (10 days) of ~$170 / XMR at the time of writing this proposal, this makes for **8.5 XMR** (~8.47058++...) [(120 * 4) * 3 = $1440) to be split in three (3) monthly milestones. Rounding ~8.47058++... XMR to 8.5 XMR to cover for price votatility between Work In Progress phase and progressive milestone(s) payouts.

revuo-monero-maintenance-2025-q1.md

+---
+layout: wip
+title: Revuo Monero maintenance (2025 Q1)
+author: rottenwheel
+date: December 26, 2024
+amount: 8
+milestones:
+  - name: January
+    funds: 3
+    done: 10 February 2025
+    status: finished
+  - name: February
+    funds: 3
+    done: 3 March 2025
+    status: finished
+  - name: March
+    funds: 2
+    done:
+    status: unfinished
+payouts:
+  - date: 24 February 2025
+    amount: 3
+  - date: 19 March 2025
+    amount: 3
+  - date:
+    amount:
+---
+
+# What
+
+I will maintain Revuo Monero (https://www.revuo-xmr.com/) for the next 3 months (2025 Q1): January, February and March. There is a chance I may skip one week to tend to real life issues, in such case, next issue will just cover 2 weeks instead of the usual 1.
+
+Tasks:
+
+- Daily/weekly: search, curate, structure and publish new issues.
+- As Needed: make sure the website is live and working as expected (server maintenance, billing, etc.)
+- As Needed: cover code enhancements/fixes expenses, sysadmin consultations and additional Revuo tools/services for the community. 
+
+# Who
+
+rottenwheel, I joined the Monero community some time in 2017 by jumping into IRC, attending some Workgroup meetings, volunteering at the Monero village at DEFCON 28 in 2019 (https://redlib.zaggy.nl/r/Monero/comments/cqegma/monero_village_defcon_2019_report/), participating in community events and being involved with other community-driven, smaller projects.
+
+As a proof of work for this specific proposal, I have, since January 2022 until now, written more than two hundred (200) weekly issues of the Revuo Monero newsletter, the first five (5) first published and hosted at [LocalMonero](https://localmonero.co/revuo) and the rest, 200++, were published in current Revuo's self-hosted website. About 24-25 of them had their maintenance and editorial work funded through the CCS, for 2024 Q3 and Q4; now looking to get funding secured for 2025 Q1 with this proposal. Beyond that, I have completed and deployed the following enhancements:
+
+Up to this point, all efforts behind Revuo Monero's comeback after Diego "rehrar" Salazar was let go and Revuo Monero's publication was paused for a few months, include but are not limited to:
+
+- Light/dark theme with a toggle button (mostly in CSS/HTML, minimizing the reliance in JavaScript as much as possible; site loads everything just fine in Tor browser with strict security mode on.)
+- Support and Source Code sections added.
+- RSS and Support icons.
+- Google fonts removed.
+- Twitter profile set up and posting new issues every week automatically, which often get reposted via @monero main account. Twitter: https://nitter.poast.org/revuoxmr
+- Addition of RM's group chats and social media profile links at the bottom of hamburger menu. Nostr, X, XMPP, Matrix, SimpleX and IRC.
+
+**New**: Revuo Calc. See: https://calc.revuo-xmr.com/ // Source code: https://github.com/rottenwheel/moner.ooo/ 
+[WIP] Moneroj.net maintenance and enhancements. Almost ready for relaunch/announcement, under Revuo's umbrella, as Revuo Moneroj.
+
+# Proposal
+
+I will publish weekly issues (4 per month, average) at a rate of $120 / issue. Using MA10 - Moving Average 10 (10 days) of ~$191 / XMR at the time of writing this proposal, this makes for **8 XMR** (~7.5392++...) [(120 * 4) * 3 = $1440) to be split in three (3) monthly milestones. Rounding ~7.5392++... XMR to 8 XMR even to cover for price votatility between Work In Progress phase and progressive milestone(s) payouts.