seraphis-poc.md

 ---
-layout: wip
+layout: cp
 title: "koe: Seraphis Proof-of-Concept"
 author: koe
 date: 1 October 2021
@@ -7,9 +7,11 @@ amount: 92.6
 milestones:
   - name: PoC
     funds: 100% (92.6 XMR)
-    done: 
-    status: unfinished
+    done: 22 February 2022
+    status: finished
 payouts:
+  - date: 25 April 2022
+    amount: 92.6
 ---
 
 ## Intro

seraphis-wallet-poc-2.md

+---
+layout: wip
+title: "koe: Seraphis Wallet Proof-of-Concept 2"
+author: koe
+date: 1 May 2022
+amount: 155
+milestones:
+  - name: PoC
+    funds: 100% (155 XMR)
+    done: 
+    status: unfinished
+payouts:
+---
+
+## Intro
+
+Hi all, I [closed out](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/290#note_16046) my previous [Seraphis Wallet PoC CCS](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/290) after consuming all the hours. There are additional tasks I would like to work on. For background on this CCS, please see the links in the previous sentence.
+
+
+## Continuing work
+
+Here are the tasks I hope to finish by the end of this CCS. As before, these will be implemented in my [seraphis_lib](https://github.com/UkoeHB/monero/tree/seraphis_lib) branch.
+
+- Add tx builder plumbing for _discretized_ tx fees (see the [04/20/22 MRL meeting](https://github.com/monero-project/meta/issues/691) for a discussion).
+- Consider using 16-byte address indices (instead of 7), with 2-byte encoded address index MACs (instead of 1).
+- Implement a robust 'input selection' solver that takes advantage of statically-determinable tx weights.
+- Implement a maximally-efficient and generic enote-scanning workflow.
+- Build a wallet proof-of-concept that demonstrates all the 'transaction engineering' capabilities and implementation modularity of Seraphis/Jamtis. My goal is to have unit tests representing all the main workflows possible with Seraphis, and all the main wallet implementations necessary (i.e. mock-ups of interfaces that could potentially be developed into full-fledged wallet software).
+- Test out using x25519 for enote ECDH instead of ed25519, which may speed up enote scanning by a non-trivial amount (>10%).
+- Miscellaneous code cleanup (mostly update/add comments, cleanup TODOs).
+
+As usual, I will also lump all the miscellaneous Monero R&D tasks that I work on into this CCS (e.g. in the last period I did more review/work on multisig security patches, among other things).
+
+
+## Funding
+
+- Rate: 50 USD + 0.2 XMR
+- Hours: 16 weeks @ 20hr/wk = 320hrs
+- XMR equivalent: 64 + (50\*320)/USD\_EXCHANGE\_RATE XMR
+- USD\_EXCHANGE\_RATE: set from 14-day EMA on a major exchange
+  - 175 USD/XMR at 0100 UTC 05/16/2022 w/ 14-day EMA on Kraken -> 155 XMR total
+
+If I require more time, and the community supports it, then I may make another proposal to extend the hours.

seraphis-wallet-poc.md

 ---
-layout: wip
+layout: cp
 title: "koe: Seraphis Wallet Proof-of-Concept"
 author: koe
 date: 23 February 2022
@@ -7,9 +7,11 @@ amount: 81.4
 milestones:
   - name: PoC
     funds: 100% (81.4 XMR)
-    done: 
-    status: unfinished
+    done: 25 April 2022
+    status: finished
 payouts:
+  - date: 12 May 2022
+    amount: 81.4
 ---
 
 ## Intro

soloptxmr-mj-endor-2022.md

 ---
-layout: fr
+layout: wip
 title: SolOptXMR - Solar Optimal mining of XMR
 author: mj
 date: Mar 26, 2022
@@ -7,8 +7,8 @@ amount: 110.55 XMR
 milestones:
   - name: 1 Initial setup
     funds: 20.10 XMR
-    done:
-    status: unfinished
+    done: 29 May 2022
+    status: finished
   - name: 2 Profitability calculator
     funds: 16.75 XMR
     done:
@@ -22,8 +22,8 @@ milestones:
     done:
     status: unfinished
 payouts:
-  - date:
-    amount:
+  - date: 2 July 2022
+    amount: 20.1
   - date:
     amount:
   - date:

tobtoht-feather-dev-2021-3.md

 ---
-layout: wip
+layout: cp
 title: "Continued Feather Wallet development (3 months)"
 author: tobtoht
 date: 1 Nov 2021
@@ -7,23 +7,19 @@ amount: 93
 milestones:
   - name: First month 
     funds: 33% (31 XMR)
-    done: 
-    status: unfinished
+    done: 8 July 2022
+    status: finished
   - name: Second month
     funds: 33% (31 XMR)
-    done: 
-    status: unfinished
+    done: 8 July 2022
+    status: finished
   - name: Third month
     funds: 33% (31 XMR)
-    done: 
-    status: unfinished
+    done: 8 July 2022
+    status: finished
 payouts:
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 16 July 2022
+    amount: 93
 ---
 
 ### What

tobtoht-feather-dev-2022-1.md

+---
+layout: fr
+title: "Continued Feather Wallet development (3 months)"
+author: tobtoht
+date: 20 Jul 2022
+amount: 162
+milestones:
+  - name: First month 
+    funds: 33% (54 XMR)
+    done: 
+    status: unfinished
+  - name: Second month
+    funds: 33% (54 XMR)
+    done: 
+    status: unfinished
+  - name: Third month
+    funds: 33% (54 XMR)
+    done: 
+    status: unfinished
+payouts:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+### What
+
+This CCS proposal is for 3 months of full time Feather Wallet development.
+
+Non-exhaustive list of things I want to work on/towards or experiment with:
+
+- Bootstrappable builds
+  - Leverage [Guix](https://github.com/bitcoin/bitcoin/tree/master/contrib/guix) to produce cross-compiled, reproducible, [bootstrappable](https://bootstrappable.org/) builds for all target platforms and operating systems. Most of the work for this is already [done](https://github.com/feather-wallet/feather/pull/20). This has the added benefit of greatly speeding up release engineering, allowing for quicker release cycles.
+
+- Offline transaction signing using animated QR codes
+  - Export/import outputs, key images and transactions using animated QR Codes based on Blockchain Common's [Uniform Resources](https://github.com/BlockchainCommons/bc-ur).
+  - Work with the [Keystone](https://keyst.one/) team to add support for Monero and integrate with Feather.
+
+- Multi-node syncing (experiment)
+  - Syncing a month worth of blocks now requires more than 300 MB of data. Wallet synchronization (when connected to a remote node) is often limited by one of two things: your download speed or a node's upload speed (for mobile devices your CPU might play a role too). Multi-node syncing will experimentally determine the fastest nodes from your node list and automatically gather blocks from the highest performing nodes to utilize as much of your available bandwidth as possible. If you are on a fast internet connection this can result in dramatically faster syncing.
+
+- Allow skipping synchronization
+  - POV: You just opened your wallet on Tails after leaving it unopened for 3 months. You proceed to wait an hour or more for your wallet to synchronize knowing that there has been no activity. An advanced option to skip synchronization will eliminate the wait and allow you to send transactions almost immediately.
+
+- Improve Tor support and add support for more anonymity networks
+  - Add support for Tor bridges and stream isolation
+  - Switch the Tor client implementation to [Arti](https://blog.torproject.org/announcing-arti/) (when it is ready)
+  - Remove the hard dependency on Tor and allow Feather to be used without anonymity networks
+  - Modularize the anonymity network code to make it possible to integrate other networks like I2P and [Nym](https://github.com/nymtech/nym).
+
+- Mining interface overhaul (+ P2Pool support)
+  - The Mining tab is a bit crude. Mining is [not trivial](https://docs.featherwallet.org/guides/mining-setup) to set-up for new users, and it lacks configurability for advanced users. It's currently not possible to mine without having a wallet open. I want to move the Mining tab to a utility that can be accessed via the taskbar icon. Users should be able to quickly setup P2Pool, solo and pool mining. Feather will be able to run in the background and allow users configure scheduled mining, as well as provide a dashboard where users can check their mining stats and make changes to the configuration.
+
+- Improve packaging for Linux distributions
+  - Make Feather available as a Flatpak, Debian package, and maintain a working -bin package on the AUR. I also want to work on documentation that will help maintainers package Feather for their distribution.
+
+- Support more ways of spending Monero
+  - The libwallet interface lacks support for various advanced ways of spending Monero. The current Feather release added manual input selection. More is still desired, such as multi-destination sweeps or spends with an alternative change address.
+
+- Improved documenatation
+  - I'm already quite happy with the [documentation](https://docs.featherwallet.org/) in it's current state, but there is still room for improvement. A search feature is lacking and some parts could be improved with screenshots. Other parts can be rewritten to improve clarity and a glossary would be a welcome addition. I also want to add a section that goes in depth about threat-modeling to help users make more informed decisions about how they should use and configure the program to address their specific privacy or security concerns.
+
+- Fix bugs and issues as they arise
+
+I'll also work on reviewing contributions to CLI / GUI where I can and work on upstreaming patches to core.
+
+As always I will heavily prioritize user feedback when deciding what to focus on.
+
+### Who
+
+Hi, I'm tobtoht. I am an active contributor to the Monero ecosystem since April 2018. Currently, I maintain Feather Wallet and contribute to the core codebase.
+
+Previous CCS proposals:
+
+- https://ccs.getmonero.org/proposals/tobtoht-feather-dev-2021-3.html
+- https://ccs.getmonero.org/proposals/tobtoht-feather-dev-2021-2.html
+- https://ccs.getmonero.org/proposals/tobtoht_feather_dev_q1_2021.html
+- https://ccs.getmonero.org/proposals/feather-2020.html
+
+### Proposal
+
+Work 40 hours per week over the next 3 months at a rate of €45 / hour. At €133 / XMR (14 day EMA) this makes 162 XMR.

unstoppableswap-gui-2.md

+---
+layout: wip
+title: "XMR BTC Atomic Swaps Desktop GUI - Continued development for 4 months"
+author: binarybaron
+date: 26 May, 2022
+amount: 232
+milestones:
+  - name: July
+    funds: 58
+    done:
+    status: unfinished
+  - name: August
+    funds: 58
+    done:
+    status: unfinished
+  - name: September
+    funds: 58
+    done:
+    status: unfinished
+  - name: October
+    funds: 58
+    done:
+    status: unfinished
+payouts:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+  - date:
+    amount:
+---
+
+![](https://user-images.githubusercontent.com/86064887/152649852-4c8c6c3f-0568-4347-89d1-c291c17f2d30.png)
+![](https://user-images.githubusercontent.com/86064887/152678743-b86f395e-01dc-43c5-ba71-b27962a4a6ba.png)
+![](https://user-images.githubusercontent.com/86064887/152649633-9ae29f79-8041-476c-be45-ef3441f4dee1.png)
+
+We've successfully completed all of the goals we set for ourselves in our [first CCS proposal](https://ccs.getmonero.org/proposals/binarybaron-unstoppableswap.html). The prototype of the GUI we wanted to develop is fully functional (on testnet) and it will soon replace the now obsolete web interface ([UnstoppableSwap.net](https://unstoppableswap.net)).
+Based on the community response to both of our status updates ([reddit post 1](https://www.reddit.com/r/Monero/comments/slvy2a/making_atomic_swaps_accessible_to_all/), [reddit post 2](https://www.reddit.com/r/Monero/comments/uawipv/atomic_swap_gui_demo_on_mainnet_unstoppableswap/)), we felt that there is a strong desire in the community for us to continue development.
+
+Over the course of 7 months we have:
+
+- Made over **175 commits** to the [UnstoppableSwap GUI repository](https://github.com/UnstoppableSwap/unstoppableswap-gui/commits/main) and developed an initial working prototype.
+    - [Demo video of mainnet swap](https://www.youtube.com/watch?v=8XLGSsggnP0)
+    - [Demo video of decentralized peer discover](https://www.youtube.com/watch?v=MvUsjU67jf0)
+- I’ve become one of the three unpaid volunteers maintaining the [xmr-btc-swap](https://github.com/comit-network/xmr-btc-swap/) repository after the comit guys (original developers who developed the first MVP) have moved on to other projects. I’ve submitted and merged [12 Pull Requests](https://github.com/comit-network/xmr-btc-swap/pulls?q=is%3Apr+is%3Amerged+author%3Abinarybaron+) over the last months and reviewed some more.
+
+### Proposal:
+
+We are excited to keep working on Atomic Swaps. There are still loads of things needed to make it accessible and easy to use for everyone. Therefore we'd like to continue spending our time working on the FOSS GUI for BTC<>XMR Atomic Swaps. It is being built around the *[swap-cli](https://github.com/comit-network/xmr-btc-swap/blob/master/docs/cli/README.md)* and will empower even non-technical people to swap their BTC for XMR in a safe, decentralized and trustless manner. We are asking for 232 XMR for continued development for 4 months. At the end of each month 37 XMR will be paid out. We will work approximately 25 hours per week for 4 months straight which amounts to 400 hours of labour. Our hourly rate is 66 USD which amounts to 232 XMR at a current price of 112 XMR/USD
+
+### Who:
+I am binarybaron, the creator of UnstoppableSwap.net and Monero enthusiast. I was excited about Atomic Swaps from the very beginning, tested the first versions (MVP developed by COMIT guys) and contributed to the project early on. When the first testnet swap provider came online, I realized that we would need a better user interface and a platform to compare different swap providers. I decided to start building UnstoppableSwap.net. To my surprise, the interest was much greater than I could have ever predicted. In the first week alone, the website was visited more than 150,000 times. 
+Once I realized that a website was not enough due to the technical requirements, I started working on a desktop app. Soon after, I submitted my first CCS, which was quickly funded, and developed the first working prototype of the desktop user interface.
+
+### **What:**
+
+1. Development of the graphical user interface (*[GUI](https://github.com/UnstoppableSwap/unstoppableswap-gui)*)
+    1. **Auto Update**. For this to work we’ll need to code sign the releases on Mac OS using a paid certificate. The *GUI* will download and install the new version on startup if a new release is available. 
+    2. **Educate users on the rules of the swap protocol.** There are some simple but important rules all users need to follow to avoid loosing funds. Most importantly the functionality of the cancel and refund timelocks must be understood. If users are not fully aware on how to act in certain scenarios, **they risk loosing funds**. We’re not yet sure how to proceed on this. Some ideas are outlined below:
+        1. Quiz at first start-up to make sure the user understands what rules he needs to follow
+        2. Refer to official documentation of the *[swap-cli](https://github.com/comit-network/xmr-btc-swap/blob/master/docs/cli/README.md)* and the GUI
+        3. Refer to blog posts, videos and other online resources by the community
+    3. **Allow manual cancel & refund of swaps.** Although the *[swap-cli](https://github.com/comit-network/xmr-btc-swap/blob/master/docs/cli/README.md)* should refund swaps automatically in most cases, there are some edge cases where the user is required to cancel & refund manually. This is currently not possible in the GUI. Enabling the user to easily do this in the GUI is a must.
+    4. **Unit and Integration tests.** Although the *GUI* is relatively stable, it has pretty low test coverage. We need to create a lot more unit and possibly integration tests to cover all edge cases. Especially critical code like the internal finite state machine needs extensive test coverage.
+    5. **New Icon**. The current icon was only meant to be a placeholder and wasn’t intended to be final. We’ll either commision someone to make a new one or ask the community for input.
+    6. **Performance improvements.** We need to investigate what the performance bottlenecks of the *GUI* are. The most obvious ones at the moment are:
+        1. Inefficient SQL queries being used for querying the swap database
+        2. Overly-cautious file reads of the swap database
+        3. Unnecessary re-renders of React components
+        4. Blocking code being run in the main thread leading to freezing of the whole application
+    7. **General improvement of the GUI**. Fixing bugs, responding to issues, writing documentation and implementing new features as they come to mind.
+    8. **Switch the GUI from Testnet to Mainnet.** The GUI is currently Testnet only. Once we feel it is stable enough overall we’ll switch it over to Mainnet.
+2. **Development and maintenance of the API that enables clients to easily discover swap providers.** A swap provider is a peer you can connect with to exchange your BTC for XMR. ****Our API indexes them and provides additional data such as their uptime and their age. This API is publicly accessible and can be used by other services (e.g orangefren.com). We provide an HTTP(s) and a WebSocket (socket.io) endpoint which will be documented on UnstoppableSwap.net.
+3. **Development and maintenance of the UnstoppableSwap.net site.** It was the first initial prototype for a user interface for Atomic Swaps. It used to be a very stripped down version of the GUI and allowed users to more easily initiate a swap using the *[swap-cli](https://github.com/comit-network/xmr-btc-swap/blob/master/docs/cli/README.md)* by displaying them with a command they could copy and paste. This was not ideal, as it gave the impression of being user-friendly, but could be quite confusing and risky to use. The site will be converted into a simple download page for the *GUI* (similar to bisq.network)
+4. **Maintenance of rendezvous point.** There are currently three major ways for users to discover swap providers (peers they can swap their Bitcoin for Monero with). This proposal also includes the maintenance of the rendezvous point we run.
+    1. Word-of-mouth: The community can share the address of swap providers online (e.g on Reddit, IRC, Matrix..)
+    2. Centralized peer discovery via UnstoppableSwap API: We actively maintain a database of swap providers which can be used by anyone to retrieve a list of swap providers
+    3. Rendezvous point: The [rendezvous](https://github.com/libp2p/specs/blob/master/rendezvous/README.md) protocol is a lightweight mechanism for generalized peer discovery. It allows for the discovery of peers in a decentralized fashion. We operate a community rendezvous point through which swap providers can make themselves known to users, and through which users can find swap providers with whom they want to swap.(`/dns4/discover.unstoppableswap.net/tcp/8888/p2p/12D3KooWA6cnqJpVnreBVnoro8midDL9Lpzmg8oJPoAGi7YYaamE`)
+5. **Reviewing, merging and possibly submitting Pull Requests to the [xmr-btc-swap](https://github.com/comit-network/xmr-btc-swap/) repository.**
+    1. This proposal is mainly for continued development of the GUI and not for maintenance of the xmr-btc-swap project. **Time spent on the [repository](https://github.com/comit-network/xmr-btc-swap/) will at most be 5% of the total time spent on this proposal.**
+    2. Most of the Pull Requests we’ll submit will be related to making the *[swap-cli](https://github.com/comit-network/xmr-btc-swap/blob/master/docs/cli/README.md)* compatible with the *GUI*
+    
+
+If funded we'll provide monthly updates in the CCS comment section.

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

@@ -16,17 +16,17 @@ milestones:
   - name: April
     funds: 16.66% (10.3 XMR)
     done: April 30, 2022
-    status: unfinished
+    status: finished
   - name: May
     funds: 16.66% (10.3 XMR)
     done: May 31, 2022
-    status: unfinished
+    status: finished
   - name: June
     funds: 16.66% (10.3 XMR)
     done: June 30, 2022
-    status: unfinished
+    status: finished
   - name: July
-    funds: 16.66% (10.3 XMR)
+    funds: 16.66% (10.5 XMR)
     done: July 31, 2022
     status: unfinished
 payouts:
@@ -34,12 +34,12 @@ payouts:
     amount: 10.3
   - date: 2 April 2022
     amount: 10.3
-  - date:
-    amount:
-  - date:
-    amount:
-  - date:
-    amount:
+  - date: 2 May 2022
+    amount: 10.3
+  - date: 9 June 2022
+    amount: 10.3
+  - date: 6 July 2022
+    amount: 10.3
   - date:
     amount:
 ---

vtnerd-2021-q1.md

@@ -7,7 +7,7 @@ amount: 133.4 XMR
 milestones:
   - name: Month 1 (160 hours)
     funds: 44 XMR
-    done:
+    done: 09 April 2021
     status: unfinished
   - name: Month 2 (320 hours)
     funds: 44 XMR