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
  • zhangyijia2022/openenet-ms-01-monero-space-decentralized-satellite-network
  • kasamantin/openenet-ms-01-monero-space-decentralized-satellite-network
209 results
Show changes
Showing
with 1766 additions and 36 deletions
---
layout: cp
title: mj part time coding Q4 2021
author: mj
date: Oct 20, 2021
amount: 72.0 XMR
milestones:
- name: Month 1
funds: 24.0 XMR
done: 30 November 2021
status: finished
- name: Month 2
funds: 24.0 XMR
done: 31 December 2021
status: finished
- name: Month 3
funds: 24.0 XMR
done: 29 January 2022
status: finished
payouts:
- date: 4 December 2021
amount: 24
- date: 5 Jan 2022
amount: 24
- date: 26 February 2022
amount: 24
---
# What
In the same way as previously, I propose to work for 3 months, spending 30 hours a week on Monero Core, specifically on topics such as (in this order):
- statistical simulation (see [Proposal](#Proposal))
- addressing user issues (whenever I can help)
- enabling and helping new developers
- code reviews
- CI fixes
- extending my [Monero health report](http://cryptog.hopto.org/monero/health/)
- adding Monero-GUI to the health report
- general firefighting, whatever problems we face in near future
# Why
I need to raise the stakes unfortunately, since I'm strongly considering ditching my job, which became a pain in my back. This means, that I will be more dependent on the XMR money. Also, since I live in Western Europe, I pay my bills in EUR, which is seemingly going down against USD in a long term trend.
I normally hate hearing from people, who I have to hire to do things, which they can do better than me, that "they Have to earn more". I prefer saying first what additional stuff I'll deliver. Since my job will not get into the way as it did before, I will have more mental capacity to learn and read about the internals of Monero (outside of the proposed 30h/w). So far I've been doing (and gaining experience in) a lot of support tasks and I'm happy with the results as far as they can be reviewed and merged by the Maintainers. However there are now also some new challenges in Monero, which deal with statistics. I have some self-taught knowledge the field and I could provide some time series simulations, that would help in verifying if a given statistician's (or my) solution is able to yield the expected results in multiple alternative scenarios, as opposed to relying on a fixed history, which always leads to [overfitting](https://en.wikipedia.org/wiki/Overfitting). Please refer to the wonderful work of [Nassim Nicholas Taleb](https://en.wikipedia.org/wiki/Nassim_Nicholas_Taleb), especially [Fooled by Randomness](https://en.wikipedia.org/wiki/Fooled_by_Randomness) for more background. I already have a working software for such simulations, but it has to be adapted to fit Monero. I'd gladly reuse it for you guys, while you'd only pay for the adaptation itself. I think it's a good deal. I've been working on this software for many years for the purpose of statistical analysis of financial data, and a huge amount of them.
Some more details and summaries of other work packages are below:
## Statistical simulator
Here are the most relevant features of the simulator, that I'd adapt for Monero:
- Parallel Monte-Carlo simulation of alternative scenarios. The result of such a simulation are median and standard deviation of all experiments (in other words: the expected value as well as best and worst case scenario)
- The resulting value(s) are of a unit, defined by whatever objective function that is being fed into the simulator. In my current case of the financial simulation, it's the trading profitability.
- Smooth interfacing with Python (either via Boost or TCP), as Python is the (reasonable) language of choice for Statisticians. This means, that the Statisticians will not have to immediately rewrite their code to C++, if they want to have them checked by a very fast C++ simulator, compared to an analogous task, performed by Python code.
- Very fast loading of serialized data
The current visuals of my simulator can be seen below:
### Visualization
The visualization allows to take a closer look at what happens on the lowest level:
![QT](http://cryptog.hopto.org/monero/sim/sim-qt.png)
### Configuration
The current configuration UI, which produces serializable configuration files:
![Cfg](http://cryptog.hopto.org/monero/sim/sim-config.png)
### Evaluation
A console program, which performs the evaluation on larger data in parallel and joins them, plotting the result in the console:
![Test](http://cryptog.hopto.org/monero/sim/sim-test.png)
### Reporting
An HTML report is being generated after each evaluation. Here's how it currently looks:
A compound report, like in the console evaluation:
![Rep1](http://cryptog.hopto.org/monero/sim/sim-report-whole.png)
An individual report for each component:
![Rep2](http://cryptog.hopto.org/monero/sim/sim-report-indiv.png)
## CI
Me and the team were able to fix the prevailing [FreeBSD ccache issue](https://github.com/monero-project/monero/pull/7832). I also [separated the caches](https://github.com/monero-project/monero/pull/7780) based on how often they have to be recreated, which in turn saved space, so that GitHub doesn't have to purge them as often as before. All this together lead to a lot quicker reactions.
I don't see a potential for improvements of the CI anymore, which makes me happy. We can work relatively efficiently now, offsetting a lot of testing onto the CI without having to wait for a long time, nor having a bad feeling about abusing the service.
However, as soon as an unpredictable problem appears on the CI, I'm ready to address it.
## Enabling new devs
I helped in adaptation of Monero for RPi4 in the last month. I found it encouraging to work with people, who know what they want and are able to react lively. I spent some time on introducing new devs into the project, but somehow they gave up. OTOH, many new Monero devs, who didn't give up, to say the least, often message me privately with C++ questions, that I'm always happy to answer. I'd bet a lot of XMR, that it saves them a lot of frustration and time of own research. I'll happily keep doing it all.
## Health report
- I extended my [Monero health report](http://enjo.hopto.org/pub/monero/) with the Memory consumption (for compilation) report lately uncovering a huge RAM consumption of source files like `wallet2.cpp`. [See here](http://cryptog.hopto.org/monero/health/data/753dc901a/753dc901a-mem-usage-prod.txt).
- The report will be extended to cover Monero-GUI
- I will keep adding next tools into Monero codebase itself, whenever I decide, that they will have reached a production-ready state
# Who
mj, I have been contributing to Monero-core since 2020 with 73 merged commits. Here is a list of my previous work:
CLI contributions: https://github.com/pulls?q=is%3Apr+author%3Amj-xmr+archived%3Afalse+is%3Amerged+
## Previous reports
Here is a list of the previous reports, that describe my completed or started tasks in more detail:
- [Report 01](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/200#note_10764)
- [Report 02](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/200#note_10860)
- [Report 03](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/200#note_10954)
- [Report 05](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/231#note_11248)
- [Report 06](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/231#note_11421)
- [Report 07](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/231#note_11662)
Previous CCS: https://ccs.getmonero.org/proposals/mj-part-time-2021-q3.html
# Proposal
In Q4, I am able to realistically spend 30 hours a week on Monero. I arranged everything so, that the Q4 and January will be easy on me, so I won't have to prolong the work (and payment) like I had to do it in Q3. I'd like to start in November.
I propose a wage of 45 €/h for 3 months. As of 20.10.2021 the XMR/EUR is at around 220 €. This would make a total of:
45 €/h * 30 h/week * 4 weeks * 3 months / 220 XMR/EUR = 73.6 XMR, rounded down to be divisible = 72 XMR
Cheers!
# Expiration date
31 Jan, 2022
---
layout: cp
title: mj part time coding Q2 2022
author: mj
date: Mar 01, 2022
amount: 102.0 XMR
milestones:
- name: Month 1
funds: 34.0 XMR
done: 30 March 2022
status: finished
- name: Month 2
funds: 34.0 XMR
done: 10 May 2022
status: finished
- name: Month 3
funds: 34.0 XMR
done: 18 June 2022
status: finished
payouts:
- date: 2 April 2022
amount: 34
- date: 18 May 2022
amount: 34
- date: 4 July 2022
amount: 34
---
# What
I propose to work for 3 months, spending 30 hours a week on Monero Core and Monero GUI, specifically on topics such as (in this order):
- reviewing the Monero Core and GUI code
- enabling and helping new developers
- providing more documentation for new devs
- CI fixes
- addressing user issues (whenever I can help)
- benchmarking [tsqsim](https://github.com/mj-xmr/tsqsim) (although this one is arguable)
- regenerating and extending my [Monero health report](http://cryptog.hopto.org/monero/health/)
- adding Monero-GUI to the health report
- general firefighting, whatever problems we face in near future
# Why
Over the last 3 month period, I've been fully focused on developing my [tsqsim](https://github.com/mj-xmr/tsqsim) tool for Monero Research Lab's [OSPEAD](https://ccs.getmonero.org/proposals/Rucknium-OSPEAD-Fortifying-Monero-Against-Statistical-Attack.html) project. Even though I did occasionally review new code in Monero Core and GUI, a few members noted that since I was being focused on the tool so much, they felt developer resources being dragged away from Core/GUI. I'd gladly take it as a compliment :>
The current state of tsqsim is "usable", but not yet perfect. To unleash its full potential, some more work has to be put in: I estimate ~2-4 months. However this can be scheduled for later (and half-time) as well, while the OSPEAD research could already start, based on the current state of tsqsim.
Therefore in the next 3 months, I'd like to catch up with the usual maintenance. Additionally, I'd like to continue enabling new devs, by pointing them to documentation, explaining and extending it. Previously, I was helping new devs in the #monero-dev channel. Just recently I noticed, that there's quite a crowd awaiting directions in the Recruitment Matrix Channel, formed at the end of last year by @Rucknium (correct me if I'm wrong). I promised them, that I'd be available from March for either 1-on-1 sessions or to answer general questions in the channel.
## Benchmarking tsqsim
A special sub-task of the quarter would be benchmarking the tsqsim, requested by @selsta and @bigbklynballs. Even though C and C++ remain the fastest languages (yielding only to Assembler), I'm of the opinion, that the USP of tsqsim is the ability of setting up controlled experiments, without the need of them to be coded by the Researcher. This fact will be reflected by the benchmark, or more generally then: a comparison. While the user @bigbklynballs suggested benchmarking tsqsim against [all of his proposed 10 alternatives](https://libera.ems.host/_matrix/media/r0/download/libera.chat/ffa8bb5c2f97fd1ff5b9990a70f139ad96586270), which were:
- https://github.com/statsmodels/statsmodels
- https://github.com/rapidsai/cuml
- https://github.com/h2oai/h2o4gpu
- https://github.com/alkaline-ml/pmdarima
- https://github.com/timeseriesAI/tsai
- https://github.com/facebookresearch/Kats
- https://github.com/unit8co/darts
- https://github.com/winedarksea/AutoTS
- https://github.com/alan-turing-institute/sktime
- https://github.com/linkedin/greykite
, I'll spare the Community's funds by restricting the benchmarking process to 1 or 2 of the above tools and then ask for further wishes.
# Who
mj, I have been contributing to Monero-core since 2020. Here is a [list of my previous work](https://github.com/pulls?q=is%3Apr+author%3Amj-xmr+archived%3Afalse+is%3Amerged+), all related to Monero, even if it got upstreamed.
## Previous reports
Here is a list of the previous reports, that describe my completed or started tasks in more detail:
- [Report 01](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/200#note_10764)
- [Report 02](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/200#note_10860)
- [Report 03](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/200#note_10954)
- [Report 04](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/231#note_11248)
- [Report 05](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/231#note_11421)
- [Report 06](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/231#note_11662)
- [Report 07](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/266#note_14040)
- [Report 08](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/266#note_14436)
- [Report 09](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/266#note_14671)
[Previous CCS Proposal](https://ccs.getmonero.org/proposals/mj-part-time-2021-q4.html)
[Postponed CCS Proposal (tsqsim)](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/283)
# Proposal
I will spend 30 hours a week on Monero for the next 3 month period, starting from 1st March.
I propose a wage of 45 €/h for 3 months. As of 01.03.2022 the average between the opening and closing price of XMR/EUR was at (159.850 + 151.990)/2 = 155.92 € [according to investing.com](https://www.investing.com/crypto/monero/xmr-eur-historical-data). This would make a total of:
45 €/h * 30 h/week * 4 weeks * 3 months / 155.92 XMR/EUR = 103.899 XMR. Rounded down to be divisible by 3 -> 102 XMR.
Cheers!
# Expiration date
30 Jun, 2022
---
layout: cp
title: monero-bash, a wrapper for monero written in bash, for Linux
author: hinto-janaiyo
date: March 24, 2022
amount: 10.0 XMR
milestones:
- name: Integrated P2Pool Mining
funds: 5 XMR
done: 30 April 2022
status: finished
- name: RPC/Daemon API integration
funds: 3.5 XMR
done: 30 April 2022
status: finished
- name: Mining quickstart commands
funds: 1 XMR
done: 30 April 2022
status: finished
- name: Automated encrypted wallet backup
funds: 0.25 XMR
done: 30 April 2022
status: finished
- name: Auto GPG key verification for binaries
funds: 0.25 XMR
done: 30 April 2022
status: finished
payouts:
- date: 30 April 2022
amount: 10
---
# Intro
Hi everyone, I'm hinto. This is my first CCS Proposal.
I would like to develop directly for Monero, but unfortunately: I cannot code. With that said, I've setup Monero nodes and miners on many machines for others and myself, and after a while, ended up making tons of Bash scripts to automate these processes.
I rewrote a couple scripts to make them usable by anyone and put them in the public:
- [XMRig-Auto-Build, for downloading/building everything needed to build XMRig](https://github.com/hinto-janaiyo/XMRig-Auto-Build)
- [monero-toolchain, a link filterer that always downloads the latest releases of monero-related software](https://github.com/hinto-janaiyo/monero-toolchain)
I'd like to receive support through this CCS to continue on a more ambitious project: `monero-bash`
## What
[monero-bash](https://github.com/hinto-janaiyo/monero-bash) is a wrapper for monero written in bash, for Linux.
monero-bash does what bash normally does:
**it glues together multiple programs in a more automatic fashion, in this case:**
- monerod
- monero-wallet-cli
- monero-rpc
- (p2pool planned...)
monero-bash abstracts `monero-cli` commands into interactive prompts and `linux-like` syntax
while monero-bash is helpful for people who want everything automated, it's also just as powerful as monero-cli because:
~~~
it is essentially a bunch of bash scripts invoking monero-cli
~~~
and so, any `monerod.conf` or `monero-wallet-cli.conf` that may be in your `.bitmonero` folder, can be used by monero-bash
## Features
**currently implemented:**
- Automatic `monero` release upgrades, verified with SHA256SUMS
- Software and wallet management
- Easy wallet/daemon control
- Price stats from API
**to be added:**
- Automatic P2Pool mining
- RPC/Daemon API integration
- Mining quickstart commands
- Encrypted wallet backups
- GPG key verification for binaries
## Issues
`monero-bash` runs into problems much like [systemd](https://en.wikipedia.org/wiki/Systemd):
There are massive conveniences to having a single program manage and abstract everything for an end user, however, that funnels all the trust onto that single program. Although... `systemd` is a highly adopted system-manager on Linux, `monero-bash` is a niche script-system for Monero *from some random person.* So, the question might be asked:
## But, Why?
I think something like `monero-bash` would give a nice and easy bootstrap to people who normally wouldn't have manually setup a node or setup P2P mining. Another (maybe selfish) reason is that I'm making this to actually use it myself! Running `monerod`, `monero-wallet-cli`, `monero-rpc`, `XMRig` and `P2Pool` on multiple headless machines makes me wish there were a more central program to manage it all.
## Security
As the person who will be making this, I obviously have no problems using it, however, even I would be wary of using other's supposedly "safe" scripts to manage sensitive things like Monero. Thankfully since it's just Bash, anyone that uses Linux (or macOS,BSD) will most likely be able to audit everything. If there are `spooky` looking functions or variables, I'd be happy to explain its purpose and what it does. If something looks over-complicated, it's not on purpose, I'm just bad at bash.
## End-Game & Proposal
I'd like for:
- Running a Monero Node
- Managing Wallets
- Upgrading and Verifying Monero-CLI Binaries
- Mining on P2Pool as the Default
to be as simple as running a couple commands.
I'll be working for however long it takes to satisfy these milestones:
- 5.0 XMR: Integrated P2Pool Mining
- 3.5 XMR: RPC/Daemon API integration
- 1.0 XMR: Mining quickstart commands
- 0.25 XMR: Automated encrypted wallet backup
- 0.25 XMR: Auto GPG key verification for binaries
for a total of 10XMR, regardless of fiat pricing.
[For full details of the current version, here is the GitHub.](https://github.com/hinto-janaiyo/monero-bash)
Feedback would be appreciated.
---
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
amount: 43.2
milestones:
- name: MLSAG
funds: 14.4
done: 31 May 2022
status: finished
- name: CLSAG
funds: 14.4
done: 3 July 2022
status: finished
- name: Seraphis / Optimizations / Functional website delivery
funds: 14.4
done: 4 September 2022
status: finished
payouts:
- 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.
Check the initial scratch [here](https://criptando.pythonanywhere.com/).
I would like your support to finish it :)
## What and Why ?
I will try to address the following issues:
1) Provide solid information about inflation.
This project is highly focused on building the minimum necessary tools in Python to prove that there is no money leakage (inflation) occurring or that has occurred. Therefore, the community is welcome to use the tools provided here and also make improvement suggestions on how to answer this question in the most decisive way.
2) Educational material.
This work also intends to convey the message that Monero is as safe or more as Bitcoin (cryptographically speaking). Therefore some educational material is provided for the layman and for someone looking to understand the code. Convincing someone about something may require different levels of explanations. This work tries to address this issue.
3) Provide more transparency and ease the fear of users and investors.
Nobody heavily invests into something that they do not understand. This work provides more transparency and education on how the blockchain works with the focus on the inflation issue. Therefore, users would feel safer by investing and using Monero.
4) Abstraction of the C++ code and further implementations using Python.
This work also gives more independence from the C++ code, which the great majority of people heavily relies on to verify the blockchain. If useful functions are implemented here, it could also help, in the future, other people to make different implementations like wallets and nodes in Python.
5) Overview of blockchain history focused on the inflation issue.
Any successful project has to be able to tell its history in the most detailed way for the newcomers that did not live the events that happened in the past. Therefore, scanning the whole blockchain looking for leakages and providing some educational material with codes, some stats and insights is crucial not only for the new members but actually for anyone who wants to revisit the history.
## Who
- I would like to stay anonymous for the moment. I believe that the goal of the CCS is to fund an idea instead of a person so if I do not do the job, the CCS can fund someone else to do it in the way it was proposed here.
- I have never contributed to Monero and I actually got on-board recently although I know its existence for some years.
- I started investigating after this post on [reddit](https://www.reddit.com/r/Monero/comments/s9z67a/again_about_the_inflation/).
- I have a broad set of experiences like web design, Python coding, applied math and economics.
- I am highly motivated to work on this project as it is almost an existential question for me.
- I am pretty sure that I am capable of doing it following the proposed time schedule as I have been working in this project for the past two months already.
## About the proposal
First, I would like to thank everyone in the MRL channel for pointing me some directions. I believe that basically what needs to be done is the creation of Python scripts and educational materials in order to: check the ring signatures, check the amounts involved, check the uniqueness of key images and check the emission curve.
These tasks have to be done for the Pre-RingCT era, MLSAG and CLSAG.
As I have already done a scratch for the Pre-RingCT (v1) era (it is not ready yet but I strongly recommend you to check out the [temporary version](https://criptando.pythonanywhere.com/) to have an idea how the final product will look like), I still need to do improve the Pre-RingCT era and create the necessary material for the MLSAG and CLSAG. I also propose to create some educational material and scripts for Seraphis.
This work does not intend to end the discussion about inflation in Monero, it is quite the opposite, it looks for providing tools and educational material so people can have the same base for a serious and structured discussion about it. I do not expect to deliver the message that you should blindly trust in Monero but I expect to deliver a message which will raise the awareness on the inflation issue.
I will do my best to reply in a meaningful way the concerns of the community and I also will be constantly in touch with the developers and the ones that have much more knowledge than me (they have been really nice and kind so far) to explain the inflation issue in the best way.
## Importance for the community
- Give some material and orientation for the ones looking to increase their understanding about the Monero blockchain with the focus on the inflation issue.
- Create Python functions (ring signature verifiers and others) to check the real data stored in the blockchain
- Give more transparency and explanation to the verification process of a transaction
- Reduce the fear of investors that do not understand how Monero can be transparent and at the same time private.
## Timeline and payouts
First delivery: Codes, nice explanation and some stats about MLSAG /
Date: End of May /
Amount: 14.4 XMR
Second delivery: Codes, nice explanation and some stats about CLSAG /
Date: End of June /
Amount: 14.4 XMR
Third delivery: More codes and explanations (Seraphis), clean website, optimizations and corrections /
Date: End of August /
Amount: 14.4 XMR
I propose to work for 18 USD per hour, 30h per week, for 16 weeks. Which means 18*30*16 = 8640 USD / 200 USD = 43.2 XMR
Total: 43.2 XMR
I will also pay for the costs to host the website and buy a meaningful domain name for the project.
## About deliveries
I will make all the content (codes, images, texts, ...) available and free to use, modify, share and do whatever you want.
As soon as I finish some task, I will make them available.
## Expiration Date
It would be nice if it get funded before 30.04.2022 so I can keep the expected timeline. Thank you very much in advance.
---
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: wip layout: cp
title: Monero FM (community run radio project) title: Monero FM (community run radio project)
author: rehrar and needmoney90 author: ajs
date: September 7, 2020 date: September 7, 2020
amount: 35 amount: 35
milestones: milestones:
- name: Initial payout for license acquisition - name: Payout for license acquisition, initial expenses
funds: 17.5 funds: 17.569028
done: done: 7 August 2021
status: unfinished status: finished
- name: Payout for music after licenses are secured - name: Payout excess to genfund
funds: 17.5 funds: 17.430972
done: done: 12 February 2022
status: unfinished status: finished
payouts: payouts:
- date: - date: 8 August
amount: amount: 17.569028
- date: - date: 12 February 2022
amount: amount: 17.430972
--- ---
# Monero.FM, the Monero community run radio station. # Monero.FM, the Monero community run radio station.
...@@ -70,4 +70,4 @@ Once annual estimated costs are achieved for the year (totaling $2666 as denoted ...@@ -70,4 +70,4 @@ Once annual estimated costs are achieved for the year (totaling $2666 as denoted
Monero FM will leave 'profit mode' upon the next calendar year until the sustenance costs are recouped again. Monero FM will leave 'profit mode' upon the next calendar year until the sustenance costs are recouped again.
Note: It is not guaranteed that Monero FM will EVER go into profit mode. Please remember that this is an online radio station, which typically have low margins, especially for niche communities like cryptocurrency. Note: It is not guaranteed that Monero FM will EVER go into profit mode. Please remember that this is an online radio station, which typically have low margins, especially for niche communities like cryptocurrency.
\ No newline at end of file
---
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" title: "moneromooo: three months from December 2020"
author: moneromooo author: moneromooo
date: 05 December 2020 date: 05 December 2020
...@@ -15,11 +15,13 @@ milestones: ...@@ -15,11 +15,13 @@ milestones:
status: finished status: finished
- name: third month - name: third month
funds: 33.34% (75 XMR) funds: 33.34% (75 XMR)
done: done: 17 May 2023
status: unfinished status: finished
payouts: payouts:
- date: 17 June 2021 - date: 17 June 2021
amount: 150 amount: 150
- date: 17 August 2023
amount: 75
--- ---
Hi, 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: cp
title: Translation Coordinator for the Monero Project
author: netrik182
date: October 6, 2021
amount: 11
milestones:
- name: One month work
funds: 11
done: 3 December 2021
status: finished
payouts:
- date: 8 December 2021
amount: 11
---
## Translation Coordinator for the Monero Project
Translations have always been an important part of this community and an essential tool to spread Monero to everyone. ErCiccione has been the manager of this workgroup for a long time (see their proposals at the bottom) and recently has been looking for someone to take on these responsibilities as they are focusing their time on other projects now (e.g. Haveno).
The Monero Project has always benefited from having well structured and consistent translations across its many resources thanks to ErCiccione and many other contributors/translators. After they announced on #monero-translations that they are looking for someone to take care of it, I want to step in and keep that going.
## About me
I have been involved with FLOSS and Monero-specific translation work for more than 5 years now. I also run https://monerobrasil.org/ and [#monero-brasil](https://matrix.to/#/#monero-brasil:monero.social).
### My profiles
- repo.getmonero.org [profile](https://repo.getmonero.org/users/netrik182/activity) where I contributed before Pootle (and now Weblate) was a thing.
- Weblate [profile](https://translate.getmonero.org/user/netrik182/) where I contribute to getmonero.org, Monero GUI translations, Monero Means Money, and other Dr. Kim's videos, etc.
- GitHub [profile](https://github.com/netrik182) where most things were done.
### Previous Work
- **Monero Ecosystem Translations:** Provided the transcription, captions and translations. As well as the terminology guides. You can check all [here](https://github.com/monero-ecosystem/monero-translations/pulls?q=netrik182) and [here](https://github.com/ajs-xmr/moneromovie/pulls?q=is%3Apr+author%3Anetrik182+).
- **Monero Website and Monero GUI:** Most of my contributions to GUI Wallet are on Weblate. Contributions I made on GitHub [here](https://github.com/monero-project/monero-gui/pulls?q=netrik182+) and [here](https://github.com/monero-project/monero-site/pulls?q=netrik182).
- **Monero Outreach:** I contributed with translation, transcription and revision of many [outreach materials](https://github.com/monero-ecosystem/outreach-docs/pulls?q=netrik182).
- **Monerujo:** Translation and review of [Monejuro](https://github.com/m2049r/xmrwallet/pulls?q=netrik182).
- **AgoraDesk/LocalMonero:** [Translation and review](https://github.com/AgoraDesk-LocalMonero/translation/pulls?q=is%3Apr+author%3Anetrik182) of their website.
- **Mastering Monero:** [Translation](https://github.com/monerobook/monerobook/pull/94) and [review](https://github.com/monerobook/monerobook/pull/93). Also see [the book itself](https://netrik182.gitlab.io/docs-monerobrasil.org/masteringmonero/) and the [CCS proposal](https://ccs.getmonero.org/proposals/netrik182-mastering-monero-translation.html).
## Responsibilities
Things the manager must take care of are:
1. Manage translators and their work on Weblate for the following projects:
- **Community:** https://translate.getmonero.org/projects/community/
- **Getmonero:** https://translate.getmonero.org/projects/getmonero/
- **Getmonero user guides:** https://translate.getmonero.org/projects/getmonero-user-guides/
- **Monero CLI and GUI:** https://translate.getmonero.org/projects/monero/
2. Manage translators and their work on GitHub for the following projects:
- **Monero Translations:** https://github.com/monero-ecosystem/monero-translations
- **Monero Website:** https://github.com/monero-project/monero-site
- **Monero GUI Guide (translation only):** https://github.com/monero-ecosystem/monero-GUI-guide
3. Maintain a list of contributors and their working language;
4. Manage translations on Weblate (this includes adding notes and keeping an eye on the entire platform for spam, etc.);
- Making sure strings have clarifications and explanations where necessary;
- Communicate with ErCiccione when translations are ready so they can push them to the repository (where they are supposed to be: /monero, /monero-site, /monero-gui, /monero-translations for subtitles);
5. Take care of translations-related CCS (the current system is not optimal and needs to be improved. See more bellow.);
6. Unify, update and maintain documentation on different repositories;
- [/monero](https://github.com/monero-project/monero/blob/master/docs/README.i18n.md) instructions;
- [/monero-translations](https://github.com/monero-ecosystem/monero-translations) instructions;
- [/monero-gui](https://github.com/monero-project/monero-gui#translations) instructions;
- [/monero-site](https://github.com/monero-project/monero-site#translation) instructions;
- [Weblate](https://github.com/monero-ecosystem/monero-translations/blob/master/Weblate.md) instructions;
- [Translations tips](https://github.com/monero-ecosystem/monero-translations/blob/master/translation-tips.md);
- [Monerujo](https://github.com/monero-ecosystem/monero-translations/blob/master/translate-monerujo.md) instructions;
7. Answer questions and coordinate people in the chat-rooms (#monero-translations on Libera/Matrix);
8. Make sure when there are translations available on Weblate, they are pushed upstream (repository they belong to);
9. Provide updates to the community about the state of the translations and workgroup-related activities during #monero-community meetings;
10. Issue progress reports on a monthly basis as GitLab comments and share within the community (e.g. Reddit/Matrix/IRC).
## Limitation of Scope
ErCiccione will keep managing the backend side of things (update Weblate, bug issues, etc). I will maintain the languages on Weblate, help and find translators, update the documentation, etc. as highlighted above.
## Translation-related CCS proposals
One of the first tasks of this role will be to rethink the whole process of contributors using the CCS to fund their translation efforts. We have had problems with low quality work in the past and although some rules have been discussed and laid out with the help from Core, I want to focus on defining and _enforcing_ some basic rules for translation-related CCS's in the future, accepting work from:
- Translators with a provable portfolio as professional translators
- Contributors of the Localization Workgroup that have a track record of delivering high quality translations (work that has been reviewed by others and deemed of high quality, for example)
The end goal is to guarantee the Monero Project has its resources translated and that these translations are of high quality. We plan to establish a hybrid approach in which community members could contribute if they wanted to (as volunteers or paid work) given the rules above and in case we fail to meet the above requirements for any given language a.k.a. these contributors do not exist or are of bad quality, they could be replaced with professional resources.
## Funding
I want to open this CCS to work for the first month as a trial run and later on if the Community thinks it was worth it, I can move to 3-months proposals for long-term commitment. This proposal will consist of 20h/week for 4 weeks at a rate of 30€/h, with a total of 11 XMR (1 xmr = 219€ at Kraken). _I will update the rate shortly before merging (if merged at all)._
## Milestones for the first month:
1. **Review, update and unify translations instructions from item 6 above:** the idea is to have a single document with all instructions laid out and then each repository could reference this _source_ material. This will simplify maintenance and also help onboarding new contributors. I think this is the most important milestone and hence it will take most of my time.
2. **Translation-work coordination:** this covers the whole process of managing translations, community and outsourced translators and so on. It is the bulk of responsibilities and must be performed continually. I would also put in here the community reports/updates on a monthly basis and participation on -community meetings.
## Future ideas
1. **Work with Core and ErCiccione to grab statistics from Monero Website:** the idea is to assess visitors preferred language and use that information to focus on which language we need to prioritize and also which resources are most valuable to translate first. This will enable us to create a prioritization list of sorts.
2. **Create a Translation Fund for continued maintenance of translation work:** I have talked with some Core Team members and they expressed the possibility of a Translation Fund existing and those funds being used to outsource specific work to translation outlets in the absence of community members meeting the criteria of high quality work. Having money set apart for this specific goal together with the statistics of language/resource prioritization list will help us achieve the end goal of ensuring Monero is translated into the most needed languages.
## Expiration
October 31, 2021
## Past coordination proposals by ErCiccione for reference
- https://forum.getmonero.org/22/completed-tasks/89232/coordinator-for-localization-group-various-maintenance
- https://forum.getmonero.org/22/completed-tasks/90000/monero-localizations-coordinator-2nd-ffs
- https://forum.getmonero.org/22/completed-tasks/90271/coordinator-of-the-localization-workgroup-3-more-months-erciccione
- https://forum.getmonero.org/9/work-in-progress/90800/erciccione-coordinator-of-the-localization-workgroup-translations-another-quarter
- https://forum.getmonero.org/9/work-in-progress/91261/erciccione-coordinator-of-the-localization-workgroup
- https://ccs.getmonero.org/proposals/ErCiccione-localizations.html
- https://ccs.getmonero.org/proposals/ErCiccione-Weblate.html
---
layout: cp
title: Three Months of Translation Coordination
author: netrik182
date: December 7, 2021
amount: 45
milestones:
- name: December
funds: 15
done: 31 December 2021
status: finished
- name: January
funds: 15
done: 31 January 2022
status: finished
- name: February
funds: 15
done: 12 February 2025
status: finished
payouts:
- date: 5 January 2022
amount: 15
- date: 8 February 2022
amount: 15
- 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/).
As stated before, the Monero Project has always benefited from having well structured and consistent translations across its many resources and I want to keep that going.
### My profiles
- repo.getmonero.org [profile](https://repo.getmonero.org/users/netrik182/activity)
- Weblate [profile](https://translate.getmonero.org/user/netrik182/)
- GitHub [profile](https://github.com/netrik182)
- GitLab [profile](https://gitlab.com/netrik182)
### Previous Work
You can read a detailed list in my first proposal.
## Responsibilities
Responsibilities remain the same as before, summarized as:
1. Manage translators and their work on Weblate for the following projects:
- **Community:** https://translate.getmonero.org/projects/community/
- **Getmonero:** https://translate.getmonero.org/projects/getmonero/
- **Getmonero user guides:** https://translate.getmonero.org/projects/getmonero-user-guides/
- **Monero CLI and GUI:** https://translate.getmonero.org/projects/monero/
2. Manage translators and their work on GitHub for the following projects:
- **Monero Translations:** https://github.com/monero-ecosystem/monero-translations
- **Monero GUI Guide (translation only):** https://github.com/monero-ecosystem/monero-GUI-guide
3. Maintain a list of contributors and their working language;
4. Take care of translations-related CCS (the current system is not optimal and needs to be improved. See more bellow.);
5. Maintain translation documentation on different repositories;
- [/monero](https://github.com/monero-project/monero/blob/master/docs/README.i18n.md)
- [/monero-translations](https://github.com/monero-ecosystem/monero-translations)
- [/monero-gui](https://github.com/monero-project/monero-gui#translations)
- [/monero-site](https://github.com/monero-project/monero-site#translation)
- [Weblate](https://github.com/monero-ecosystem/monero-translations/blob/master/Weblate.md)
- [Translations tips](https://github.com/monero-ecosystem/monero-translations/blob/master/translation-tips.md)
- [Monerujo](https://github.com/monero-ecosystem/monero-translations/blob/master/translate-monerujo.md)
6. Answer questions and coordinate people in the chat-rooms (#monero-translations on Libera/Matrix)
7. Make sure when there are translations available on Weblate, they are pushed upstream (repository they belong to)
8. Provide updates to the community about the state of the translations and workgroup-related activities during #monero-community meetings
9. Issue progress reports on a monthly basis as GitLab comments and share within the community (e.g. Reddit/Matrix/IRC)
## Limitation of Scope
Core Team is looking for someone to manage the backend structure as ErCiccione announced they're stepping down (update Weblate, bug issues, etc). I will maintain the languages on Weblate, help and find translators, update the documentation, etc. as highlighted above.
## Milestones and Funding
Now I would like to keep this CCS as 3-months proposals for long-term commitment. This proposal will consist of about 20h/week from December 1st, 2021 to February 28th, 2022 at a rate of 30€/h I'm rounding to 45 XMR (1 xmr = 170€ at Kraken). **Translation coordination** work covers the whole process of managing translations, community members, weblate and the repositories. We're are still having many merging conflicts on Weblate and some integrations are not working properly. Resolving that will ensure we have a friction-free process.
## Expiration
December 31, 2021
---
layout: cp
title: ETH-XMR Atomic Swap Development
author: noot
date: Dec 4 2021
amount: 56 XMR
milestones:
- name: Maintainence of existing codebase
funds: 5 XMR
done: 5 February 2022
status: finished
- name: Contract improvements
funds: 8 XMR
done: 27 January 2022
status: finished
- name: DLEq integration
funds: 12 XMR
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: 24 May 2022
status: finished
- name: Pre-print paper and additional research
funds: 5 XMR
done: 23 June 2022
status: finished
- name: UI
funds: 10 XMR
done: 23 June 2022
status: finished
payouts:
- date: 28 January 2022
amount: 8
- date: 8 February 2022
amount: 5
- date: 22 March 2022
amount: 8
- date: 27 May 2022
amount: 20
- date: 29 June 2022
amount: 5
- date: 29 June 2022
amount: 10
---
# Summary
This proposal is for the continued development of ETH-XMR atomic swaps. The milestones include continued maintence and testing of the current codebase, gas improvements, network and integration testing, and documentation. At the completion of this proposal, there will be an audit-ready pre-production release of the ETH-XMR atomic swap software, as well as a pre-print paper outlining future improvements to the protocol. The total estimated duration of this proposal is 16 weeks.
# Team
[noot](github.com/noot) will be completing milestones 1-6. Milestone 7 will be completed by [Tbaut](https://github.com/Tbaut).
### About me (noot)
Since I'm quite new to the Monero space, I figured I'd post a little bit about me here. I've been working as a professional blockchain protocol engineer for nearly 4 years (will be 4 years in March 2022). I also have a Bachelor's of Applied Science specializing in Computer Engineering from the University of Toronto. For my undergraduate thesis project, I explored adding privacy to Ethereum, which ended up with me writing a Go implementation of RingCT. Although the project didn't really go anywhere, it was my introduction to real-life cryptography and of course Monero. Since then I've been casually following Monero. I've always loved the tech and the ethos and I'm glad to finally be able to contribute to it!
I'm passionate about privacy-preserving technologies and I think Monero really is the best and only (afaik) cryptocurrency that's truly private. I hope this project will bring more users to Monero by reducing the onboarding overhead, specifically by not needing to rely on a centralized exchange. I hope this work, along with the current inspiring XMR-BTC swap work being done, will help bring in fully decentralized, peer-to-peer exchanges.
Most of my past work is focused on alternative blockchain protocol implementations, including implementations for Polkadot and Filecoin. I've also worked on Ethermint (EVM Cosmos module), a *little* bit on some ETH2 libraries, and written/tested various smart contracts in my day, which consists of most of my Ethereum experience. I've also worked on go-libp2p-noise (a handshake protocol for the p2p library libp2p) and go-schorrkel (schnorr signatures over ristretto255, used in Polkadot), both of which are now in production! The language I've used the most is Go (namely why this project is in Go), but I've also used Rust, JS, and Solidity.
Since I'll be continuing to work full-time, this project will be done on a part-time basis. As of writing I'm the only person who will be working on this. I estimate I'll be able to put in ~15 hours per week, which might vary week-to-week depending on how busy I am.
# Motivation
Atomic swaps are a method for trustlessly exchanging funds across blockchains. An ETH-XMR atomic swap will allow for users to, in a trustless and completely decentralized manner, exchange Ether for Monero. This connects the leading smart contract blockchain (and the home of defi) with the leading privacy-preserving blockchain. Along with the BTC-XMR atomic swaps, this will allow for completely decentralized cross-chain exchanges to be built that allow for XMR swaps.
# Milestones
## 1. Maintenance of existing codebase (estimated 2 weeks)
This includes:
- improved unit tests, >70% test coverage for whole repo
- inline documentation (ie. code-level docs)
- JSON-RPC API documentation
- general code cleanup
## 2. Swap contract improvements (estimated 2 weeks)
There is already a smart contract (Swap.sol) that implements the Ethereum on-chain side of the protocol. However, to reduce gas costs, this can be turned into a "factory" style contract that allows users to create swap instances without having to re-deploy a contract, thus allowing for gas savings.
This milestone includes:
- Creation of swap factory contract
- Testing and integration of contract with codebase
- Documentation on how to deploy the swap contract ot any EVM-based chain and interact with it
## 3. DLEq integration (estimated 2-4 weeks)
For background, monero uses the ed25519 elliptic curve and ethereum uses the secp256k1 elliptic curve. The current implementation of the protocol verifies that a secret corresponds to a valid public key on the ed25519 curve by performing an elliptic curve multiplication (ECMUL). There is a version of the protocol that allows for massive gas savings (~30x improvement on Claim/Refund calls) by moving some of the computation off-chain. This is achieved by allowing secp256k1 keys to be verified on-chain (instead of ed25519), while off-chain, a DLEq proof is passed by each party to the counterparty that proves that their secret corresponds to public keys on both the secp256k1 curve and the ed25519 curve.
This milestone includes:
- Completion of the DLEq version of the swap contract, which performs a secp256k1 ECMUL as the verification step
- Testing of the contract
- DLEq proof generation and verification
- either using an existing Rust library, potentially using CGO to create language bindings from Rust->Go
- or, creating a Go implementation of DLEq proof and verification
- Integration with the codebase (updates of network messages and handling of protocol steps)
A potential alternative to using an existing Rust library is to write a DLEq implementation in Go. This would be preferred in the long run as it will be easier for users to build (as they would only been one language installed) and usage of CGO can cause linking issues during build on different platforms. As well as a developer, it's easier to maintain. I would prefer to create a Go implementation for the aforementioned reasons, although it would take longer than using an existing library. However, in the long run, I believe it would save developer hours.
## 4. Integration testing (estimated 2 weeks)
This includes:
- End-to-end testing of the swap from both parties's point of view and for all possible claim/refund cases.
- Will be in the form of Go test cases.
## 5. Network testing and infrastructure (estimated 3 weeks)
This includes:
- setting up infrastructure (servers) to host swap nodes
- testing of a larger network of swap nodes (10+ nodes) that has many swap providers
- testing of node discovery, messaging, and swap initiation
- testing script to allow for the above cases to be run against a network
As there will likely be issues that are uncovered while testing, this milestone is assumed to include fixes for those issues.
## 6. Additional research and pre-print paper (estimated 2-4 weeks)
I would like to formalize the existing swap protocol and its variations, and as well to conduct additional research into improvements to the protocol.
This includes:
- a pre-print paper that describes the current ETH-XMR atomic swap protocol and its security guarantees
- a new version of the protocol that allows the XMR-holding party to move first, as the current protocol is limited by the ETH party needing to lock their funds first
- potential optimizations to the protocol, focusing on ethereum gas costs
- discussion of privacy implications on both the ethereum and monero sides
## 7. UI
This milestone includes an in-browser UI for interacting with the swap network.
This includes:
- displaying the current swap offers available on the network
- ability for a user to log in with a browser-based Ethereum wallet (Metamask) and take a swap offer
## In case of extra funds
If there are extra funds/time left over, this will be used to investigate the following:
- ERC20 support; ie. ability to directly swap XMR for an ERC20 token
- privacy improvements on the ethereum side
- tor support
## Licensing
The codebase is currently licensed as GPLv3 due to usage of a library that is licensed GPLv3. However, this license can be changed after the DLEq integration (milestone 3) is complete. My preference is for GPL but I will also relicense as LGPL if needed. I would like to stick with GPL or LGPL as it prevents the code from being relicensed and used in closed-source software.
## At completion
At completion of this proposal, there will be a pre-production release of the software that includes binaries for Linux, MacOS and Windows.
# Expiration date
This CCS will expire on February 4 2022.
--- ---
layout: wip layout: cp
title: Translation of Monero GUI Wallet, Getmonero (monero-site), Community (Monero Means Money (subtitles) and Sound Money, Safe Mode (subtitles)) to Greek title: Translation of Monero GUI Wallet, Getmonero (monero-site), Community (Monero Means Money (subtitles) and Sound Money, Safe Mode (subtitles)) to Greek
author: Donald A. Iljazi author: Donald A. Iljazi
date: November 9, 2020 date: November 9, 2020
...@@ -7,29 +7,23 @@ amount: 30 ...@@ -7,29 +7,23 @@ amount: 30
milestones: milestones:
- name: Milestone 1 - Completion of GUI Wallet Translation to Greek - name: Milestone 1 - Completion of GUI Wallet Translation to Greek
funds: 2 XMR funds: 2 XMR
done: done: 11 November 2020
status: unfinished status: finished
- name: Milestone 2 - Completion of monero-site Translation to Greek - name: Milestone 2 - Completion of monero-site Translation to Greek
funds: 8 XMR funds: 8 XMR
done: done: 25 November 2020
status: unfinished status: finished
- name: Milestone 3 - Completion of Monero Means Money (subtitles) Translation to Greek - name: Milestone 3 - Completion of Monero Means Money (subtitles) Translation to Greek
funds: 10 XMR funds: 10 XMR
done: done: 20 February 2021
status: unfinished status: finished
- name: Milestone 4 - Completion of Sound Money, Safe Mode (subtitles) Translation to Greek - name: Milestone 4 - Completion of Sound Money, Safe Mode (subtitles) Translation to Greek
funds: 10 XMR funds: 10 XMR
done: done: 17 April 2021
status: unfinished status: finished
payouts: payouts:
- date: - date: 2 October 2021
amount: amount: 30
- date:
amount:
- date:
amount:
- date:
amount:
--- ---
# About this Proposal # About this Proposal
...@@ -107,4 +101,4 @@ Timeline: 21/12/2020 - 10/01/2021 ...@@ -107,4 +101,4 @@ Timeline: 21/12/2020 - 10/01/2021
### Proposal Expiration Date ### Proposal Expiration Date
19/11/2020 19/11/2020
\ No newline at end of file
---
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: 6 April 2025
status: finished
- 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: 18 April 2025
amount: 14
- 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.
---
layout: cp
title: "CCS Coordinator"
author: plowsof
date: October 20th 2023
amount: 69
milestones:
- name: 2 meetings + hours worked
funds: 23 XMR
done: 14 January 2024
status: finished
- name: 2 meetings + hours worked
funds: 23 XMR
done: 14 January 2024
status: finished
- name: 2 meetings + hours worked
funds: 23 XMR
done: 17 March 2024
status: finished
payouts:
- date: 28 January 2024
amount: 46
- date: 16 April 2024
amount: 23
---
# Who?
Hello, plowsof here, I show up and try to be helpful. My [previous](https://ccs.getmonero.org/proposals/plowsof-com-rel.html) [proposals](https://ccs.getmonero.org/proposals/plowsof-ccs-coordinator-2.html) happened, i would like to make it happen again, and do more of the same things.
# What?
- Gather consensus for CCS proposals. (feedback from GitLab/IRC/Reddit).
- Organise bi-weekly meetings to discuss proposals / current events (more if necessary).
- Provide decisions in 1 month or less (Yes/No to being funded or if something has to be changed with the proposal to satisfy our community).
- Be impartial when communicating with CCS proposers - everyone gets a fair shake.
- Checking up on the WIP list to find / fix problems early (e.g. payments overdue or proposers AWOL).
- Take responsibility for the entire CCS process - It's my fault when 'things go wrong'.
- Someone who is online for several hours a day / 7 days a week that knows what's going on.
- Act as a liaison to Core - keep them informed of whats happening / poke them when required / handle their requests.
- As part of this CCS, you will also be sponsoring my work when quality assurance testing new features/bug fixes each release cycle in the GUI, CLI, and RPC wallets.
- And Getmonero.org contributions.
- Consultancy before / during / after the idea stage.
# Funding
20hr/week - 40 eur/hr with XMR at 144EUR (MA20 @ Kraken) gives 72.420 but i like 69 better so 23 XMR/milestone bringing the total requested amount to 69XMR. Maximum of 1 milestone can be claimed per month. Price fluctuation after moving to funding will have no effect.
Consider this proposal expired in the event of my untimely death / unheard of for >5 months / have not claimed all payouts in 12 months. If expired - all remaining unclaimed funds are to be donated to other CCS proposals.