Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • monero-project/ccs-proposals
  • rehrar/ccs-proposals
  • DSal/ccs-proposals
  • el00ruobuob/ccs-proposals
  • TONGZHENGSHIJIE/ccs-proposals
  • SarangNoether/ccs-proposals
  • pwrcycle/ccs-proposals
  • onosendai/ccs-proposals
  • xeagu/ccs-proposals
  • b-g-goodell/ccs-proposals
  • xmrhaelan/ccs-proposals
  • moneromooo-monero/ccs-proposals
  • AcceptThisYouCensors/ccs-proposals
  • Needmoney90/ccs-proposals
  • erciccione/ccs-proposals
  • knueffelbund/ccs-proposals
  • xiphon/ccs-proposals
  • dsc/ccs-proposals
  • Codivorous/ccs-proposals
  • serhack/ccs-proposals
  • sgp/ccs-proposals
  • Kukks/ccs-proposals
  • gingeropolous/ccs-proposals
  • hyc/ccs-proposals
  • saumyabratadutt/ccs-proposals
  • kayront/ccs-proposals
  • rellis/ccs-proposals
  • Avantpay19/ccs-proposals
  • lazaridiscom/ccs-proposals
  • omani/ccs-proposals
  • JackBlack/ccs-proposals
  • Kyoto/ccs-proposals
  • Endogen/ccs-proposals
  • sri346/ccs-proposals
  • asymptotically/ccs-proposals
  • Avis/ccs-proposals
  • Monero/ccs-proposals
  • jtgrassie/ccs-proposals
  • Fudin/ccs-proposals
  • helloworld9998/ccs-proposals
  • lalanza808/ccs-proposals
  • TheCharlatan/ccs-proposals
  • atoc/ccs-proposals
  • randybrito/ccs-proposals
  • Ministo/ccs-proposals
  • objectorange/ccs-proposals
  • adrelanos/ccs-proposals
  • mj/ccs-proposals
  • MoneroAddict/ccs-proposals
  • h4sh3d/ccs-proposals
  • paulshapiro/ccs-proposals
  • pricode/ccs-proposals
  • naijaminer/ccs-proposals
  • niyiajayi/ccs-proposals
  • cryptosourov/ccs-proposals
  • Drowxes/ccs-proposals
  • Mon_icp/ccs-proposals
  • Madbu221b/ccs-proposals
  • suyash67/ccs-proposals
  • kdavid2008/ccs-proposals
  • xmrLovera/ccs-proposals
  • lh1008/ccs-proposals
  • jatinajwani/ccs-proposals
  • normoes/ccs-proposals
  • Wobole/ccs-proposals
  • lederstrumpf/ccs-proposals
  • AlexAnarcho/ccs-proposals
  • readifugly/ccs-proposals
  • binaryFate/ccs-proposals
  • oeAdgK01/ccs-proposals
  • nio21/ccs-proposals
  • michaelizer/ccs-proposals
  • janowitz/ccs-proposals
  • fleaw/ccs-proposals
  • gusan/ccs-proposals
  • Leo27/ccs-proposals
  • tobtoht/ccs-proposals
  • anon/ccs-proposals
  • panagot12/ccs-proposals
  • kysn/ccs-proposals
  • monerotesla/ccs-proposals
  • sahil07/ccs-proposals
  • xmronadaily/ccs-proposals
  • ClaytonBHooverIII/ccs-proposals
  • txstreet/ccs-proposals
  • Aron/ccs-proposals
  • jklein/ccs-proposals
  • wtii/ccs-proposals
  • alynoe/ccs-proposals
  • selsta/ccs-proposals
  • johnfoss67/ccs-proposals
  • benevanoff/ccs-proposals
  • op/ccs-proposals
  • cirocosta/ccs-proposals
  • ragazzo/ccs-proposals
  • 888/ccs-proposals
  • elibroftw/ccs-proposals
  • amr-monero/ccs-proposals
  • behash/ccs-proposals
  • AnonDev/ccs-proposals
  • Rucknium/ccs-proposals
  • rating89us/ccs-proposals
  • AdorableTanuki/ccs-proposals
  • neat/ccs-proposals
  • plowsoff/ccs-proposals
  • xmr_sale/ccs-proposals
  • escapethe3RA/ccs-proposals
  • DouglasTuman/ccs-proposals
  • Bl5ckj5ck/ccs-proposals
  • j-berman/ccs-proposals
  • CrypticEntertainments/ccs-proposals
  • Geroser/ccs-proposals
  • ava_haidang/ccs-proposals
  • pluja/ccs-proposals
  • msvblab/ccs-proposals
  • monerokage/ccs-proposals
  • noot/ccs-proposals
  • RogueMaven/ccs-proposals
  • xmrman/ccs-proposals
  • moneronews/ccs-proposals
  • spirobel/ccs-proposals
  • winstonsthiccbooty/ccs-proposals
  • help.ukraine/help-ukraine-to-use-monero
  • dangerousfreedom/ccs-proposals
  • moneroist/ccs-proposals
  • anon_/ccs-proposals
  • agustincruz/3-d-metal-printer-project
  • savandra/ccs-proposals
  • willk/ccs-proposals
  • max.zab/ccs-proposals
  • rimuru/ccs-proposals
  • CryptoMorpheus_/ccs-proposals
  • jeffro256_/ccs-proposals
  • m0n3r0d1c3/ccs-proposals
  • leonerone/ccs-proposals
  • marjorie69/ccs-proposals
  • monero_archive/monero-archive
  • forgotsudo/ccs-proposals
  • mikigrey321/ccs-proposals
  • anhdres/ccs-proposals
  • thelefterisjp/ccs-proposals
  • lescuer971/ccs-proposals
  • MoneroBro/ccs-proposals
  • rayatina/ccs-proposals
  • HoudiniSwap/ccs-proposals
  • nightwolf361/ccs-proposals
  • z00t/ccs-proposals
  • markofdistinction_/ccs-proposals
  • busyboredom/ccs-proposals
  • Mitchellpkt/ccs-proposals
  • Fierfek/p-2-p-publisher-monerotopia-mexico-city
  • BigmenPixel/ccs-proposals
  • cmiv/ccs-proposals
  • VOSTOEMISIO/ccs-proposals
  • valldrac/ccs-proposals
  • Titus/ccs-proposals
  • C0mradeBlin/ccs-proposals
  • kayabaNerve/ccs-proposals
  • Boog9001/ccs-proposals
  • 4rkal/ccs-proposals
  • binarybaron2/ccs-proposals-bb
  • ajs/ccs-proposals
  • sacatunquetun/ccs-proposals
  • vtnerd/ccs-proposals
  • 0xFFFC0000/ccs-proposals
  • Clodagh/ccs-proposals
  • mrcyjanek/ccs-proposals
  • detheforxmr/ccs-proposals
  • r4v3r23/ccs-proposals
  • janaka303/ccs-proposals
  • eyedeekay/ccs-proposals
  • Secrecy1337/ccs-proposals
  • rohanrhu/ccs-proposals
  • baldeagle/ccs-proposals
  • fengzie_mbz/mobazha-with-monero-in-privacy-ecommerce
  • freeross/ccs-proposals
  • DiosDelRayo/ccs-proposals
  • omnedeus/ccs-proposals
  • geonic/ccs-proposals
  • untraceable/ccs-proposals
  • ki9/ccs-proposals
  • monerobullgitlab/ccs-proposals
  • sybann/ccs-proposals-bb
  • hinto/ccs-proposals
  • HardenedSteel/ccs-proposals
  • Kewbit/ccs-proposals
  • plowsofff/ccs-proposals
  • mainnet-pat/ccs-proposals
  • SimplifiedPrivacy/ccs-proposal-carrot-animated-video
  • SimplifiedPrivacy/ccs-proposal-carrot-animated-video-b
  • SNeedlewoods/ccs-proposals
  • midipoet/ccs-proposals
  • soufiane/ccs-proposals
  • geonic1/ccs-proposals
  • v1docq47/ccs-proposals
  • fullmetalScience/ccs-proposals
  • FiatDemise/xmrchat
  • dadybayo/ccs-proposals
  • rottenwheel/ccs-proposals
  • napoly/ccs-proposals
  • techpopulus/marketplace-monero-techdaddi
  • hbs/ccs-proposals
  • acx/ccs-proposals
  • wallet-verse/ccs-proposals
  • N1co1asB1ancon1/monero-contract-system
  • SyntheticBird/ccs-proposals
  • NorrinRadd/ccs-proposals
