v1docq47-video-creation-translations-into-russian-(august-2020-january-2021).md

@@ -42,6 +42,8 @@ payouts:
     amount: 16.3
 ---
 
+_Note: Overfunding of 9.775398688381 XMR from this proposal has been awarded to [v1docq47 2024](https://ccs.getmonero.org/proposals/v1docq47-monerotopia-2024-voiceovers-and-working-on-xmr.ru.html)_
+
 Hello, my dear followers, colleagues, and friends!  
 v1docq47 is here!  
 And this is my new funding request for my work.

v1docq47-video-creation-translations-into-russian-(august-january-2022).md

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

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

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

vThorOfflineSigningLibrary_XmrSignerToProduction.md

+---
+layout: wip
+title: Offline Signing Library for XmrSigner to Production
+date: August 31, 2024
+author: Thor a.k.a. vThor a.k.a DiosDelRayo
+amount: 196
+milestones:
+  - name: Upfront
+    funds: 20 XMR
+    done: 11 November 2024
+    status: finished
+  - name: First month, minus upfront
+    funds: 46 XMR
+    done: 5 December 2024
+    status: finished
+  - name: Second month
+    funds: 65 XMR
+    done: 30 January 2025
+    status: finished
+  - name: Third month
+    funds: 65 XMR
+    done:
+    status: unfinished
+payouts:
+  - date: 15 November 2024
+    amount: 20
+  - date: 13 December 2024
+    amount: 46
+  - date: 10 February 2025
+    amount: 65
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+# Offline Signing Library for XmrSigner Production
+
+## About
+
+This proposal aims to create a minimal library for offline signing on
+air-gapped devices, and make XmrSigner production ready to actual use secure, focusing on essential features:
+
+- Seed phrase generation (including polyseed)
+- Address and key generation
+- Account and sub-address management
+- Address verification
+- Output importing and Key Image exporting (raw and encrypted)*
+- Unsigned transaction handling (description, sanity checks, signing)
+- Block height and date estimation
+
+The library will be implemented in C++ with a C ABI, allowing use in
+multiple languages. It will be based on the current Monero source but
+without relying on wallet2, aiming for minimal external dependencies,
+not inventing the wheel again, nor rolling own crypto.
+
+Key objectives:
+- Comprehensive documentation (OTS library, OTS Python library, buildroot packages desired integrated into monero docs for a easy and quick start to build something)
+- Quick start guide for offline and hardware wallet developers
+- Documentation of challenges in stripping down and cross-compiling
+- Buildroot package for easy target system integration
+- Python module for library usage
+- Test code
+- Modification of XmrSigner to use this new library
+
+## Who
+
+Thor (vThor/DiosDelRayo), completed the [XmrSigner (MoneroSigner Resurrection) proposal](https://ccs.getmonero.org/proposals/%20MoneroSignerResurrection.html).
+
+## Why
+
+[XmrSigner](https://github.com/XmrSigner/xmrsigner), while functional, is currently more of a proof of concept than a
+production-ready tool. This library addresses several key issues:
+
+1. Performance: The current implementation using wallet RPC is slow,
+especially on resource-constrained devices.
+2. Security: Minimizing dependencies and code base improves auditability
+and reduces attack surface.
+3. Flexibility: A dedicated library allows for easier integration into
+various offline signing solutions.
+4. Resource efficiency: Stripping down to essential features enables use on
+lower-power devices.
+
+By creating this library, we will:
+- Bring XmrSigner to production readiness
+- Provide a foundation for future hardware wallet development
+- Explore the viability of using even more resource-constrained devices (e.g., MCUs) for offline signing
+- Build the basis for a lib which could also serve for quick payment way (seems there exists something like it called pocket change, was not aware of before) even if the customer is offline. Talked about that in [#monero-community](https://libera.monerologs.net/monero-community/20241018#c446995)
+
+A proof of concept has been developed to validate this approach:
+[c_abi_for_cpp_code_PoC](https://github.com/DiosDelRayo/c_abi_for_cpp_code_PoC)
+
+This library will significantly improve XmrSigner's performance, security,
+and usability while opening doors for more diverse Monero hardware wallet
+solutions in the future.
+
+## Milestones and Timeline
+# Offline Signing Library for XmrSigner Production
+
+## Milestones and Timeline
+
+### 1. Setting up documentation site (4 hours)
+
+All OTS library related will go into a fork of docs.get-monero.org and should take me no more than a blink of an eye to get going.
+For the XmrSigner related part I will setup the same mkdocs via github pages.
+This is apart from the Doxygen and Sphinx documentation, which I need to see how to make it best available on the way.
+<details>
+<summary>View tasks</summary>
+
+| Task | Hours | Sessions |
+|------|-------|----------|
+| Set up initial documentation structure | 2 | 1 |
+| Configure documentation site | 2 | 1 |
+| Use existing Monero documentation through PR's | 0 | 0 |
+
+</details>
+
+### 2. MVP library with C ABI (164 hours)
+
+The main task of this proposal, creating an ots folder in monero/src and nit pick the parts the lib needs together
+to create and compile a actual library. On top add the C ABI and make the build script as easy and robust as possible.
+<details>
+<summary>View tasks</summary>
+
+| Task | Hours | Sessions |
+|------|-------|----------|
+| Initial ABI design | 16 | 8 |
+| Seed phrase generation | 8 | 4 |
+| Address and key generation | 10 | 5 |
+| Account and sub-address management | 10 | 5 |
+| Address verification | 10 | 5 |
+| Output importing and Key Image exporting | 30 | 15 |
+| Unsigned transaction handling | 30 | 15 |
+| Write Doxygen documentation | 14 | 7 |
+| Create detailed documentation of the ABI and library internals | 14 | 7 |
+| Develop unit tests with Check | 14 | 7 |
+| PR process revisions and merge | 8 | 4 |
+
+</details>
+
+### 3. Python cffi classes (44 hours)
+
+Building the clue code between the C ABI and Python in a pythonic way.
+
+<details>
+<summary>View tasks</summary>
+
+| Task | Hours | Sessions |
+|------|-------|----------|
+| Design Python class structure | 10 | 5 |
+| Implement Python wrapper classes | 20 | 10 |
+| Write rich inline documentation | 8 | 4 |
+| Create Sphinx documentation | 2 | 1 |
+| Develop unit tests for Python classes | 4 | 2 |
+
+</details>
+
+### 4. Building library in buildroot (44 hours)
+
+buildroot is a build kit to create an embedded linux with the help of
+packages which get cross compiled for the target platform. Here the dependencies
+to build the OTS library from the monero sources need to be fulfilled.
+
+<details>
+<summery>Show more...</summary>
+A very critical part to use the library on the pi zero (or other target device - maybe modifications will be needed here fore).
+I build for XmrSigner before buildroot packages, but struggled to get monero-wallet-rpc as binary running on
+the pi via Buildroot (how I was building on the Pi itself and there are so many dependencies that finally I pulled
+the plug on that version, becauseit was clear that monero-wallet-rpc was only a temporary solution to finish the CCS
+in a running state)
+</details>
+
+<details>
+<summary>View tasks</summary>
+
+| Task | Hours | Sessions |
+|------|-------|----------|
+| Adapt CMakeLists.txt for the library and its dependencies | 20 | 10 |
+| Create buildroot package for downloading and compiling | 12 | 6 |
+| Write documentation for builders/developers | 12 | 6 |
+
+</details>
+
+### 5. Buildroot package for Python library (12 hours)
+
+The same but a lot easier then for the OTS library, here the Python OTS
+library will get compiled via CPython, how there are only two dependencies (the OTS library and
+cffi) it should be much easier even with a deterministic build.
+
+<details>
+<summary>View tasks</summary>
+
+| Task | Hours | Sessions |
+|------|-------|----------|
+| Create buildroot package for the Python library | 8 | 4 |
+| Write documentation for builders/developers | 4 | 2 |
+
+</details>
+
+### 6. XmrSigner integration (34 hours)
+
+Here the XmrSigner code get's the upgrade, monero-wallet-rpc, python-monero, python-polyseed will
+be replaced by the Python OTS library.
+
+<details>
+<summary>View tasks</summary>
+
+| Task | Hours | Sessions |
+|------|-------|----------|
+| Remove existing dependencies and integrate new Python library | 26 | 13 |
+| Update XmrSigner documentation | 8 | 4 |
+
+</details>
+
+### 7. XmrSigner on XmrSigner OS (buildroot2) (42 hours)
+
+Here all gets assembled together to create the actual XmrSigner production image.
+
+<details>
+<summery>Show more...</summary>
+How I did that already outside of the last CSS, I need only to make some modifications,
+get the dependencies right, the biggest part will be testing and debugging if something
+goes wrong - I had this issue already, but hope that this time is minimal to use the calculated
+time for Milestone 9 because I really like to improve there. But 30 hours can vanish quick debugging
+issues there because it took like 30min to build on a 4c ore i7 with 16GB (lack at the moment something more powerful)
+and then flashing to microSD and test. But how from the buildroot image was forked from SeedSignerOS which stripped handy
+everything unnecessary away - good for security and speed - but terrible to debug.
+</details>
+
+<details>
+<summary>View tasks</summary>
+
+| Task | Hours | Sessions |
+|------|-------|----------|
+| Create buildroot package for XmrSigner | 8 | 4 |
+| Test and debug XmrSigner in buildroot environment | 30 | 15 |
+| Write documentation for XmrSigner OS integration | 4 | 2 |
+
+</details>
+
+### 8. Unify XmrSigner-related components (48 hours)
+
+Getting all the XmrSigner stuff on one place together and the OTS library stuff on docs.get-monero.org, or
+at least in close reach.
+<details>
+<summery>Show more...</summary>
+Through the excessive amount of time the last CCS took the rebranding to XmrSigner and
+putting documentation and linking nice together suffered a bit. So here everything will
+get separated what is actual XmrSigner and what is needed to build a different Offline Signer
+from the OTS library and BCUR. So that XmrSigner is XmrSigner, and the building blocks a close to get-monrero.org
+as possible. All development resources should be on monero docs after the PR got merged, so there is a quickstart
+and all documents to create an offline signer pretty quick.
+</details>
+
+<details>
+<summary>View tasks</summary>
+
+| Task | Hours | Sessions |
+|------|-------|----------|
+| Reorganize and consolidate XmrSigner-related content on GitHub | 8 | 4 |
+| Create separate documentation for UR codes | 20 | 10 |
+| Register UR types used | 6 | 3 |
+| Final review and organization of all documentation | 14 | 7 |
+
+</details>
+
+### 9. (Optional/Stretch) Clean-up and Optimization (82 hours)
+
+Here is where my heart is, but after carefully calculating through the time, and catching myself,
+arguing on almost each point it could be done faster, and almost halving most points... I still with 138h more
+then the original 240 hours estimated. And instead of doubling or triple the time to have more air for unforeseen
+challenges I'm now even tighter, so that I probably will end up again working a lot of hours for free to get all done.
+But I still hope to safe enough time to get this milestone done, too.
+
+<details>
+<summary>View tasks</summary>
+
+| Task | Hours | Sessions |
+|------|-------|----------|
+| Analyze Monero source dependencies | 20 | 10 |
+| Remove unnecessary dependencies | 20 | 10 |
+| Optimize remaining code | 10 | 5 |
+| Document changes and rationale | 16 | 8 |
+| Analyze minimal resources needed for OTS library on restricted devices | 8 | 4 |
+| PR process revisions and merge | 8 | 4 |
+
+</details>
+
+### 10. (Stretch) Xmr Signer Pure (Rewrite in C++) (98 hours)
+
+If I have the mega flow, I will continue here to move substitute the Python code
+to C++. Why C++ and not Go or not Rust? First I'm still learning daily in C++, but
+the more important reason, I think there is a benefit in thinking on a bare metal
+XmrSigner NG in future. [circle](https://github.com/rsta2/circle) and [libcamera](https://github.com/rsta2/libcamera)
+would make it possible to run XmrSigner on bare metal what is a C++ environment...
+So done this here well, most of the work would be already done for the next step.
+
+<details>
+<summary>View tasks</summary>
+
+| Task | Hours | Sessions |
+|------|-------|----------|
+| Build environment | 6 | 3 |
+| Screen | 8 | 4 |
+| UI | 12 | 6 |
+| Logic | 20 | 10 |
+| OTS | 4 | 2 |
+| CBOR | 8 | 4 |
+| BCUR | 8 | 4 |
+| Zxing | 12 | 6 |
+| Cam | 20 | 10 |
+
+</details>
+
+### 11. (Stretch) JNI classes (44 hours)
+
+This is another thing I wanted to include but the time constraints will probably not allow it.
+One to have a second language using the C ABI with documentation, and second to be used
+for Android apps.
+
+<details>
+<summary>View tasks</summary>
+
+| Task | Hours | Sessions |
+|------|-------|----------|
+| Design Java class structure | 10 | - |
+| Implement Java wrapper classes | 20 | - |
+| Create Java documentation | 10 | - |
+| Develop unit tests for Java classes | 4 | 44 |
+</details>
+
+## Total Estimated Time
+
+Core Milestones (1-8): 392 hours
+Optional/Stretch Milestones (9-11): 224 hours
+Grand Total: 616 hours
+
+*Note: This timeline is an estimate and may be subject to adjustments as the project progresses. The sessions are based on the Pomodoro technique to maintain high focus and productivity throughout the project.*
+  
+Given the significant time investment and potential challenges ahead, I
+propose a shift from my usual value-based pricing to an monthly rate for
+this project.
+
+Proposed terms:
+- 65 Promodoro Sessions (130 hours) per month for three months (196 sessions in total, first month one extra session)
+- Compensation: 1 XMR per session, making 66 XMR first and 65 XMR second and 65 third month. (196 in total)
+- I would kindly request a 20 xmr upfront on start from the first month.
+- Total compensation: 196 XMR
+
+Hours worked beyond in the running month shall roll over to the next month. If I can work some time out I will work
+on the optional/strech goals. If time is missing to get milestone 1-8 done in the calculated hours, I will work hours for free to get it done - I always do.
+
+I will commit every day my work, on starting each repository I will advertise them here in a comment an push my commits every day.
+And I will create a repository/blog or something as a daily logbook to document the work done and the daily progress.
+
+<details><summary>I set up a [website](https://diosdelrayo.github.io) which syncronizes my actual pomodoro sessions, and the last 48 hours the work done</summary> on which tasks and how many sessions, even each unit time, so it is more transparent. On the way I plan to render also all tasks with the total time and a calendar. But the raw data is available in the issues of the [github repository](https://github.com/DiosDelRayo/DiosDelRayo.github.io) of the site. The time worked on each task can be calculated by the label and unlabeling of `WIP` label is start to work and unlabel end of work on it.
+</details>

vd-wallet-sdk-android.md

@@ -11,8 +11,8 @@ milestones:
     status: finished
   - name: Security Enhancements
     funds: 24 XMR
-    done:
-    status: unfinished
+    done: 12 August 2024
+    status: finished
   - name: Continuous Integration & Testing
     funds: 51 XMR
     done:
@@ -28,8 +28,8 @@ milestones:
 payouts:
   - date: 21 March 2024
     amount: 180
-  - date:
-    amount:
+  - date: 14 August 2024
+    amount: 24
   - date:
     amount:
   - date:

vtnerd-2024-q3.md

 ---
-layout: wip
+layout: cp
 title: vtnerd full-time 2024 q3
 author: Lee Clagett (vtnerd)
 date: July 11, 2024
@@ -7,24 +7,23 @@ amount: 208.12 XMR
 milestones:
   - name: Month 1 (160 hours)
     funds: 69 XMR
-    done:
-    status: unfinished
+    done: 24 August 2024
+    status: finished
   - name: Month 2 (320 hours)
     funds: 69 XMR
-    done:
+    done: 03 October 2024
     status: unfinished
   - name: Month 3 (480 hours)
     funds: 70.12
-    done:
-    status: unfinished
-
+    done: 22 November 2024
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 4 September 2024
+    amount: 69
+  - date: 26 October 2024
+    amount: 69
+  - date: 6 December 2024
+    amount: 70.12
 ---
 
 3-Months full-time software development on monero "core" components in 2024 q3.

vtnerd-2025-q1.md

+---
+layout: wip
+title: vtnerd full-time 2025 q1/q2
+author: Lee Clagett (vtnerd)
+date: February 21, 2025
+amount: 134.37 XMR
+milestones:
+  - name: Month 1 (160 hours)
+    funds: 44.79 XMR
+    done:
+    status: unfinished
+  - name: Month 2 (320 hours)
+    funds: 44.79 XMR
+    done:
+    status: unfinished
+  - name: Month 3 (480 hours)
+    funds: 44.79
+    done:
+    status: unfinished
+payouts:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+3-Months full-time software development on monero "core" components in 2025 q1/q2.
+
+## What
+Work primarily on `monerod`, `wallet`, and `monero-lws`. Some of the work to be attempted or investigated:
+  - Code reviews of monero core PRs
+  - monerod/monero-lws bug fixes and HackerOne mitigations as they arrive
+  - Keep existing PRs up-to-date:
+    - New Serialization routine
+    - Change from raw pointers to weak_ptrs in levin code
+    - Socks v5
+    - P2P SSL Support
+    - Updating levin callbacks to C++14 moves
+    - Embargo timeout fix
+  - Find (possible) memory leak in weak_ptr PR
+  - Complete work necessary to merge [DANE/TLSA in wallet2/epee](https://github.com/vtnerd/monero/tree/improve/dane_tlsa).
+  - Adding trust-on-first-use support to wallet2
+  - Add msgpack support to monerod-ZMQ (requires merging of new serialization system)
+  - `monero-lws` work:
+    - Determine a “push” interface for LWS clients (instead of existing poll interface)
+    - Complete LWS frontend (using `wallet_api.h` as interface) so that wallets can begin using LWS API easily. This is separate from woodser et al working on LWS API within `wallet2` which may be deprecated.
+    - Add a new utility (to LWS-frontend) that accepts a spend key to report balance+spent transactions of wallet (requested via Github Issues). This will help verify accuracy of LWS endpoints
+    - Update LWS spec and implementation to support new "carrot" features (view-balance key, etc)
+    - Update LWS backend to work with fcmp++ experimental branch
+    - Add a "scale" factor to remote scanning load balancing - send more accounts to systems with faster single thread performance 
+    - Add 64-bit ed25519 code for faster arm64 scanning
+    - Provide official LWS docker-image
+    - Provide pre-built binaries
+    - (Unlikely) - reproducible builds so community members can verify+sign the binary hashes
+
+There is intentionally more work than time allows - to ensure there is always something to work on in the proposal.
+
+## Who
+
+Lee Clagett (vtnerd). I've [had](https://ccs.getmonero.org/proposals/vtnerd-tor-tx-broadcasting.html) [five](https://ccs.getmonero.org/proposals/vtnerd-2020-q4.html) [CCS](https://ccs.getmonero.org/proposals/vtnerd-2021-q1.html), [proposals](https://ccs.getmonero.org/proposals/vtnerd-2023-q3.html) ([last one](https://ccs.getmonero.org/proposals/vtnerd-2024-q3.html)), and [one Magic Grant](https://monerofund.org/projects/Q1Q2_2024_dev_vtnerd).
+
+Some of my biggest features in monero core repo are [Dandelion++](https://github.com/monero-project/monero/pull/6314), [adding supercop ASM speedups to wallet code](https://github.com/monero-project/monero/pull/6337), [ZeroMQ Pub Support for new blocks and transactions](https://github.com/monero-project/monero/pull/6418), and [SSL support to p2p](https://github.com/monero-project/monero/pull/8996).
+
+I've also made a functional LWS wallet scanner under CCS/Magic - which now has a MyMonero compatible REST API (now fully non-blocking to support more responses per thread), admin REST API, LMDB storage, subaddress support, webhook/zmq/rmq publishing (new receives, spends, and accounts), multi-machine scanning with (primitive) load-balancing, and an untrusted daemon mode that verifies PoW is valid (whereas normal wallets trust `monerod` responses entirely).
+
+## Proposal
+
+Work on the various tasks outlined above for 40 hours/week over the next 3 months after potential funding. I already use time-tracking software for work; if the hours dip in a given month unexpectedly, the update/milestone will be at the completion of the hours listed above.
+
+The funds were calculated with 65 USD/hour with ~232.20 USD/XMR which is the 14-day exponential moving average on Kraken through 2025/02/21.

wobole-german-translation-subtitles.md

 ---
-layout: wip
+layout: cp
 title: German translation of Monero Means Money (subtitles) and Sound Money, Safe Mode (subtitles)
 author: Wobole
 date: June 27, 2021
@@ -20,6 +20,17 @@ payouts:
     amount:
 ---
 
+
+## Proposal Update 2024/09/05
+
+- Wobole completed this proposal Jan 22, 2022 as confirmed independantly by 2, native german, community members.
+- A partial address was posted in [this payout request](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/237#note_21125). 
+- The full address was never shared with Luigi or the acting CCS Coordinator at that time.
+- Wobole has 1 year from now, to attempt to claim these funds by pasting a _new_ payout address from the same Gitlab account. 
+- After 2025-09-05 the entire balance (9.9 XMR) will be returned to the General Fund.
+
+---
+
 Hello everybody, this is Wobole again :)
 
 ## What and Why

xiphon-7.md

 ---
-layout: wip
+layout: cp
 title: xiphon full-time coding (3 months)
 author: xiphon
 date: 6 Feb 2021
@@ -26,6 +26,19 @@ payouts:
     amount:
 ---
 
+### Proposal closed
+
+The remaining funds (121XMR) have been donated to the general fund.
+
+- Xiphon has not been seen/heard of for >2 years.
+- This proposal has been abandonned.
+- Xiphons total earnings from the CCS (year/xmr/price on day of payout(s))
+  - 2019: 190, $12533.36 USD
+  - 2020: 1051, $86310.75 USD
+  - 2021: 222.0, $56598.92 USD
+- Should they re-appear they are welcome to create a fresh proposal.
+
+
 # What
 
 Would love to prolong my Monero coding for another 3 months and dedicate 40h/week, i.e. to work full-time.

xmrchat.md

+---
+layout: wip
+title: XMRChat - a service for content creators to receive messages and tips in Monero.
+author: FiatDemise
+date: December 8, 2024
+amount: 114
+milestones:
+  - name: Milestone 1 - MVP (minimum viable product) using LWS
+    funds: 40
+    done: August 4, 2024
+    status: finished
+  - name: Milestone 2 - video display of xmrchats with Streamyard and OBS, find creator page, private xmrchats, making repo open source
+    funds: 30.56
+    done: November 20, 2024
+    status: finished
+  - name: Milestone 3 - creator specific minimum tip amount, links to more creator content + new tab UI for that and other settings, audio tip received notification, How To section in FAQ, old xmrchats expiration, admin page, site monitoring.
+    funds: 17
+    done:
+    status: unfinished
+  - name: Milestone 4 - on screen special effects and notifications based on tip tier, moderator / cohost page, feature currently live streams, fee system
+    funds: 27
+    done:
+    status: unfinished    
+payouts:
+  - date: 19 March 2025
+    amount: 70.56
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+_Note: 70.56XMR has been awarded to XMRChat from [TipXMR](https://ccs.getmonero.org/proposals/tipxmr.live.html)_
+
+Who?
+
+Douglas Tuman - Host of popular YouTube show, Monero Talk. Host of weekly show Monerotopia livestreamed in multiple platforms. Creator of Monerotopia annual conference - monerotopia.com. Creator of the Copamonero annual Monero-sponsored soccer tournament - copamonero.com. Sets up booth/tent at Libertarian party conventions and Porcfest to spread Monero awareness. Creator of gratuitas.org coffee beans business (and coffee brewer/bartender at XMR meetups/conventions. Founder of xmrbazaar.com online, p2p marketplace. Founder of plug-n-play XMR node implementation, the Nodo - moneronodo.com. X handle @DouglasTuman.
+
+FiatDemise - Guy with project management experience that joined the Monero community in 2020. Helped save Kuno (kuno.anne.media) and volunteers time there as a moderator. Contributed to testing and provided feature feedback for xmrbazaar. Created a Monero for All brochure that is available in several languages and was distributed at Porcfest 2024. X handle @FiatDemise.
+
+Saeed - Front-end web developer found via Monero Jobs & Proposals Telegram group, GitHub https://github.com/sa8ab. Developed dex alcor.exchange, github.com/avral/alcor-ui. Created raceroms.com. Has a network of other front and back end developers he partners with.
+
+What?
+
+XMRChat is website that provides content creators with a service, allowing them a way to receive messages and tips in Monero. We launched https://xmrchat.com/ on 8/4/2024, using it for the first time in MoneroTopia episode 177, where Doug interviewed Saeed, going over the project and what the site is capable of. https://www.youtube.com/watch?v=f1sy8ICsgBQ. We are looking to raise a total amount of 114 XMR at this time, split in 4 milestones as seen above.
+
+Website: https://xmrchat.com/
+X Account: https://x.com/xmr_chat
+Code: https://github.com/sa8ab/xmrchat
+
+How we got started?
+
+In early 2024, FiatDemise was watching a streamer, one that accepts tips from viewers and reads their messages as part of their show. They accept fiat using YouTube Superchats, Rumble Rants, and Streamlabs. They publicly stated they’d like to accept crypto too. FiatDemise started a conversation with their staff to try to get them to use Luke Smith’s Shadowchat. FiatDemise volunteered to pay for a company to install and configure it too. After some promising back and forth, FiatDemise got a response saying the team’s web dev / admin was too busy with current projects and they didn’t want to devote any time towards installing or managing Shadowchat. FiatDemise learned that the market wanted a very simple solution that doesn’t require any installation, hosting, or technical knowledge.
+
+At the time, FiatDemise was volunteering as a tester for xmrbazaar and raised the idea of a simple, hosted superchat solution in that Matrix group. Doug supported it right away, and we began working on requirements and giving shape to the vision with a Balsamiq wireframe. We worked with one developer to create a rough proof of concept. Then we found Saeed, a talented developer who could take the project to the next level. We saw the limitation of RPC, only being able to monitor incoming tips for one wallet, which wouldn’t work with the goal of hosting a solution for many content creators. After research, trial and error, and consultations with VTNerd and Radanne, we got LWS to work. After several more updates, the MVP was launched.
+

xmrhaelan-monero-outreach-round-3.md

 ---
-layout: wip
+layout: cp
 title: Monero Outreach Round 3
 author: xmrhaelan
 date: 22 May 2019
@@ -22,10 +22,14 @@ payouts:
     amount: 36.66
   - date: 23 November 2020
     amount: 36.67
-  - date: TBD
+  - date:
     amount: 36.67
 ---
 
+### Proposal closure/repurposed
+
+_All remaining funds (36.67 XMR) have been transferred to [Monerotopia 2024 marketing and publicity](https://ccs.getmonero.org/proposals/monerotopia2024publicity.html)_
+
 A big thanks again to everyone who supported Round 2 of funding for Monero Outreach! Final report can be found [here](https://www.reddit.com/r/Monero/comments/bonpt3/monero_outreach_round_2_ccs_final_report_see_what/). 
 We have made significant progress in our ability to support and enhance the outreach efforts of the Monero Community, and are beginning to receive requests for support from various areas of the Monero ecosystem. We are honored to be able to support Monero in this way, and we look forward even more to what is ahead!