207 results
Show changes
Showing
with 1433 additions and 62 deletions
---
layout: cp
title: "jeffro256: part-time dev work 2022Q3"
author: jeffro256
date: 17 May 2022
amount: 60
milestones:
- name: Month 1
funds: 33% (20 XMR)
done: 23 September 2022
status: finished
- name: Month 2
funds: 33% (20 XMR)
done: 19 November 2022
status: finished
- name: Month 3
funds: 34% (20 XMR)
done: 4 April 2023
status: finished
payouts:
- date: 24 October 2022
amount: 20
- date: 29 December 2022
amount: 20
- date: 11 May 2023
amount: 20
---
## What
I propose to spend 20 hours a week for 3 months working on Monero Core and the Monero GUI. Here are some areas, in tentative order of descending importance/specificity, that I'd work on:
1. Work with @selsta to protect GUI users in "simple mode" by implementing a trusted community node system
2. Create a RPC SSL connection integrity indicator for the CLI and GUI wallets
3. Allow GUI users more fine-grained control of their SSL connections
4. Create a more thorough UI for warning users of GUI mode of high fees
5. Draft a formal Levin/Cryptonote protocol specification
6. Revamp Doxygen documentation
7. Do other general documentation of the codebase
8. Transition legacy OpenSSL code to comply with OpenSSL 3.0 (already started)
9. Explore using faster & smaller EC OpenSSL certificates in place of traditional RSA certificates
10. Continue to remove dead code, and simplify codebase, especially the (epee module)[https://github.com/monero-project/monero/pull/8211]
12. Misc developing / reviews
## Who
My name is Jeffrey; I am currently working on completing a computer science major with a minor in both cybersecurity and mathematics. I have always been fascinated with cryptography and digital privacy, so learning about Monero during the altcoin boom of 2017 was eye-opening and exciting. Soon enough, supporting Monero became a no-brainer for someone who is passionate about digital privacy.
I got my first PR merged on March 18th, and you can see the rest of them here: <https://github.com/monero-project/monero/pulls?q=is%3Apr+is%3Amerged+author%3Ajeffro256>. So far I have been doing it as a hobby, but I would love to spend more time on this project than I currently am, as I am rather busy with schoolwork and my job. As this is my first CCS proposal, I am very open to criticism and questions, so don't be afraid to ask! I will do my best to respond in the comments below.
## Why
### Trusted community node system and high fees (1 & 4)
As can be seen in [this issue](https://github.com/monero-project/monero/issues/8298), among others, there appear to be malicious node(s) which advertise themselves as public nodes, allow users using the GUI wallet in "simple node" to connect, and respond with insanely high fees. This issue runs even deeper, and this exploit can be used to deanonymize GUI users to a certain degree in simple mode when they send transactions. There's no replacement for running your own node (and double-checking your fee amounts), but for those who choose not to, they should be able to expect at a minimum to not have their funds stolen from them.
### RPC connection integrity indicator and fine-grained SSL control (2 & 3)
Getting SSL right is difficult and nuanced. You can verify with system certificates, user-supplied certificates, accept any connection as long as it is secured, or any combination of these options. You can have certificates which sign other certificates. As it stands, the way the GUI wallet secures connections is not ideal. It more or less accepts any connection, using SSL if its available, but for no specific ccertificate, and there is not a way to specify how to connect with SSL (unlike in the CLI wallet). I want to afford the users two things: the ability to quickly asses the quality of their connections to their nodes via an elegant UI element, and the ability to tweak their SSL settings if so desired.
### Levin/Cryptonote Specification (5)
Unclear protocols cause bugs and choke out emerging projects which wish to incorporate into the ecosystem. Here are a couple recent PRs to fix bugs with the p2p/relay code:
* <https://github.com/monero-project/monero/pull/8330>
* <https://github.com/monero-project/monero/pull/8326>
* <https://github.com/monero-project/monero/pull/8324>
While it would be quite a feat to document ALL of the cryptonote protocol, it could be helpful to more thoroughly document the Levin protocol commands and the expectations surrounding the calls (interface, relay rules, ban criteria, etc). The p2p protocol of Monero is useful not only for nodes, but also for wallets and light wallet servers, especially when using untrusted connections. This was already started in [this document](https://github.com/monero-project/monero/blob/master/docs/LEVIN_PROTOCOL.md), but could certainly be fleshed out.
### OpenSSL 3.0 Compatibility (8)
It's always a nice thing to have your code compile on all your targets. In newer versions of OpenSSL, they have deprecated a large portion of the API, much of which we rely on to secure connections in Monero, particularly RPC.
### EC OpenSSL certificates (9)
Currently, we use RSA certificates for RPC SSL, but EC certificates are smaller and thus faster. This could offer speed improvements while syncing, etc. @HYC suggested the idea while I was working on moving certain parts of the codebase to OpenSSL 3.0: <https://github.com/monero-project/monero/pull/8335>.
### Nice-to-haves (6, 7, 10, 11)
All of these points do not directly affect the end-user experience but will ultimately improve the developer experience, reducing friction in the future, contributing to the long-term health of the codebase.
## Funding
* Wage: 30 USD/hr
* Hours: 12 weeks x 20 hours/week = 240 hours
* Total pay in USD: 240 hours x 30 USD/hr = $7200 USD
* Exchange rate: $116.41 USD/XMR. Calculated from one week simple average of closing prices on coinmarketcap.com
* 24 June: $126.47
* 23 June: $122.70
* 22 June: $111.18
* 21 June: $118.80
* 20 June: $117.30
* 19 June: $114.22
* 18 June: $104.18
* Total pay in XMR: $7200 USD / $116.41 USD/XMR = 61.85 XMR
Expiration Date
1 August, 2022
---
layout: cp
title: Retroactive funding for work on full-chain membership proofs
author: Luke Parker (kayabaNerve)
date: July 24, 2023
amount: 310 XMR
milestones:
- name: Implementation of Bulletproofs+
funds: 150 XMR
done: 23 June 2023
status: finished
- name: Implementation of Curve Trees
funds: 100 XMR
done: 23 June 2023
status: finished
- name: Application of elliptic curve divisors for multiple times faster proofs
funds: 50 XMR
done: 23 June 2023
status: finished
- name: Implementation of COPZ's efficient cross-group discrete log equality proof
funds: 10 XMR
done: 23 June 2023
status: finished
payouts:
- date: 21 March 2024
amount: 310
---
Prior to Monerokon, I spent a month and a half working on full chain membership proofs for Monero. This is the product of
- Discussions from https://github.com/monero-project/research-lab/issues/100
- Curve trees, as the fundamental idea https://eprint.iacr.org/2022/756
- Eagen's application of Elliptic Curve divisors https://eprint.iacr.org/2022/596
- COPZ's discrete log equality proof, letting us move to a curve cycle https://eprint.iacr.org/2022/1593
Having finished the work, which was considerable, I would like to fundraise for retroactive funding given the expenses occurred to me. Not only did I put off my own work for the significant amount of time spent on this, I made the decision to bring j-berman in at a rate we had prior established for their work on my own project.
To explain the work, it's an implementation of a membership proof _compatible with Seraphis_ which is efficient enough to feasibly support up to 777 million outputs. For more than 777 million outputs, proof time would increase ~50%, yet the chain would continue.
While this work isn't complete, it has asserted its existence as a viable path to proceed down.
# What Has Been Done
- An implementation of Bulletproofs+, designed to be clearly understandable and efficient.
A new implementation was written despite Monero already having a deployed implementation. This was due to Monero's implementation only supporting aggregate range proofs and being so tailored for them, it being infeasible to expand to include support for arithmetic circuits (the proof Curve Trees uses).
It is not yet ready for production for a few reasons.
1) It panics on invalid inputs, instead of returning errors.
2) It hasn't been externally reviewed/audited.
3) A design criteria to support curve trees is a vector commitment scheme (VCS). Bulletproofs+ does not support vector commitments, and I had to shim in my own scheme to compensate which is not viable for production.
This will be discussed below.
- An implementation of Curve Trees, or at least, the idea of Curve Trees.
Curve Trees describes a n-ary Merkle Tree where the hash function is a Pedersen hash. Since a Pedersen hash hashes from scalars to a group element, and the variables in an arithmetic circuit are scalars, Curve Trees uses a pair of Bulletproofs over a curve cycle, each layer of the tree represented by the complimentary proof. This ensures the output of the hash is always a native variable. My implementation is similar, yet instead of using the scalar multiplication algorithm provided in its paper, Eagen's application of Elliptic Curve divisors is used. This is multiple times more performant.
Additionally, my work was done over Bulletproofs+, not Bulletproofs, for minor efficiency gains. Post-deciding which arithmetic circuit proof to use, it was learned Curve Trees requires a VCS. Bulletproofs+ does not have a VCS posited, while Bulletproofs has one posited yet not proven. While work could be done to prove the VCS posited for BPs instead of developing a new scheme for BPs+, this would be detrimental in the long term.
To explain why, BPs defines a "inner-product" argument. BPs+, "weighted inner-product". BPs++, "norm". BPs++ argues its "norm" argument can be equivalent to BPs+'s "weighted inner-product", implying future development of a VCS around BPs++ would be best done from a VCS around BPs+. Since it is a goal to move to BPs++ for efficiency, not just for arithmetic circuits (this work) yet also Monero's range proofs (which BPs++ already has funding to be reviewed for), this was kept in mind.
As part of my work, I reached out to Firo, with researcher Aram Jivanyan and contracting researcher Aaron Feickert (sarangnoether) from Cypher Stack. I requested their collaboration in this effort, with current discussions being around them working on developing and proving a VCS. While no guarantees have been made, the answer to if a scheme for BPs+'s WIP argument is possible was estimated to be on the scale of weeks, not months. Accordingly, I'd personally evaluate it within timelines _and long-term fruitful_ to continue with BPs+ and not revert to BPs. If a BPs+ VCS is infeasible, then the work falls back to proving the VCS posited for BPs, which has passed first glances.
- An implementation of Elliptic Curve divisor calculation and checks
Elliptic curve divisors can be used to offer proof-of-knowledge of discrete logarithms which are several times more efficient than in-circuit elliptic curve additions. I implemented the calculation of divisors, checks for them (in and out of circuit), achieving a roughly 3x reduction in DLog PoK circuit size than the Curve Trees DLog PoK circuit. This circuit is most of the overall circuit, and circuit size does directly relate to proof verification time.
- An implementation of COPZ's discrete logarithm equality proof
Since Curve Trees effectively requires a curve cycle, Monero would have to move to one. This proof lets Monero move to a curve cycle at a marginal cost (a one-time 160-byte proof per-output).
# What's Next
A series of tasks can be defined.
1) Proving and implementing a proper VCS scheme
This is currently in progress, and doesn't actively require the Monero project. In the future, it may require our involvement, and if so, we can discuss it then.
2) Proving/formally verifying Curve Trees
I agree more certainty behind Curve Trees is needed. I do not believe we should halt development efforts until we are fully certain, given the amount of evidence before us and alternative paths ahead of us for any road blocks we may face. Already happening is the development of a VCS scheme, with proofs. Once that happens, letting us formally define our Curve Trees instantiation, we can continue obtaining certainty. All of this can be done in parallel to this work's completion.
3) Polishing the above work
This will be tackled by future CCSs. I am planning one, and j-berman has already submitted a CCS which part of is experimentally integrating Curve Trees into Monero (https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/401). I have also discussed with multiple developers in the ecosystem getting their involvement.
To be perfectly clear, in no uncertain terms, this CCS does not provide funding for nor guarantee any continued development. It is solely a representation of gratitude and acknowledgement for work already performed, and organization provided.
4) Auditing
Auditing can only occur once the academia, and the code, is completed.
5) The Monero project deciding whether or not to move to a curve cycle
I cannot truly comment here as I do not speak for the Monero community.
My personal thoughts on moving to a curve cycle can be found here: https://gist.github.com/kayabaNerve/97441ad851dc6e4d2a0b699f58a004f2
Relevant MRL issues are https://github.com/monero-project/research-lab/issues/100 and https://github.com/monero-project/research-lab/issues/110.
While this isn't the place to decide if a curve cycle is necessary, or if one will be adopted, it is important to note a curve cycle isn't technically required. It's optimal, and somewhat expected, yet we can hash Ed25519 points into a cycle (at additional cost). Accordingly, this work is relevant even if we don't move to a curve cycle.
6) The Monero project deciding whether or not to integrate this work
In order for the community to decide if this work should be integrated, it must be evaluated. Evaluation requires this work being viable for integration, which won't happen until it's complete. For now, I restate
> While this work isn't complete, it has asserted its existence as a viable path to proceed down.
And accordingly justify not only its historical funding, yet future funding.
# Why Historical Funding
The CCS has a distaste for historical/retroactive funding, which I understand. Personally, I do not accept payment for a job until it is done. While the milestone system offers that, I still must promise and obligate myself to doing the work by the fact I created a CCS and succesfully raised funds. I do not appreciate those obligations when I was unsure of my capabilities to produce not just a membership proof, yet a membership proof viable to continue with which was worth fundraising for. Before I wrote an implementation of BPs+, designed a higher-level arithmetic circuit framework, learned enough math to implement Elliptic Curve divisors, engaged with multiple other parties, and implemented Curve Trees, I was unsure this would become meaningful to Monero. It was on a scale I had never worked with before, and far too much work to ever be certain about before it is done and actual metrics can be assigned. Accordingly, I would never have felt comfortable with funding beforehand.
I also wished to avoid debate about the legitimacy of atttempting this work. This work, as currently implemented, with its current performance, commentary, and understandings, establishes itself as viable. Before it existed, it could not establish itself as viable. By waiting, I removed discussions about if it would be viable by now providing a proof it is.
While this work was done with limited visibility, I did contact parties as soon as they became relevant. Prior mentioned was a collaboration with Firo, yet I also reached out to Liam Eagen (author of BPs++ and a proof applying Elliptic Curve divisors), narodnik, and j-berman as beneficial.
# Funds Breakdown
The amount quoted is roughly 50,000 USD. Given the amount of work produced, and time spent, I believe this to be fair.
This is inclusive of my obligation to j-berman ($3,600) who:
- Reduced the multiplications performed, savings tens of percent off verification time
- Investigated a new algorithm for further reducing multiplicatios, which would also be applicable to Monero's current BP+ implementation
And my desire to thank Eagen for their contributions with $5,000. Eagen's application of divisors drastically increased the performance of this work. Also notable is narodnik who provided an initial Python reference for divisor construction and evaluation, yet they have declined to be so thanked.
With all of this in mind, and given the extended hours I generally work, my hourly rate would be roughly 100 USD.
# Resolution
If this proposal is not funded within two months, it will be closed regardless of status. All raised funds will be directed towards the already completed milestones, even if only partially funded. Whatever amount raised will close this CCS, and be considered as complete funding for these milestones.
---
layout: wip
title: Maintaining Flatpak package
author: BigmenPixel
date: March 21, 2023
amount: 10.02
milestones:
- name: manifest to core repo
funds: 3.5
done:
status: unfinished
- name: 3 month maintenance
funds: 1.63
done: 2 April 2024
status: finished
- name: 3 month maintenance
funds: 1.63
done: 2 April 2024
status: finished
- name: 3 month maintenance
funds: 1.63
done: 2 April 2024
status: finished
- name: 3 month maintenance
funds: 1.63
done: 2 April 2024
status: finished
payouts:
- date: 9 April 2024
amount: 6.52
- date:
amount:
- date:
amount:
- date:
amount:
- date:
amount:
---
## **Maintaining flatpak package `org.getmonero.Monero`**
## Summary
I have been maintaining `org.getmonero.Monero` on Flathub since July 2021. Now I want to move its manifest to the [monero-gui](https://github.com/monero-project/monero-gui) repository. The org.getmonero.Monero github repo which is now used to push files to flathub will be discontinued. The files will be built and pushed directly from the monero-gui repository. Users will then be able to compare the hashes of files on their machines to those from the monero-gui workflow run. We can then give Monero-gui flatpak app a "verified" checkmark. This is an optional step for the community to decide at a later date. Flatpak installs will still remain 3rd-party and users are encouraged to confirm hashes, as they are with any other package repository.
Thanks to this, users will be able to trust this flatpak package more.
## Installing and using
The `org.getmonero.Monero` flatpak package is a good replacement for ordinary packages in GNU/Linux distributions, for example it can be used in Whonix to [replace](https://forums.whonix.org/t/how-to-verify-the-monero-binaries-that-are-shipped-with-whonix/16439/10) the Debian package.
At first you have to [setup flatpak](https://flatpak.org/setup) with Flathub repository on your GNU/Linux distribution. After that, run this command:
```
$ flatpak install flathub org.getmonero.Monero
```
By default, `org.getmonero.Monero` has access only to the `~/Monero` directory, if you need more, do it:
```
$ flatpak --user override --filesystem=/path_to_your_directory org.getmonero.Monero
```
Some people need access to the `monerod` command:
```
$ flatpak run --command=monerod org.getmonero.Monero [options|settings] [daemon_command...]
```
## About me
I am [BigmenPixel](https://github.com/BigmenPixel0), who maintains Monero GUI on Flathub and some packages in the [AUR](https://aur.archlinux.org/account/BigmenPixel).
### Milestone 1 (3.5XMR)
Move the manifest to the [monero-gui](https://github.com/monero-project/monero-gui) repository.
### Milestone 2 (6.5XMR)
1 year of maintenance to be paid quarterly @1.63XMR after performance review (updates are ready in a timely manner / critical issues solved).
These rates are based off of the previous [debian package maintenance](https://ccs.getmonero.org/proposals/adrelanos-debian-package.html) proposal.
---
layout: wip
title: "From Prototype to Marketplace: Maturing the XMR-BTC Atomic Swaps Ecosystem"
author: "binarybaron and einliterflasche"
date: July 9, 2024
amount: 729
milestones:
- name: 1st month
funds: 121.5
status: finished
done: 15 October 2024
- name: 2nd month
funds: 121.5
status: finished
done: 26 November 2024
- name: 3rd month
funds: 121.5
status: finished
done: 21 January 2025
- name: 4th month
funds: 121.5
status: unfinished
done:
- name: 5th month
funds: 121.5
status: unfinished
done:
- name: 6th month
funds: 121.5
status: unfinished
done:
payouts:
- date: 19 October 2024
amount: 121.5
- date: 6 December 2024
amount: 121.5
- date: 3 February 2025
amount: 121.5
- date:
amount:
- date:
amount:
- date:
amount:
---
![https://i.ibb.co/3NvpYp2/upload-398781d371d354427bb455356731258c.png](https://i.ibb.co/3NvpYp2/upload-398781d371d354427bb455356731258c.png)
![https://i.ibb.co/wgYK9FF/generated-gif-2.gif](https://i.ibb.co/wgYK9FF/generated-gif-2.gif)
### Who
We (binarybaron and einliterflasche) are two Monero enthusiasts from Berlin and both computer science students. We have been excited about XMR<>BTC atomic swaps since the COMIT team started development of their prototype. binarybaron has contributed to the project since its early stages while einliterflasche joined later on.
### What is this project anyway?
The project mostly consists of four parts:
1. A command-line utility ([ASB](https://github.com/comit-network/xmr-btc-swap/blob/master/docs/asb/README.md)) that enables individuals to operate a 'swap provider' service. These swap providers offer to sell Monero in exchange for Bitcoin.
2. A command-line interface ([CLI](https://github.com/comit-network/xmr-btc-swap/blob/master/docs/cli/README.md)) that allows users to connect with swap providers and exchange their Bitcoin for Monero.
3. A graphical user interface ([GUI](https://github.com/UnstoppableSwap/unstoppableswap-gui/)) that utilizes the CLI behind the scenes, making the swap process way more user-friendly.
4. A command-line utility for hosting a [rendezvous point](https://github.com/comit-network/rendezvous-server) in the decentralized discovery network. Swap providers can register at these nodes to make themselves known to the network. CLI users can retrieve a list of swap providers.
### What we have been working on over the last 2 years:
- Developed an early web interface to simplify XMR<>BTC swaps. This project has since been deprecated and replaced with a desktop GUI.
- Stepped in as maintainers for the [xmr-btc-swap](https://github.com/comit-network/xmr-btc-swap) project which includes the ASB and CLI applications. We have become the main developers fixing issues, implementing new features and pushing out releases.
- Developed the [GUI](https://github.com/UnstoppableSwap/unstoppableswap-gui/). Last year alone, more than 3,000 swaps were completed using our GUI. Since we completed our second CCS from May 2022, we worked on the project during our free time. This is also the reason we weren't able to dedicate as much time to the project as we'd like to and, frankly, as it deserves.
- Running a mainnet swap provider to kickstart adoption that has performed over a thousand swaps with users. This has been put on pause for now as more swap providers have emerged.
- We have also been hosting, and developing publicely accessible infrastructure
- An API service that gathers a list of all known swap providers. This can be used in the GUI and also by others in the community (e.g [OrangeFren](https://orangefren.com/)) in addition to rendezvous points.
- A reliable rendezvous point
- As part of our efforts to make atomic swaps accessible to the general public we have have been writing [documentation](https://docs.unstoppableswap.net/) for atomic swaps in general as well for the GUI and CLI applications.
### Proposal:
We're excited to keep working on atomic swaps. While swaps work realiably under optimal conditions, there are still many imperfections. We are confident that given a few months time to fully dedicate to the project, we can transform the ecosystem from more of a proof of concept into a mature marketplace.
We are asking the community for funding in order to be able to focus our efforts on improving the atomic swaps ecosystem.
We request 729 XMR for continued development for 6 months. At the end of each month 121.5 XMR will be paid out. We will dedicate 35 hours of focused work per week per person. Our hourly rate is 60 EUR. We're calcuating these amounts at a current average price of 138 EUR/XMR.
We will be providing monthly detailed updates in the comment section.
### What we will be working on
We will continue to maintain both the GUI and the underlying CLI/ASB by:
- Planning, coordinating and implementing new features and bug fixes,
- Coordinating releases,
- Keeping in touch with users and the community as a whole as well as offering a built-in feedback system in the GUI.
Furthermore, we will continue to manage some community infrastructure:
- We host a [webpage](https://unstoppableswap.net/) for the GUI as well as [documentation](https://docs.unstoppableswap.net/).
- We maintain both a public registry of swap providers as well as a reliable node in the decentralized discovery network.
For the CLI and ASB, which form the backbone of the GUI and swap provider infrastructure respectively, our focus will be to improve overall reliability. While swaps work consistently under optimal conditions, there are many moving parts, leading to various challenges in practice. These challenges include:
- Reliably staying in sync with both the Bitcoin and Monero blockchains,
- Completing swaps amid connectivity issues,
- Discovering peers in the network,
- Maintaining backwards compatability between peers (network protocols),
- Handling concurrent swaps,
- Accounting for blockchain congestion,
- Stringently enforcing protocol compliance,
- Ensure fail safety when swaps can't be completed,
- Minimizing the manual intervention required (e.g having to manually refund in some edge cases),
- ...
For the ASB daemon specifically, our focus will be on enhancing its ability to handle large amounts of liquidity reliably. We will also make it easier for a wider range of individuals to become a swap provider and sell their Bitcoin for Monero. This will improve competition and in turn lead to lower markup rates. Our work will include:
- Developing user-friendly tooling to simplify the setup and operation of the ASB and its accompanying services.
- Improving ASB extensibility and automatability by implementing an JSON-RPC server:
- Swap providers can connect to their ASB using a standardized OpenRPC protocol
- This will enable providers to:
- Dynamically adjust their exchange rate based on current conditions and market assessment
- Flexibly set maximum and minimum swap amounts according to their risk tolerance
- Automate access to internal Bitcoin and Monero wallets for fund management
- Listen for all kinds of events
- Enabling anyone to automate their ASB service to their liking by developing easy-to-use connector libraries for popular programming languages (e.g. Python, TypeScript, Rust, Java).
Integrating the RPC server and developing client libraries will take a lot of work and large refactors, but it will be worth the effort. It will enable the creation of custom applications and scripts built on top of the ASB. This will open basically unlimited possibilities but the most obvious use cases include:
- Complete access to statistics and internal data and logging
- Adjust exchange rate and minimum swap amount based on current Bitcoin transaction fees
- Listening for specific events and executing custom actions e.g. sending notifications or replenishing funds by executing trades on other platforms
- Integration of Bitcoin privacy protocols (e.g., CoinJoin, Whirlpool) for received funds
For the GUI itself our focus will be to:
- Make the GUI more accessible to non technical users (e.g. tooltips, explanations, ...),
- Provide documentation for end users as well as technical documentation to improve transparency and attract new developers,
- Work on migrating the GUI framework (from Electron to Tauri) to simplify the architechture,
- Release an Android (and possibly iOS) version of the GUI.
- _(We are also looking into a web version, powered by WebAssembly, which can run in browsers. This may not be possible and will require extensive refactors in the code base.)_
- Build a new UI for hosting and managing the ASB from inside the GUI. Thereby enabling selling Monero for Bitcoin.
### Why
We want to enable anyone to reliably acquire Monero by building an anonymized, decentralized and trustless market that is resiliant to censorship. We believe that by realizing the potential of this project we can bring this to reality.
A mature ecosystem will attract more users and swap providers. This will lead to increased liquidity and competition and thus make atomic swaps a viable alternative to centralized exchanges.
---
layout: wip
layout: cp
title: "Spanish translation and proofreading of the monero site, GUI/CLI wallets and User Guides"
author: michaelizer
date: May 28, 2021
......@@ -7,23 +7,19 @@ amount: 12
milestones:
- name: Milestone 1 - Translation and proofreading of the Monero site
funds: 33.33% (4 XMR)
done:
status: unfinished
done: 15 July 2022
status: finished
- name: Milestone 2 - Translation and proofreading of the GUI and CLI wallets
funds: 41.67% (5 XMR)
done:
status: unfinished
done: 15 July 2022
status: finished
- name: Milestone 3 - Translation and proofreading of the user guides
funds: 25% (3 XMR)
done:
status: unfinished
done: 15 July 2022
status: finished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
- date: 23 July 2022
amount: 12
---
## What the proposal is about?
......
---
layout: wip
layout: cp
title: midipoet-Oslo_Freedom_Forum_CCS_proposal.md
author: midipoet
date: April 6, 2022
......@@ -10,14 +10,16 @@ milestones:
done: 25 April 2022
status: finished
- name: Report submitted
funds: 4.25 XMR
done:
status: unfinished
funds: 4.25 XMR (2.25 to midipoet, 2 to GF)
done: 24 September 2022
status: finished
payouts:
- date: 25 April 2022
amount: 4.25
- date:
amount:
- date: 28 September 2022
amount: 2.25
- date: 20 September 2022
amount: 2
---
......
---
layout: wip
layout: cp
title: mj part time coding Q2 2022
author: mj
date: Mar 01, 2022
......@@ -15,15 +15,15 @@ milestones:
status: finished
- name: Month 3
funds: 34.0 XMR
done:
status: unfinished
done: 18 June 2022
status: finished
payouts:
- date: 2 April 2022
amount: 34
- date: 18 May 2022
amount: 34
- date:
amount:
- date: 4 July 2022
amount: 34
---
......
---
layout: wip
layout: cp
title: Creation of Python tools and educational material for checking and explaining the absence of money leakage (a.k.a. inflation) in Monero.
author: DangerousFreedom
date: March 25, 2022
......@@ -7,23 +7,23 @@ amount: 43.2
milestones:
- name: MLSAG
funds: 14.4
done:
status: unfinished
done: 31 May 2022
status: finished
- name: CLSAG
funds: 14.4
done:
status: unfinished
done: 3 July 2022
status: finished
- name: Seraphis / Optimizations / Functional website delivery
funds: 14.4
done:
status: unfinished
done: 4 September 2022
status: finished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
- date: 2 June 2022
amount: 14.4
- date: 6 July 2022
amount: 14.4
- date: 7 September 2022
amount: 14.4
---
## TLDR
Minimal Python tools and educational material for checking inflation in Monero.
......
---
layout: wip
title: Audit monero-serai and monero-wallet
author: kayabaNerve
date: October 11, 2024
amount: 1050 XMR
milestones:
- name: Audit of monero-[serai, wallet], including the FROST-inspired multisig protocol
funds: 1050 XMR
done:
status: unfinished
payouts:
- date: 3 December 2024
amount: 1050
---
monero-serai and monero-wallet are public-good libraries built by myself as part of my work on Serai DEX. Despite the "-serai" name, both libraries have always been intended to be usable and actually used by the Monero community as a whole. Development has been ongoing for over two years. During that time, I have hired developers to work on and review it (including j-berman who truly needs credit and acknowledgement for their contributions), yet have never seeked community funding for my work. Now that monero-serai and monero-wallet are ready for their 1.0 release, meaning they have reached the necessary milestone to be considered sufficiently developed and meaningful, I have decided to request the community's support for their audits.
monero-serai is a from-scratch reimplementation of the Monero transaction protocol in Rust. It originally also
included wallet functionality yet that was split out into the monero-wallet library to offer greater
flexibility to consumers.
monero-serai is used by Cuprate[[1]](
https://github.com/Cuprate/cuprate
)[[2]](
https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/405
)[[3]](
https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/422
)[[4]](
https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/431
)[[5]](
https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/456
)[[6]](
https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/469
)[[7]](
https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/484
) for its parsing/handling/stateless verification of Monero transactions. Specifically, included is:
- An implementation of v1 and v2 transactions
- Cryptonote ring signature, MLSAG, and CLSAG verification
- Borromean, Bulletproofs, and Bulletproofs(+) verification
monero-serai also underpins monero-wallet, a Rust library for sending and receiving Monero. It's intended to have a clean, high-level API, be usable in a variety of contexts (from desktops to embedded devices to web browsers), and support everything from traditional wallets to more novel use cases (such as atomic swaps). As part of this, it offers:
- Proving CLSAG, Bulletproofs, and Bulletproofs(+)
- Honest-sender outgoing view keys (deterministically derived transaction keys to simplify payment proofs and allow verifying transactions match an intent)
- A FROST-inspired multisig which has O(1) per-signer upload complexity and O(n) computational complexity, compared to Monero's multisig which has O(n!) complexity (where n is the amount of signers)
Potentially of most note is the work on multisig. FROST is a widely regarded, [IRTF standardized](https://datatracker.ietf.org/doc/rfc9591/) multisignature protocol for Schnorr signatures which I've applied to Monero's CLSAG (caveats apply). The application to CLSAG is built upon [modular-frost](https://github.com/serai-dex/serai/tree/develop/crypto/frost), a FROST implementation I wrote for Serai and have already [prior audited](https://github.com/serai-dex/serai/tree/develop/audits/Cypher%20Stack%20crypto%20March%202023).
Monero has historically had issues with its multisig which has a novel high-complexity DKG and a signing protocol which isn't formalized (though is currently Musig2-inspired). monero-wallet represents an opportunity to step forth with a formalized, proven, and audited multisignature implementation. One idea occassionally brought up has been to remove multisig from Monero proper, placing it in its own distinct repository, in order to not have multisig burden Monero. With the work done on monero-wallet, and the audit being funded here, completely deferring multisig to it would become a viable option.
monero-wallet has also been checked to have a matching decoy selection algorithm (specifically, a matching distribution of selected decoys), fee algorithm, and various other properties (such as TX extra) to ensure its transactions won't be fingerprintable.
There is interest by multiple wallets to use monero-wallet, and it's already being developed on top of by Serai, a user-facing multisignature use case, and an application premised on web technology (which compiles monero-wallet to WASM).
This CCS is to fund the formalization of the implemented CLSAG multisig protocol (already outlined), provide the necessary security proofs (derived from FROST), and audit monero-[serai, wallet]. The audit will be done by Cypher Stack (their quoted amount being the amount requested). The one milestone is to be paid directly, immediately, and in full, to Cypher Stack for their work.
After the audit, the plan is to transfer monero-serai into the newly created [monero-oxide](https://github.com/monero-oxide/monero-oxide) organization (head by myself and boog900 from Cuprate). This is to help ensure it stands as a public good and doesn't solely service a single project's needs. Additional discussions are ongoing regarding the future governance of monero-wallet.
---
layout: cp
title: Help an independent film featuring Monero get to the Oscars™!
author: markofdistinction_
date: January 20, 2023
amount: 154
milestones:
- name: upon approval
funds: 77
done: 25 September 2023
status: finished
- name: upon qualifying for Academy Award
funds: 77
done: 25 September 2023
status: finished
payouts:
- date: 5 November 2023
amount: 154
---
### Note: This proposal generated significant and thoughtful discussion; potential donors are invited to read it [here](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/371).
![HorizontalPoster](https://raw.githubusercontent.com/markofdistinction/ccs/main/MarkOfDistinction_16x9_1280x720.jpg)
# Help an independent film featuring Monero get to the Oscars™!
### Who are you?
Hey all, my name is George Nicholas, an “award-winning” filmmaker and Monero enthusiast. You can see my IMDb profile here: https://www.imdb.com/name/nm11077440/
I was involved with making "Monero Means Money".
### What’s up?
I’ve written and directed an independent, 38-minute live-action film titled MARK OF DISTINCTION. The film is in Spanish and English and was shot in Tijuana, Mexico in July of ‘22 on 16mm Kodak film. It features Monero, but is not focused on it -- it is inspired by real events and tells the story of a 16-year-old boy who gets recruited by the Mexican cartel to smuggle liquid meth across the border. The boy dies tragically at the hands of U.S. Customs and Border Protection, who ask him to drink the liquid to prove that it’s not drugs.
You can see a report and footage of the incident here:
https://www.youtube.com/watch?v=7KsKtVnrRaM
And some behind-the-scenes photos from our shoot [here](https://twitter.com/markofdistinctn/status/1554237266460954625?s=20) and [here](https://twitter.com/markofdistinctn/status/1554237518098313217?s=20).
Government coercion over the individual is the reason I came to Monero and it is the reason I was driven to tell this story.
### How is this related to Monero?
Monero is featured in 3 scenes. As background, the protagonist, MANUEL, has found a physical Monero coin that his father had stashed away for him before his disappearance--
### Did you just say a physical Monero coin? gtfo
Yeah, a physical Monero coin, like this one: https://bitcointalk.org/index.php?topic=1502918.0
### OK, so what happens next?
So, Manuel is carrying the coin around in his pocket like an idiot, not realizing what he has. His friend, RODOLFO, sees him trying to shove it down a slot machine, but thankfully the coin is too big to fit. Rodolfo explains to him what he has and Manuel’s eyes light up. Outside the bar, the two get beat up because of an earlier incident and the hooligans make off with Manuel’s scooter and his coin. Manuel gets his revenge and recovers the scooter, but not the coin. Rodolfo later finds the coin and tries to give it back to Manuel, but it is too late…
Monero represents the boy’s potential – the unrealized wealth that every individual carries within, although not everyone finds the key to unlock it. The coin ends up with the person who understands its value, as often happens in real life.
### How can we help?
I self-funded the shoot and post-production (the budget was in the low six figures), which exhausted my personal savings. We need funds for the most crucial phase – the release of the film. This includes getting it in front of festivals and promoting it there, hiring a publicist, running an awards campaign. All this costs money and I am coming to the Monero community for help.
### What do we get in return?
##### 1. Exposure (the good kind)
The film has the chance of reaching hundreds of thousands and even millions of people. Not every viewer will become a Monero user, but they will all be exposed to Monero in a positive way. The community will also receive an acknowledgement in the credits, to the effect of "this movie was kindly supported by the Monero community" with the Monero logo and getmonero.org underneath.
Monero already gets exposure in the media and [even some TV shows](https://twitter.com/vikrantnyc/status/1616152774856540166?s=20), but almost always as a Ransomcoin. This is a story that shows Monero being used in the way most of us use it -- as a savings vehicle that we can spend or pass down to our loved ones outside of anyone else's control. Monero means money, but it also represents so much more -- a path towards personal freedom, away from coercion by the state or others. This is what the film tries to get across and hopefully it succeeds.
##### 2. Physical presence
With the community's help and the right release strategy, the film will play at major festivals across the world. Anytime the film plays, this will be an opportunity for an impromptu Monero meetup. Screenings can be publicized in the community beforehand to attract local Monero fans throughout the world.
##### 3. A cause to rally behind
I know we take the whole magic internet money thing seriously around here, which is why I love Monero. It is the reason no other coin was considered to take its place in the film. And I respect the more conservative view that the CCS should only be used to fund developer work. The number of undelivered, CCS-funded projects is dishearteninig, which is why I held off on asking for help until the film was actually made and ready to go.
Monero has the best p2p cash characteristics of any coin, but we could do a better job of celebrating that. This film will give us an opportunity to rally behind a cause that almost all of us agree with -- the right of the individual to remain free from oppression, especially from governments. We can go to festivals together or follow from home, celebrate the wins and mourn the losses. Consider it an exercise in community-building.
##### 4. Some cool GIFs, of course.
But you'll get them regardless, since the film is already made.
![CoinGIF](https://raw.githubusercontent.com/markofdistinction/ccs/main/coin_squeeze.gif)
Also, the idea to have a private screening for the community at MoneroKon was floated, which I'd be open to doing if there is interest.
### Alright, how much do you want? Spit it out.
###### We are looking to raise 154 XMR (the equivalent of $25K at Kraken’s current 20-day EMA)
### What's your Oscars strategy? (i.e. How are you going to spend it?)
Films under 40 minutes are considered live action short films by the Academy of Motion Picture Arts and Sciences. This is the category we're aiming for. There are two ways for a film to qualify:
1. The film must win an award at one of the ~130 Academy Award-qualifying festivals throughout the world:
https://www.oscars.org/sites/oscars/files/95aa_anim_short_festivals.pdf
Submission fees to these festivals are generally in the $50-$100 range, so that alone can eat up $10K.
2. The film must be publicly exhibited for paid admission in a movie theater in Los Angeles or New York City for
one week: https://www.oscars.org/sites/oscars/files/93aa_short_films.pdf
This is the cheaper option at about $3K, but films that qualify with a festival win are preferred by Academy voters, so we'll try the festival route first.
Once the film qualifies, the remaining funds will go towards hiring a publicist and running an awards campaign. Jim Dobson at Indie-PR has seen the film and loves it.
He ran the Oscars campaign for AUDIBLE, a short documentary that received a nomination in 2022. https://www.indie-pr.com/about
Another PR firm with extensive experience that has expressed interest is JJPR: http://joshuajasonpr.com/film-campaigns
I make no guarantees that we will win an Oscar or be nominated, but every industry professional who has seen the film thinks we have a good chance (and not just the publicists who stand to make money). We are taking this journey and I'd like the community to come along!
### Who else has seen the film?
I've reached out to some people I know in the community, who have kindly taken the time to see it. Here's what they had to say:
##### jberman said:
"This has the feel of something that would win a lot of awards."
"Was the idea of the friend chasing him to give the coin to him basically saying Monero represented an
alternative path to a better life/better system instead of the darker one he chose? That's how I read its place
in the story."
##### midipoet said:
"you don't need me to tell you, but for what it's worth, the production value is extremely high"
"it's pretty much feature length quality, as you were aiming for. what struck me most though was the quality
of the acting."
##### Vik Sharma said:
"Really, really well made."
##### Doug from MoneroTalk said:
"Captivating! Sunita and I loved it."
##### Johnny Mnemonic said:
"Awesome film! The Monero coin inclusion was great…
Touching story… I really feel for the kid at the end because he’s just trying to make things right with his grandfather.
I also liked that you included real footage at the end… really makes you feel how real it is. "
##### dsc said:
"that last scene had me on the edge of my seat!"
### What happens if Monero's price fluctuates in the meantime?
The amount we're raising is denominated in XMR. Any fluctuations in fiat value are at our own risk/benefit.
### When do you expect to be paid?
50% upon approval, 50% upon qualifying for the Academy Awards, as described above.
### Is the film on any social media?
https://twitter.com/markofdistinctn
https://instagram.com/markofdistinctionfilm
https://fb.com/markofdistinctionfilm
### Can I see it before I donate?
Yes, please send 1 piconero (0.000000000001 XMR) to the donation address as a captcha and email markofdistinction@proton.me with the txid and tx key and you'll receive a link back.
### OK, take my money! ;-)
---
layout: cp
title: "monerobull for website workgroup"
author: monerobull
date: 5 July 2024
amount: 30
milestones:
- name: 2 meetings + hours worked
funds: 10 XMR
done: 1 January 2025
status: finished
- name: 2 meetings + hours worked
funds: 10 XMR
done: 1 January 2025
status: finished
- name: 2 meetings + hours worked
funds: 10 XMR
done: 1 January 2025
status: finished
payouts:
- date: 30 January 2025
amount: 30
---
# Who, what, when, where?
Hi, I'm monerobull. I run monero.town & monerosupplies.com. I also never did any paid work for Monero before.
I was recently mentioned in a CCS proposal by geonic, famous Monero movie director. 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 my own CCS proposal rather than through geonics. This moves me from being accountable to nobody, to accountable to the community.
A quick summary of what I'd be working on:
- Setting up / managing a Monero Website Workgroup, keep it up to date (our roadmap still mentions triptych)
- Joining the moderator teams for Matrix and helping along with discord
- Being a supportive figure 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, not IRC, Matrix, Reddit, etc.)
- Aiding and assisting in event work as needed (part of Monerokon team since MK3)
# Why?
There's lots of non-dev stuff to do, and not so many people to do it. I am mostly capable and willing.
# How long? How much?
30 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. Luigi does a lot of work, I'd like to take on some of that.
# COI
I would have never made this proposal without geonics preceding yolo proposal. In the past I've tried to stay away from the CCS due to all the drama surrounding it. This very proposal was born out of CCS drama.
---
layout: cp
title: MoneroKon 2023 CCS-1
author: ajs-xmr
date: December 12, 2022
amount: 553.67
milestones:
- name: Neuchatel
funds: 383.31
done:
status: unfinished
- name: Prague
funds: 170.36
done:
status: unfinished
payouts:
- date: 21 December 2022
amount: 553.67
---
# Table of Contents
- [Who?](#who)
- [What?](#what)
- [Costs](#costs)
- [Bursary](#bursary)
- [Amount](#amount)
- [CCS Disbursement](#ccs-disbursement)
- [CCS-2 Contingency Funding](#ccs-2-contingency-funding)
- [Donor Benefits](#ccs-donor-benefits)
- [Exchange Rate](#exchange-rate)
## Who
I am ajs-xmr, co-author of [the scripts]( https://github.com/monero-ecosystem/promo-video) for the [Monero explainer videos]( https://www.youtube.com/channel/UCnjUpT9gGxyQ_lud7uKoTCg), cam operator and editor of [Monero Means Money: Cryptocurrency 101, Live from Leipzig]( https://www.youtube.com/watch?v=8quGD9W7B2I)[America’s #1 box office hit in April 2020](https://ia902907.us.archive.org/5/items/monero-means-money-press-release_20200421/Monero%20Means%20Money%20Press%20Release.pdf), and was part of the organization team for the [Monero Village at DefCon27](https://www.youtube.com/watch?v=g8PBOVDWO6Y), [CDC/36C3](https://www.youtube.com/playlist?list=PLsSYUeVwrHBn07zTBg7fGHRW5Kn_Z3FJL), and [MoneroKon 2022](https://www.youtube.com/watch?v=r_vH-NyOYAg&list=PLsSYUeVwrHBndRQoQ-vLezzlHPLRDNzaw). I am also the maintainer of [XMRradio.i2p](https://xmr.radio) and have contributed to the [Monero Policy Working Group](https://github.com/monero-policy). I will be the principal showrunner of the event, responsible for pushing things forward.
Digital Renegades ApS (“DR”), a limited liability company we are using to contract with the venue, suppliers, and traditional payment processors. It also provides a part-time executive assistant to help the organization team with administrative tasks. DR does not cost or charge anything, all company contributions and liabilities to support MoneroKon being effectively a donation to the Monero community. It is incorporated in Denmark and a director of which is a member of the Monero core team.
## What
Monero Konferenco (“MoneroKon”) is an annual meeting of privacy advocates, cypherpunks, scientists, and philosophers and is designed to disseminate scientific and technical results in privacy and financial technologies like censorship-resistant digital cash. It was first held in [Denver, Colorado]( https://www.youtube.com/playlist?list=PLsSYUeVwrHBkJHJg_l2uDgbicDJ1PmAVW) in 2019 and after a hiatus due to COVID-19, the event was rebooted in [Lisbon, Portugal]( https://www.youtube.com/playlist?list=PLsSYUeVwrHBndRQoQ-vLezzlHPLRDNzaw) this past summer. The [2019 event had 73 attendees and 27 speakers]( https://github.com/b-g-goodell/mrl-skunkworks-mirror/blob/master/Konferenco/2019/postmorto.md#1-budget-actuals) and in 2022, there were a total of 160 attendees and 40 speakers, having [sold out in less than 6 weeks]( https://nitter.net/MoneroKon/status/1528247373398515712).
In a [MoneroKon 2023 Planning Meeting that was held on November 12th 2022](https://monero.observer/assets/logs/221112-monerokon23.log), meeting participants unanimously agreed to try to hold the event again next summer at [La Fabrika](https://www.lafabrika.cz/en/lafabrika) in Prague, Czech Republic on 23rd-25th June 2023. Photos, and other details about the venue, merch, A/V set up, and preliminary schedule can be found [here](https://github.com/MoneroKon/meta/blob/main/monerokon2023-plan-a.md).
If the target funding goal is not met in 90 days from the date this proposal is merged, we would fall back to holding the event at [University of Neuchâtel](https://www.unine.ch/batiments/home/prestations/location-de-laula-des-jeunes-riv.html) in Switzerland on 30th June - 2nd July 2023. Details for the Neuchâtel option can be found [here](https://github.com/MoneroKon/meta/blob/main/monerokon2023-plan-b.md). However, if the raised funds are not enough to cover the expenses of Neuchâtel, the funds would roll over to the budget of MoneroKon 2024.
The aim is to have at least the same number of participants as in Lisbon (200) with the capability to scale up to 400 attendees, around 30 speakers, and a number of workshops.
**La Fabrika, Studio 1 - Talks (Main Stage)**
![](https://repo.getmonero.org/ajs/meta/-/raw/main/pics/room1-1.jpeg)
**La Fabrika, Studio 2- Workshops/Chill Area/Sponsor Area**
![](https://repo.getmonero.org/ajs/meta/-/raw/main/pics/studio2.jpeg)
## Costs
Please note that this is a **not-for-profit event** and the aim is to keep ticket prices as accessible for the public as financially possible, while keeping production quality high.
The total cost of the event is estimated to be approximately 168,000€. To take into account uncertainties (_e.g._ the number of ticket, merch sales, sponsors, requests for bursaries), the CCS will be divided into 2 parts. In CCS-1, we are be seeking 553.67 XMR, which represents around 34-38% of the cost, assuming we reach the target ticket sales range (200-400) and the number of sponsors (15). We included a 15% contingency fund for emergencies or unexpected expenses. The budget for Prague can be found [here](https://cryptpad.disroot.org/sheet/#/2/sheet/view/DWRJjhmFhIZSJddgkRDgbEi6gnMMnBFDjxpUPIiOA6Q/embed/) (**please note, that the budget is only a rough estimate and is subject to be updated**).
**Sponsorship Target**
- Supporter (no table, logo only) (5) - 1,500€
- Contributor (7) - 4,500€
- Cypherpunk Hero (3) - 9,000€
Total: 15
Sponsor benefits are TBD, but generally, may include company logo placement on MoneroKon’s website and printed banners, free tickets, and a table at the event for Contributor and Cypherpunk Hero levels.
#### Tickets
The ticket types and supply are as follows:
**Prague 2023**
- GA (315) - 120€
- VIP (60) - 240€
- SP (25) - 60€
The benefits for the VIP tickets are TBD, but will include a free merch pack.
For comparison, the past ticket sales and CCS funding were as follows:
**Lisbon 2022**
**Ticket Sales**
- GA (133) - 50€
- VIP (24) - 150€
- SP (3) - 30€
**CCS**
- Amount Raised - 55,650€
- PR Merged - 7 December 2021
- Fully Funded - 15 February 2022 (70 days)
For 2022, the [total cost was 65,410.37€ and had a surplus of 7,577.16€](https://docs.google.com/spreadsheets/d/1KwKrJ-YX4ByI2fKxpILukIb4jLog7JD8TZLWUelGY7M/edit#gid=0).
**Denver 2019**
**Ticket Sales**
- GA (60) - $128
- VIP (9) - $287
- SP (4) - $54
**CCS**
- Amount Raised - $60,100
- PR Merged - 10 October 2018
- Fully Funded - 30 January 2019 (112 days)
For 2019, the total cost was [$100,210.22 and had a deficit of $-32,815.31](https://github.com/b-g-goodell/mrl-skunkworks-mirror/blob/master/Konferenco/2019/postmorto.md#1-budget-actuals)
Any surplus income or over-funding from this CCS will be rolled over for MoneroKon 2024's budget. However, if there is a deficit, we would need to propose a second CCS to cover the difference.
## Bursary
All speakers and organizers as well as volunteers who have logged at least 15 volunteer hours may request a bursary up to a maximum of 2,000€ to help cover international/local travel, taxies, carshare, accommodation, meals, and any other incidental travel expenses. Expenses must be ordinary, necessary, and reasonable.
The applicant would need to submit a single PDF with scanned copies of ticket stubs and/or receipts (with any personal information redacted) and an invoice with the total amount requested to the Monero Community ("Community") for approval according to the [Invoice Payment Protocol](https://github.com/MoneroKon/meta/blob/main/monerokon2023-plan-a.md#invoice-payment-protocol). Under extenuating circumstances, the Community may vote to cover expenses above the bursary maximum.
To help simplify the process for speakers, the Personal Assistant of DR may batch multiple bursary requests into one invoice and directly seek approval from the Community on their behalf.
The deadline to submit bursary requests is August 1st, 2023.
Payments will be made via Single Euro Payments Area (SEPA) bank transfer or in XMR @ [EMA10 Euro weekly rate](https://www.investing.com/crypto/monero/xmr-eur-technical) from the date the invoice is approved.
The budget for both Prague and Neuchâtel assumes 15 bursary recipients (30,000€). If there is more demand for bursaries, we would need to seek additional funding in CCS-2.
## Amount:
383.31 XMR (Neuchâtel) or 553.67 XMR (Prague)
## CCS Disbursement
**Milestone 1**
- When at least 383.31 XMR has been met, 68 XMR should be set aside as a reserve for bursary payment requests in XMR and the remaining balance will be transferred to DR.
- DR will immediately convert the XMR to Euro @ spot market rate in order to minimize currency volatility.
**Milestone 2**
- When 553.67 XMR funding goal is reached, the remaining XMR (minus the bursary reserve) should be transferred to DR
- DR will immediately convert the XMR to Euro @ spot market rate
If milestones 1 or 2 is not met within 90 days after this CCS is merged, all funds are rolled over to the CCS for MoneroKon 2024.
## CCS-2 Contingency Funding
It is hard to predict the number of sponsors and tickets that will be sold, and total bursary needed to cover speaker, organizer, and volunteer expenses, especially in these turbulent times. If we are unable to garner enough sponsors or there is more demand for bursaries than expected, a second CCS may be required to pay for any funding shortfall. We should have a better idea if a CCS-2 proposal is needed in early May 2023.
## CCS Donor Benefits
As a sign of appreciation for your kind support, backers of this CCS will be able to claim rewards based on the level of contribution.
**0.85 XMR**
- Name/nick in end-credits of uploaded videos
- Free MoneroKon T-shirt promo code
**4.26 XMR**
- Name/nick in end-credits of uploaded videos
- Free MoneroKon T-shirt promo code
- IVPN $100 credit promo code*
- Early access 4k video uploads
**8.52 XMR**
- Name/nick in end-credits of uploaded videos
- Free MoneroKon T-shirt promo code
- IVPN $200 credit promo code*
- Early access 4k video uploads
- Exclusive invite to Speaker’s dinner
After donating, send an email to `ajs@monerokon.com` [key ID: [0xA21EDAB6](https://openpgpkey.monerokon.com/ajs.asc)] with your [proof of payment](https://www.getmonero.org/resources/user-guides/prove-payment.html) (for unofficial wallets, consult the developer's documentation) and the name/nick you would like to appear in the end credits. You could also contact me directly at:
- Libera.Chat IRC: `#monero-events` / `ajs_` / OTR: `2CBD2781 14ADCC59 80216845 7F3405F7 8AE807FA`
- Element/Matrix: `#monero-events` / `@ajs_:matrix.org`
- XMPP: `ajs@xmpp.is` / OMEMO: `2939fc3c 7c8374c1 b31fc816 d4a13ff0 522ec7c3 c2887dd1 f73187b4 95a0492b`/ OTR: `37B44AC3 0F41798E B7CA5F18 D8D2B37B BF469E22` / `monerokon@muc.xmpp.is`
- Threema ID: `AUTS66FZ`
- Mastodon: `@xmrradio@mas.to`
You'll receive promo codes, which can be used on [shop.monerokon.com](https://shop.monerokon.com) when it goes live sometime in March 2023. If CCS is not fully funded for 2023, the discount codes would be valid for 2024.
Pick up your order at MoneroKon's merch table. Be sure to bring a copy of your receipt.
*Can be used on one, or multiple accounts.
## Exchange Rate
65,000€ / 140.877 XMR ([EMA50 Euro monthly rate](https://www.investing.com/crypto/monero/xmr-eur-technical)) + 20% volatility buffer = 553.67 XMR
45,000€ / 140.877 XMR ([EMA50 Euro monthly rate](https://www.investing.com/crypto/monero/xmr-eur-technical)) + 20% volatility buffer = 383.31 XMR
---
layout: wip
title: Monerotopia 2024 Marketing and Publicity
author: geonic
date: November 6, 2024
amount: 36.68
milestones:
- name: Payment to Estrategia Blue PR
funds: 36.68
status: unfinished
done:
payouts:
- date:
amount: 36.68
---
# Monerotopia 2024 Marketing & Publicity
Hi! As discussed in the [previous community meeting](https://libera.monerologs.net/monero-community/20241026#c451916), I am proposing that we [spend the unused funds](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/70#note_26878) from the last Monero Outreach CCS on marketing & publicity for Monerotopia 2024, which starts next Thursday. I would be the key point of contact for the PR firm and will provide a final report on what's been achieved.
Our events are the perfect opportunity to publicize/advertise Monero and so far we haven't done a good job at that. This proposal is a first step in changing that.
**Estrategia Blue PR**, a leading publicity firm in Mexico, has made a [proposal](https://github.com/geonic1/geonic/blob/master/Monerotopia%20Proposal.pdf) and they are ready to start today. We need to engage them ASAP. Vik Sharma has agreed to handle the payment and receive the XMR at no surcharge. The proposed budget (~$5500) is within the remaining amount (36.68 XMR or ~$6000), which we intend to spend in full with more (or less) media buys, depending on the actual amount received by the firm.
As the only remaining, active member of Monero Outreach, I believe this is a good use of the funds and in the spirit of what the donors wished to support.
Cheers!
geonic
---
layout: wip
layout: cp
title: "moneromooo: three months from December 2020"
author: moneromooo
date: 05 December 2020
......@@ -15,11 +15,13 @@ milestones:
status: finished
- name: third month
funds: 33.34% (75 XMR)
done:
status: unfinished
done: 17 May 2023
status: finished
payouts:
- date: 17 June 2021
amount: 150
- date: 17 August 2023
amount: 75
---
Hi,
......
---
layout: wip
title: xmruw - development of cross platform wallet
author: mrcyjanek
date: February 29, 2024
amount: 76.68
milestones:
- name: Month 1
funds: 25.56
done: 8 July 2024
status: finished
- name: Month 2
funds: 25.56
done: 31 August 2024
status: finished
- name: Month 3
funds: 25.56
done:
status: unfinished
payouts:
- date: 17 July 2024
amount: 25.56
- date: 4 September 2024
amount: 25.56
- date:
amount:
---
Hello! I'm mrcyjanek and I'm currently working on the Unnamed Monero Wallet (short: xmruw) that aims to be as portable as possible and as close to `wallet2_api.h` as it is reasonably possible.
However, this project got much bigger than I initially expected and resulted in a project that is huge in size, but also has really large portability capabilities, after fighting for a couple days with Wayland implementation on SailfishOS I (with the help from Mister_Magister and NotKit) managed to run the first cryptocurrency wallet natively on SFOS ([that is available on the app store of that os](https://openrepos.net/content/mrcyjanek/unnamed-monero-wallet-xmruw)). More details and the origin story can be found in a [blog post announcing the wallet](https://www.mrcyjanek.net/p/xmruw-monero-wallet/).
I'm developing `xmruw` with a few critical points in mind:
- There should be no database responsible for any of the monero-releated functions - so I won't accidentally do something that shouldn't be done.
- The app should be as close to `wallet2_api.h` as possible to eliminate things like overly complex state management as something that causes issues.
- Privacy should be prioritized - no external services are contacted in the app, and if there ever happens to be some external feature it will be opt-in in settings with an option to route entire traffic through Tor.
- Security is also prioritized - not only by minimizing the attack surface but also by providing features such as stealth mode (inspired by Samourai wallet)
- UX is the most critical of them all in my opinion - without the right UX, not many users are going to use a wallet, so it is my responsibility as a developer to make the wallet available on all platforms and to be appealing to users.
- As a mobile Linux enthusiast I'll also do my best to offer secure monero wallet solutions for owners of non-Android and non-iOS mobile devices
# About
I've decided to take the simplest path from `wallet2_api.h` to the actual wallet UI, so instead of forking m2049r/cake implementation I've decided to use `dart:ffi` to call the native functions - this made a lot of code unnecessary, and the part that was still required was mostly generated - so I call that a huge win. But not without it's own cost - I had to write a wrapper for `wallet2_api.h` that would provide C headers instead of C++ - which meant [writing a bunch of boilerplate code](https://git.mrcyjanek.net/mrcyjanek/monero_c/src/commit/abaa3a2d165577a79ce0c3fe5382b68fa260ecc1/libbridge/src/main/cpp/wallet2_api_c.cpp#L1549) and implementing a couple of dart/flutter libraries, that gave birth to the foundation of the wallet
## Unnamed Monero Wallet (xmruw)
[Website](https://xmruw.net), [Gitea](https://git.mrcyjanek.net/mrcyjanek/unnamed_monero_wallet), [GitHub](https://github.com/mrcyjanek/unnamed_monero_wallet), [Downloads](https://download.xmruw.net/)
Features of the wallet include:
- Sending/Receiving monero
- Online/Offline wallet modes
- With URQR and file exports for Android/iOS
- With clipboard-based exports for QubesOS
- Embedded Tor support
- (soon) Embedded i2p support [^1]
- Stealth mode (fake calculator app that opens wallet if the correct pin is provided)
- Multiple account support
- Coin control
- Signing / Verifying of messages
- Custom themes
- Advanced settings
- Performance analysis tool for the `wallet2_api.h` functions called
- Debug information that makes development easier
- Configuration options to opt-in to experimental features (such as [background sync](https://github.com/monero-project/monero/pull/8619))
- OpenAlias resolving
- Backup/Restore
- Historically accurate currency conversion done fully offline
- And all of the "obvious" features such as transaction list, subaddress list, wallet locking, QR code scanning, etc.
## Scope of work
While working on Unamed Monero Wallet, here is a non-comprehensive list of the things I want to accomplish in no particular order, as it doesn't make sense to separate some things.
- Expanding compatibility of `monero_c` to all platforms that I have access to (Linux (glibc+musl), FreeBSD, iOS, MacOS, Windows) in an easily-reproducible way (single script and a docker environment)
- Making `xmruw` available for all platforms (and I do mean all platforms) and in app stores (including play store, self-hosted f-droid repository, apple app store, .deb, and .rpm repository).
- Implementing features desired by users, currently this includes
- periodic sync (via [background-sync](https://github.com/monero-project/monero/pull/8617)) to provide seamless experience, no matter how frequently the app is actually opened
- merchant mode
- many UI/UX improvements/changes (some of more important ones: make seed offset and its role more obvious, better backup mechanism, time-lock warn, automatic node selection)
- Work on documentation (this will be a significant task on its own, but the goal is to allow anybody to integrate monero no matter what language/framework they are using by using monero_c/monero.dart).
- Fix issues that were made along the way
- Bytewords entering an infinite loop when incorrect text is passed in
- No compatibility with Feather / ANONERO in offline mode due to lack of CBOR encoding
- Not cross-platform QR scanner [^2]
- Bad UI on desktop (not that it's bad, it is just mobile-first)
- and more, if found when developing
- sending fixes to relevant peers and upstream
## Milestones
Given the nebulous nature of development, I would prefer my milestones to be time-based. I prpose a milestone completion and subsequent payout once every month (after services rendered).
In addition to the above features mentioned in the scope of work, I propose an additional deliverable of a weekly report so my progress can be verified.
# Payment
I'm proposing to work for 20 hours/week for `40$/hour` at a rate of `~125,14$/XMR` (according to open prices between 2024-02-17 and 2024-03-01 (date of writing) via [CoinGecko](https://www.coingecko.com/en/coins/monero/historical_data)) for 12 weeks, summing up to a total of `~76,68` XMR split into 3 payments of `25,56` XMR every 4 weeks.
At the end of each week, I'll comment a summary of what happened along the way and what tasks were done.
[^1]: The library is there, it needs some love to be usable, cross platform and built in a reproducible fashion.
[^2]: Camera isn't fun, especially when being cross-platform is a goal, but supporting it is critical for URQRs. This isn't a milestone on it's own, but a topic that I'll research, do some PoC and come up with a solution, especially because getting camera to work is one task, then we need to scan qr the codes (and be **very** fast at it), so this milestone is more of "explore the possibilities" and come up with a reasonable plan for future regarding cross-platform camera support.
---
layout: wip
layout: cp
title: Three Months of Translation Coordination
author: netrik182
date: December 7, 2021
......@@ -15,18 +15,22 @@ milestones:
status: finished
- name: February
funds: 15
done:
status: unfinished
done: 12 February 2025
status: finished
payouts:
- date: 5 January 2022
amount: 15
- date: 8 February 2022
amount: 15
- date:
amount:
- date: 12 February 2025
amount: 15
---
### Proposal closure / funds reallocation 1st Feb 2025
The remaining 15XMR from this proposal have been transferred to [v1docq47](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests?scope=all&state=merged&author_username=v1docq47)
## Translation Coordinator for the Monero Project
My first proposal is now completed and I would like to continue working as translation coordinator for the upcoming months. You can read more about the initial proposal [here](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/260), also read the reports in the comments and on [reddit](https://www.reddit.com/r/Monero/comments/qqqoch/ccs_report_translation_coordinator/).
......
---
layout: wip
layout: cp
title: ETH-XMR Atomic Swap Development
author: noot
date: Dec 4 2021
......@@ -15,24 +15,24 @@ milestones:
status: finished
- name: DLEq integration
funds: 12 XMR
done:
status: unfinished
done: 1 May 2022
status: finished
- name: Integration testing
funds: 8 XMR
done: 21 March 2022
status: finished
- name: Network testing
funds: 8 XMR
done:
status: unfinished
done: 24 May 2022
status: finished
- name: Pre-print paper and additional research
funds: 5 XMR
done:
status: unfinished
done: 23 June 2022
status: finished
- name: UI
funds: 10 XMR
done:
status: unfinished
done: 23 June 2022
status: finished
payouts:
- date: 28 January 2022
amount: 8
......@@ -40,14 +40,12 @@ payouts:
amount: 5
- date: 22 March 2022
amount: 8
- date:
amount:
- date:
amount:
- date:
amount:
- date:
amount:
- date: 27 May 2022
amount: 20
- date: 29 June 2022
amount: 5
- date: 29 June 2022
amount: 10
---
# Summary
......
---
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
---
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.**
---
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.