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
206 results
Show changes
Showing
with 1688 additions and 31 deletions
---
layout: cp
title: "Subtitle translations for the videos Sound Money, Safe Mode and Monero Means Money into Spanish"
author: michaelizer
date: November 27, 2020
amount: 8
milestones:
- name: "Completion of Sound Money, Safe Mode (subtitles) translation into Spanish"
funds: 4
done: 31 March 2021
status: finished
- name: "Completion of Monero Means Money (subtitles) translation into Spanish"
funds: 4
done: 31 May 2021
status: finished
payouts:
- date: 26 April 2021
amount: 4
- date: 10 June 2021
amount: 4
---
## What the proposal is about?
Translation into Spanish of the following video subtitles: [Monero Means Money](https://translate.getmonero.org/projects/community/monero-means-money/) and [Sound Money, Safe Mode](https://translate.getmonero.org/projects/community/sound-money-safe-mode-subtitles/)
## Who will complete the proposal?
My name is Miguel Medina, I'm 26 years old Venezuelan studying Software Engeenering and a crypto enthusiast since 2017's boom and have been contributing to blokchain projects since then (as a translator), I worked as part of the translation team in a Community-led project named Utopian on [Steemit](https://steemit.com/@michaelizer), where I translated for several blockchain projects and tech projects of other nature. Also worked as part of the translation team for the [Rchain Cooperative](https://rchain.coop/).
## Why it is important for Monero and the community?
Spanish is the official language of 21 countries, is spoken by more than 500 million people around the world, the Spanish community in crypto is rapidly growing and those countries are adopting cryptocurrencies faster than others due to poor governance and payment limitations. I believe having this information translated into Spanish is very important (even more in these current period of time when blockchain is getting a lot of attention) to spread awareness of Monero through those communities.
## Your milestones and projected timeline
This proposal is made up of two milestones
#### **1. Completion of [Sound Money, Safe Mode (subtitles)](https://translate.getmonero.org/projects/community/sound-money-safe-mode-subtitles/) translation into Spanish**
It consists of a total of 12,404 words which means a total amount of 4 XMR
Timeline for this milestone: Completed and reviewed.
#### **2. Completion of [Monero Means Money (subtitles)](https://translate.getmonero.org/projects/community/monero-means-money/) translation into Spanish**
It consists of a total of 11,689 words which means a total amount of 4 XMR
Timeline for this milestone: Completed and pending review.
---
layout: cp
title: "Spanish translation and proofreading of the monero site, GUI/CLI wallets and User Guides"
author: michaelizer
date: May 28, 2021
amount: 12
milestones:
- name: Milestone 1 - Translation and proofreading of the Monero site
funds: 33.33% (4 XMR)
done: 15 July 2022
status: finished
- name: Milestone 2 - Translation and proofreading of the GUI and CLI wallets
funds: 41.67% (5 XMR)
done: 15 July 2022
status: finished
- name: Milestone 3 - Translation and proofreading of the user guides
funds: 25% (3 XMR)
done: 15 July 2022
status: finished
payouts:
- date: 23 July 2022
amount: 12
---
## What the proposal is about?
The purpose of this proposal is to translate what has not been translated, review what has been translated and make the necessary corrections where needed. In this way all the content uploaded to [Weblate](https://translate.getmonero.org/) would be 100% translated into Spanish.
## Who will complete the proposal?
My name is Miguel Medina, I've been around since November 2020 and worked on [these translations](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/223).
## Files to be translated
- [CLI Wallet](https://translate.getmonero.org/projects/monero/cli-wallet/es/) = 8319 words
- [GUI Wallet](https://translate.getmonero.org/projects/monero/gui-wallet/es/) = 3770 words **
- [Monero-site](https://translate.getmonero.org/projects/getmonero/monero-site/) = 11214 words *
### And these [User Guides](https://translate.getmonero.org/projects/getmonero-user-guides/)
- [Cli_wallet_daemon_isolation_qubes_whonix](https://translate.getmonero.org/projects/getmonero-user-guides/cli_wallet_daemon_isolation_qubes_whonix/es/) = 422 words **
- [Howto_fix_stuck_funds](https://translate.getmonero.org/projects/getmonero-user-guides/howto_fix_stuck_funds/es/) = 167 words **
- [Importing_blockchain](https://translate.getmonero.org/projects/getmonero-user-guides/importing_blockchain/es/) = 397 words
- [Ledger-wallet-cli](https://translate.getmonero.org/projects/getmonero-user-guides/ledger-wallet-cli/es/) = 1097 words **
- [Mine-to-pool](https://translate.getmonero.org/projects/getmonero-user-guides/mine-to-pool/es/) = 993 words
- [Monero_tools](https://translate.getmonero.org/projects/getmonero-user-guides/monero_tools/es/) = 60 words **
- [Monero-wallet-cli](https://translate.getmonero.org/projects/getmonero-user-guides/monero-wallet-cli/es/) = 1016 words **
- [Node-i2p-zero](https://translate.getmonero.org/projects/getmonero-user-guides/node-i2p-zero/es/) = 430 words
- [Offline_Backup](https://translate.getmonero.org/projects/getmonero-user-guides/offline_backup/es/) = 385 words **
- [Prove-payment](https://translate.getmonero.org/projects/getmonero-user-guides/prove-payment/es/) = 435 words **
- [Remote_node_gui](https://translate.getmonero.org/projects/getmonero-user-guides/remote_node_gui/es/) = 384 words
- [Restore_account](https://translate.getmonero.org/projects/getmonero-user-guides/restore_account/es/) = 385 words **
- [Restore_from_keys](https://translate.getmonero.org/projects/getmonero-user-guides/restore_from_keys/es/) = 302 words **
- [Securely_purchase](https://translate.getmonero.org/projects/getmonero-user-guides/securely_purchase/es/) = 758 words
- [solo_mine_GUI](https://translate.getmonero.org/projects/getmonero-user-guides/solo_mine_gui/es/) = 216 words **
- [Tor_wallet](https://translate.getmonero.org/projects/getmonero-user-guides/tor_wallet/es/) = 629 words
- [Verification-allos-advanced](https://translate.getmonero.org/projects/getmonero-user-guides/verification-allos-advanced/es/) = 1063 words **
- [Verification-windows-beginner](https://translate.getmonero.org/projects/getmonero-user-guides/verification-windows-beginner/es/) = 1111 words **
- [View_only](https://translate.getmonero.org/projects/getmonero-user-guides/view_only/es/) = 499 words
- [Vps_run_node](https://translate.getmonero.org/projects/getmonero-user-guides/vps_run_node/es/) = 191 words **
The ones ending in " ** " mean that they have been translated (mostly) so they only require revision to verify quality, the monero site ("*") is not fully translated and has some mistranslated parts. So, in total, there are **34243 words**, of which 12409 are not translated, 10620 fall into the category of (practically) revision only and 11214 belong to the monero site, so, given this small distinction in the type of work to be done, I propose the following:
$0.1/word for those where I have to translate from scratch.
$0.06/word for translating what is missing and correcting what was done wrong on the monero site.
$0.06/word for those translations that have already been done but have not been reviewed. It is mostly to review them, but also to translate what is missing.
(12409*$0.1) + (11214*$0.06) + (10620*$0.06) = $2551 at a rate of (+/-) $210/XMR gives a total of 12XMR divided in the following milestones
### Milestone 1 - Translation and proofreading of the Monero site
11214 words for a total of 4 XMR
### Milestone 2 - Translation and proofreading of the GUI and CLI wallets
12089 words for a total of 5 XMR
### Milestone 3 - Translation and proofreading of the User Guides
10940 words for a total of 3 XMR
#### Every milestone will take about two weeks each, every update and completion will be posted in the comments
---
layout: cp
title: midipoet-Oslo_Freedom_Forum_CCS_proposal.md
author: midipoet
date: April 6, 2022
amount: 8.5 XMR
milestones:
- name: Proposal funded
funds: 4.25 XMR
done: 25 April 2022
status: finished
- name: Report submitted
funds: 4.25 XMR (2.25 to midipoet, 2 to GF)
done: 24 September 2022
status: finished
payouts:
- date: 25 April 2022
amount: 4.25
- date: 28 September 2022
amount: 2.25
- date: 20 September 2022
amount: 2
---
**WHO**
I am known in the community as midipoet. I have been an active contributor for quite a number of years now, and would like to think that I have earned a level of trust from the community at large.
I have been involved in the [Monero Policy Working Group](moneropolicy.org) since its inception, contributing directly to all the [policy consultations](https://github.com/monero-policy/monero-policy.github.io/tree/master/assets/pdfs) we have done over the last year or so. - more info [here](https://www.reddit.com/r/Monero/comments/r5vodq/mpwg_final_two_responses_to_the_public/), [here](https://www.reddit.com/r/Monero/comments/qowwm4/monero_policy_working_group_response_to_the/), [here](https://www.reddit.com/r/Monero/comments/mxr15w/monero_policy_working_group_response_to_fatf/), and [here](https://www.reddit.com/r/Monero/comments/m1es4t/monero_policy_working_group_response_to_european/).
I have also conducted research on Monero, working to produce a respected journal paper for a three star academic journal. More info [here](https://www.reddit.com/r/Monero/comments/ijhas9/monero_research_those_who_control_the_code/).
I am also part of the organising team for [MoneroKon 2022](https://www.reddit.com/r/Monero/comments/tjyrut/ccs_update_monerokon_2022_location_and_venue/), being involved from the start for all the heavy lifting.
Over the years, I have given a number of talks on Monero, funded by the community (thank you!). More info [here](https://www.reddit.com/r/Monero/comments/9yh9zi/cryptofinance_oslo_2018_report_by_midipoet/) and [here](https://www.youtube.com/watch?v=6JIz_H8irAQ)
In 2019, I attended the Oslo Freedom Forum on a ‘reconnaissance’ mission, to give a talk, and also to hold a fringe event. More info [here](https://www.reddit.com/r/Monero/comments/bvoarg/oslo_freedom_forum_fringe_review_midipoet/).
**WHAT**
Now that we are back to in person event, I would like to attend the [2022 Oslo Freedom Forum](https://hrf.org/category/oslo-freedom-forum/) - May 23-25 2022 in Oslo - and more specifically like to attend the [Financial Freedom Track](https://hrf.org/hrf-and-seetee-present-the-financial-freedom-track-at-off-2022/). I think this is extremely important for two predominant reasons.
1. The Monero Policy Working Group (and the Monero community at large) should try and have a representation at these sorts of events to understand what the narrative being pushed is, and HOW it is being pushed. This is especially important when the overarching message is “Bitcoin is good for censorship resistance and the pursuit of liberty and freedom”. We all know that this is an EXTREMELY DANGEROUS message - if not communicated alongside the requirement for privacy, decentralisation, and fungibility - that only Monero ACTUALLY provides.
2. It gives the Monero community a choice to raise a voice - similar to being a raconteur - to stand up to the BTC maxi narratives and to ensure that the “Bitcoin is the answer narrative is met with sound political, technical, and ideological pushback.
**WHY**
In 2019 we were lucky enough to be invited to host a fringe event at the Oslo Freedom Forum. We did not get the same invite this year - but were provided with free tickets to attend and a warm invite from Alex Gladstein (the Chief Strategy Officer).
I have recently given a podcast talk, on the Exit Strategy podcast, in response to Gladstein’s maxi narrative. You can listen to this [here](https://exitstrategypod.libsyn.com/015-robin-renwick-revisiting-bitcoin-human-rights-and-the-oslo-freedom-forum) and the original Gladstein talk [here](https://exitstrategypod.libsyn.com/005-alex-gladstein-bitcoin-and-human-rights).
I am happy to donate my time to going, attend the event, and to provide a report to the community on the narrative, discussions and overarching message/propoganda that is being pushed.
I also think it is a good opportunity to hand out info/flyers at the event, and I will work to ensure I attend with a number of flyers/info sheets in pursuit of this.
Exit Strategy podcast has also agreed to interview me after the event to provide an update. I plan to use that opportunity to discuss the inherent dangers of promoting the BTC narrative in discussions in human rights, censorship resistance, etc. I would also use that opportunity to call out the ill-informed narratives that are pushed both at the event, and in the wider BTC community. It is time now to start taking the message seriously.
**MILESTONES**
I propose half of the XMR being paid out to allow me to pay for flights and hotels. I have priced hotel at ~ €200 per night (same hotel I stayed at in 2019), and flights at ~€300 (sub-total of €1100)
I propose a stipend for food of €50 per day for four days (sub-total €200).
I also propose writing a report and partaking in an Exit Strategy podcast. My time for this would be approximately 6 hours at €50 p/h (sub-total €300).
I also include printing costs for 200 flyer/info sheets (€100), similar to the ones we did for Oslo Freedom Forum 2019.
In total this is €1700.
At the current market rate of ~€200, this is 8.5 XMR.
**EXPIRATION DATE**
As I would like to get the accommodation and flight booked asap, I propose an expiration of 1st May on the CCS, and an expiration of the whole CCS of 1st July. Though this would also depend on the interview with Exit Strategy podcast.
**AMOUNT**
8.5 XMR.
---
layout: cp
title: Compilation time reduction and housekeeping
author: mj
date: April 15, 2020
amount: 52.9
milestones:
- name: ccache for CMake (demo)
funds: 0 XMR
done: 31 December 2020
status: finished
- name: Dynamic linkage
funds: 2% (0.9 XMR)
done: 31 December 2020
status: finished
- name: Automated reports of ClangBuildAnalyser and iwyy
funds: 4% (2 XMR)
done: 31 December 2020
status: finished
- name: Automated reports of Valgrind (test bottlenecks)
funds: 2% (1 XMR)
done: 20 May 2021
status: finished
- name: Optional precompiled headers for CMake 3.16
funds: 4% (2 XMR)
done: 20 May 2021
status: unfinished
- name: Forward declarations of own classes + interfaces
funds: 15% (8 XMR)
done: moot
status: unfinished
- name: One class per header
funds: 4% (2 XMR)
done: moot
status: unfinished
- name: Parallel tests (ctest -jN)
funds: 9% (5 XMR)
done: 20 May 2021
status: finished
- name: Static methods of the wallet2
funds: 8% (4 XMR)
done: moot
status: unfinished
- name: Proper ordering of headers (general last)
funds: 6% (3 XMR)
done: moot
status: unfinished
- name: Miscellaneous hourly work @ $40/hr (23.4 XMR remaining)
funds: 47% (25 XMR)
done: moot
status: unfinished
- name: All remaining -> General fund
funds: All remaining (40.4 XMR)
done: 26 February 2022
status: finished
payouts:
- date: 4 January 2021
amount: 2.9
- date: 17 June 2021
amount: 9.6
- date: 26 February 2022
amount: 40.4
---
# Update
This proposal has been marked completed and the remaining funds forwarded to the Monero General Fund at the request of the proposer, after seeking community input. The 12.5 XMR was paid out to mj, leaving 40.4 XMR.
# What
The proposal is about minimizing the compilation time of the project.
# Who
I have 12 years of object oriented programming experience, mostly in C++. I'm a passionate programmer, not only somebody who does this for money. I hold a M.Sc. degree in Computer Science.
Being able to see the code in a hierarchical order, both projects allowed me to create an extensive library, ready to be reused in a project like Monero, with serialization being my first low hanging fruit.
My contributions to Monero so far are the following:
- I was able to bring ccache to the project. The amount of code committed is not large, but the effect size is. The Travis CI compilation time went from 22 minutes down to [2 minutes for each build](https://github.com/monero-project/monero/pull/6452#issuecomment-615024910).
- afterwards, selsta picked it up and [brought ccache to the CI "workflows"](https://github.com/monero-project/monero/pull/6495), achieving similar results.
- upon a request by vtnerd, [I made the ccache optional](https://github.com/monero-project/monero/pull/6501).
# Why
During all these years I have noticed how important it is to have a quickly compilable code base, which would otherwise put a negative psychological pressure on developers, making them refrain from changing anything for the better, not to mention the obvious reduction of required computational resources.
For Monero specifically, I have set up the following experiment:
I have calculated the sizes of header files, summing up the sub headers included by each of them (column 3). Then I have calculated how many times a given header is included by .cpp files (column 4), thus indicating both the approximate compilation time of the header and how many .cpp files would be affected by the change if the header (column 2) and sorted ascending by this value. Below is the list of the greatest 90% of the headers, using this convention:
```
11% = 10495 = 2099 * 5: cryptonote_boost_serialization.h
12% = 11907 = 1323 * 9: wallet2_api.h
13% = 12393 = 4131 * 3: cryptonote_core.h
13% = 12924 = 718 * 18: crypto.h
16% = 14856 = 4952 * 3: core_rpc_server.h
17% = 15990 = 1599 * 10: rctTypes.h
17% = 16500 = 3300 * 5: blockchain_db.h
26% = 24225 = 8075 * 3: blockchain.h
30% = 27979 = 3997 * 7: core_rpc_server_commands_defs.h
61% = 56616 = 2696 * 21: cryptonote_basic.h
100% = 92620 = 9262 * 10: wallet2.h
```
It becomes obvious, that the wallet2.h is the largest "hot spot" of the whole project. While compilation of the project took 30 minutes, touching the wallet2.h and recompiling took entire 6 minutes = one fifth.
# Milestones
What can be done with this is creating as many wrappers of the boost library as possible and putting as much as implementation code into .cpp files, instead of insisting on writing them inline, when these spots aren't bottlenecks. Putting a trivial method as inline may help, but only when it's called very very frequently, and only if that improvement is a large percentage of other parts of the software, which it usually isn't. Inlining has to be proven by profiling the software, and not being a default policy, since it brings nothing, while costing a lot, not only because multiple recompiles of the code in .cpp files in one session, but recompiles upon changes of the inlined implementation.
I'd like to earn something like 40$/h. It's hard now to assess how much time it will take, so I'm not strict on the concrete values. If I happen to finish ahead of time, thus becoming overpaid, I will admit it. I will be writing the time of work in each of my PRs.
By assessing the payments, I will now assume a price of XMR of 125$.
## Milestone 1: ccache for CMake (demo)
Done with quite a success. The Travis CI was relieved and you, as a developer benefit each time you switch a branch.
Previous text:
"I'd like the CMake script to automatically pick ccache and clcache, when it can find them in the PATH. This piece of software helps in reducing the compilation time of compilation units (.cpp files and all their included headers), when their content hasn't changed. This means, that the more forward declarations and fewer included headers your headers have, the more the ccache will be able to leverage your discipline. This is especially useful when switching between branches."
## Milestone 2: Dynamic linkage
Static libraries tend to grow in sizes exponentially and slow down the generation of the final binaries. I would like to enable (opt-in) dynamic linkage in CMake for development purposes. Also whenever you are done writing a new test and would like to just modify the production code and just execute the test, the test binary can be made so, that it doesn't have to relink upon change of the production code's resulting shared library.
This is quite a low hanging fruit. There are 70 CMakeLists.txt, so multiplying each one by 2 minutes gives 2.33h plus 0.30h for creating some framework for further such changes gives 2.83h, and that equals to 0.9 XMR.
## Milestone 3: Automated reports of ClangBuildAnalyser and iwyy
Some advanced tools can be employed, that help in dynamic assessment of the quality of the code from many perspectives. For my purpose, I could use (ClangBuildAnalyzer)[https://github.com/aras-p/ClangBuildAnalyzer], which gives an objective truth about which parts of the code take longest time to compile. There's also CLang-based (Include What You Use)[https://include-what-you-use.org/] tool, which not only gives advice how to optimize the bottlenecks, but also tries to do it automatically (however it's better to use it just as a hint).
And last but not least, there exist tools, which help finding dangerous constructs in the code, which could lead to segmentation faults at runtime.
I'd like to use my low powered PCs to generate a daily report of the CLang tools and publish them to a dedicated webpage, that I'd manage. I will of course contribute the scripts, that generate the reports into the Monero source tree. Setting up the tools will take some time.
## Milestone 4: Automated reports of Valgrind (test bottlenecks)
Similar as above, however done weekly, since this will take more time. The context is somewhat different here however. Valgrind is able to perform performance tests, able to catch new bottlenecks by executing the tests. I think it would be benefitial, if such reports were available for the public, since their generation costs plenty of time.
This task is somewhat easier, but I'd just like to get compensated for the power costs on this one, so I think that 1 XMR should be fair.
## Milestone 5: Optional precompiled headers for latest cmake
There will surely occur a situation, when a boost header cannot be reasonably wrapped, because it is used in a template code. Such headers are best handled by precompiled headers, reducing the compilation time by up to 50% per precompiled headed. CMake 3.16 is able to generate them natively. Since some users will still be using older versions of CMake, this has to remain optional. I will start with this one before moving the headers away, as this is a low hanging fruit, delivered by CMake devs.
## Milestone 6: Moving boost headers out of own headers 1/3
If the compilation is to be done faster, all of the 3rd party large headers have to be moved outside from our headers, thus preventing them to be propagated into files, that don't need them and waste time on parsing them. This can be done via forward declarations and careful analysis of the dependency tree.
My such header analysis shows, that there are currently 369 occurrences of boost headers. Since each compilation costs 8.5 minutes and each change 2.5 minutes, we are at 11/60 * 369 = 67.65h of active work, excluding time of testing and verifying the speed improvement (passive work). This leaves us with 21.6 XMR for the active work. Let's round it up to 25 because of uncertainty and required passive work, as well as power costs. This forces me to split the task into 3 parts for simplicity. But as before, if I'm done earlier that I calculated, I will admit this and will report the work time for each PR.
## Milestone 7: Moving boost headers out of own headers 2/3
See milestone 6.
## Milestone 8: Moving boost headers out of own headers 3/3
See milestone 6.
## Milestone 9: Forward declarations of own classes + interfaces
It will be of a lot help, if abstractions (interfaces) were used instead of concrete implementations. Then you can easily share just the forward declarations of the unused parts of the interface for the client using the i-face, and include only these parts, which are needed. It can be achieved quite easily by creating and returning a unique pointer to an object of an implementation within a static function of the interface.
There are 358 .cpp files, and definitely more classes than that. If I were to start from the "hottest" 50 classes first, to achieve largest results at the beggining, I'd need 20 hours, assuming 15 minutes of active work on a class and 8.5 minutes of compilation time ((8.5+15)/60 * 50 = 19.58). This would equate to 6.26 XMR. Rounding up for the power costs, let's say 7 XMR.
## Milestone 10: One class per header
It also helps reducing the probability of having to recompile a large chunk of sources, if the classes are declared one per header. Better segmentation also helps ccache reuse its cache, if there's better granularity.
Since this is quite a mechanical work, not needing ANY analysis, I'd say 2 XMR would be enough.
## Milestone 11: Parallel tests (ctest -jN)
Did you know, that ctest allows for running the tests in parallel, just like make does? The problem is, that if they use the same resources during execution, they might (and in our case they do) affect each other. The task here would be to group the tests, which use the same resources and run them sequentially, while running other similar groups in parallel.
I honestly haven't done any analysis on this one yet (other than proving that it doesn't work yet), as there are other things to do, that's why I'll just shoot in the dark here with 5 XMR, or could leave it for somebody else to do.
## Milestone 12: Static methods of the wallet2
I'd like to address here the problems mentioned by Endogenic (highlighted at Konferenco)[https://www.youtube.com/watch?v=AsJaMw-3gGE&feature=youtu.be&t=25614] (thanks, Scott Anecito!), namely making the wallet2 as stateless as possible. I propose here 4 XMR, as this is one of the largest classes in the whole project (if not the largest).
## Milestone 13: Proper ordering of headers (general last)
The order of writing header files is not just a matter of taste. The proper order is local first, and more generic at the bottom, because only this way you could discover hidden dependencies, that you force the client to include manually. This is nicely described (here)[https://blog.knatten.org/2010/07/01/the-order-of-include-directives-matter/] and (here)[https://stackoverflow.com/questions/2762568/c-c-include-header-file-order/2762596#2762596]
With 358 .cpp files, this will take some time and is so mechanical, that I'd gladly leave it to an undegrad, but there were no takers for this yet.
Shall we make it 3 XMR?
# Expiration date
1 Jan, 2025
---
layout: cp
title: mj part time coding (3 months)
author: mj
date: 10 Jan 2021
amount: 64
milestones:
- name: 1st-month
funds: 33% (21 XMR)
done: 13 March 2021
status: finished
- name: 2nd-month
funds: 33% (21 XMR)
done: 14 April 2021
status: finished
- name: 3rd-month
funds: 33% (22 XMR)
done: 17 May 2021
status: finished
payouts:
- date: 15 March 2021
amount: 21
- date: 17 April 2021
amount: 21
- date: 17 May 2021
amount: 22
---
# What
I propose to work for 3 months, spending additional 20 hours a week on Monero Core, on topics such as CI fixes, general firefighting, reviewing, and when there’s nothing left to extinguish, fixing compiler warnings and Clang-Tidy findings.
# Who
Without repeating too much info from [my previous CCS proposal](https://ccs.getmonero.org/proposals/mj-compil-time-reduction.html), I have now 13 years of experience in IT, a master’s degree in Computer Science and specialize in coding in object oriented languages and support-like tasks. This includes using specialized tools to find causes of problems, instead of relying on a gut feeling.
My achievements so far, are [documented in this post](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/138#note_10583).
# Why
After starting my previous work package for Monero, I noticed, that it was hard to follow my fixed plan, because of many tasks, that were arriving in-between. These tasks were mostly CI fixes, that couldn’t have been predicted before. I see, that there’s a strong need for somebody to help fixing them while they arrive. There still exist some prevailing bugs, waiting to be fixed, like the infamous random crash (with about a 65% chance for every build) of the `functional_tests_rpc`.
Another reason for my plan being delayed, is that there seems to be a lack of reviewing power. The team was also super busy doing great job with simulating and fighting off attacks on the network, but because of the lack of man power, [list of my open PRs](https://github.com/issues?q=is%3Apr+is%3Aopen+author%3Amj-xmr) stagnates and I need to spend empty hours on resolving conflicts, while other branches are being merged. I’d like to help in both of those tasks (reviewing and improving security) as much as I can, so that the hands of others are freer.
Thirdly, as a partial, but already usable result of my previous CCS proposal, I started to automatically and regularly generate a report of Monero code base from various perspectives. The report is available for everybody [on this page](http://enjo.hopto.org/pub/monero/).
This helped me discovering, that there’s a lot more work to do on the code base, than my fixed plan assumed. The type of work to do, shown mostly by Clang-Tidy, is a mixture of overreactions (errors of low severity) and serious memory-related bugs, that either sporadically crash the application already or could crash it in the future, when some yet untested parameter combinations are to be used.
# Proposal
Realistically I am able to spend 20 hours a week more on the project. If the Community wishes to "hire" me for the mentioned perpetual tasks (not covered by my first proposal), then I’ll arrange it accordingly with my job. The previous proposal is still in place, but for reasons not related to me, it can’t move at the pace, that I initially intended. I’d like to oil this machine in all possible ways.
I propose a wage of 40 $/h for 3 months. The XMR/USD as of 10.01.2021 is at around 150 $. This would make a total of:
40 ($/h) * 20 (h/week) * 4 (weeks) * 3 (months) / 150 (XMR/USD) = 64 XMR.
Cheers!
---
layout: cp
title: mj part time coding Q3 2021
author: mj
date: 30 June 2021
amount: 45 XMR
milestones:
- name: Month 1
funds: 15 XMR
done: 1 August 2021
status: finished
- name: Month 2
funds: 15 XMR
done: 5 September 2021
status: finished
- name: Month 3
funds: 15 XMR
done: 10 October 2021
status: finished
payouts:
- date: 6 August 2021
amount: 15
- date: 10 September 2021
amount: 15
- date: 11 October 2021
amount: 15
---
# What
In the same way as previously, I propose to work for 3 months, spending additional 20 hours a week on Monero Core, specifically on topics such as:
- CI fixes
- code reviews
- addressing user issues (whenever I can help)
- enabling new developers to submit their patches quicker
- extending my [Monero health report](http://enjo.hopto.org/pub/monero/)
- general firefighting, whatever problems we face in near future
When there’s nothing left to extinguish, I'll be fixing compiler warnings and Clang-Tidy findings. Last time, there was so much other work, that I didn’t really even reach this topic, except for compiler warnings.
# Why
During preparation of my last such quarterly proposal, I noticed quite annoying nondeterministic CI failures, that I was able to fix, thanks to your funding and the Team's cooperation through reviews and integration. Please make your own opinion on how valuable my changes were. Due to the lack of a better measure, I propose comparing the number of pages of failed builds per month before and [after](https://github.com/monero-project/monero/actions?page=3&query=is%3Afailure) merging my change on the 30th March. In short, there are only 3 such pages in recent 2 months after, while the previous 2 months, before merging, marked a many as 7 such pages, until [here](https://github.com/monero-project/monero/actions?page=10&query=is%3Afailure)
The ability of improving this weak point of the development process gave me a lot of hope, that the somewhat disruptive, but positive changes are accepted, therefore the development will not come to a halt at some point. I'd like to continue working on such project and bring other similar improvements.
The details of the already identified work packages are the following:
## CI
- In the CI there's still an unresolved issue of FreeBSD not using ccache, thus taking unnecessary time for recompilations. This was left alone, due to the fact, that it's not a critical matter. However having this solved would be a cherry on top of the Monero's CI. I can't promise that it will be possible to fix and I haven't had time yet to look into it in detail, but I do know how to analyze such errors.
- Recently I noticed, that Unit Tests fail under Mac OSX. It wouldn't hurt to run only the UTs under OSX as one of the CI steps, as they cost only 10 minutes of processing time. Fixing the UTs would also be part of my job here.
- The CI could use a matrix of all the supported Boost library versions. As [discovered here](https://github.com/monero-project/monero/pull/7735), changes of the boost headers need to be handled with caution, in order not to introduce compilation regressions across still unchecked Boost versions. This is what a CI is for.
## Enabling new devs
- The efficient compilation and debugging document, whose value you can measure via [this link](https://github.com/monero-project/monero/blob/master/docs/COMPILING_DEBUGGING_TESTING.md), is where the new developers could read, in order to learn faster how to integrate their patches, avoiding a steep learning curve and waiting times. This document will be continuously extended with setups for various IDEs and other such findings
- I need to continue the automation of adding all the headers to the IDEs' project files. Both the missing ones and those to be added in the future. The framework for this is already prepared. What's left is some monkey business of simply identifying the gaps and using the framework. Nothing hard, but time consuming. Having this level of order in the IDEs leads to a great reduction of confusion for developers while they change header files.
## Health report
- I extended my [Monero health report](http://enjo.hopto.org/pub/monero/) with the lcov report lately (Line coverage of tests), but didn't have the time to really integrate the report generation into Monero itself. I only do it locally. Therefore other devs can't generate such a report for themselves yet. The script would be a perfect fit to the collection of other health-related tools in Monero.
- I have some other handy source analysis tools, that go in the direction of Include What You use, but are not that dependency heavy and deliver less noise. This means, that everybody can run such an evaluation on almost no-time, while the other Clang-based tools take about 1,5 hour each, however complete they are.
- both of the above scripts, although serve their purpose, are not production ready from the code quality perspective, so I myself wouldn't want to merge this into the official repo in their current preliminary state. This needs some focused work now.
## Small issues
Some small things that I've flagged as reminders for now:
- [Adding regression tests](https://github.com/monero-project/monero/issues/7756)
- [Addressing previous PR comments for documentation](https://github.com/monero-project/monero/issues/7755)
# Previous reports
I'm sure you've either already read them or simply found them too long anyway, so I'll just link here 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)
# Proposal
I am able to realistically spend 20 hours a week more on Monero, additionally to my compilation time reduction efforts, which move at a slow pace. I will start not sooner than from the middle of June, due to current personal workload.
I propose a wage of 40 $/h for 3 months. As of 30.06.2021 (1 day before Q3) the XMR/USD is at around 217 $. This would make a total of:
40 $/h * 20 h/week * 4 weeks * 3 months / 217 XMR/USD ~ 45 XMR. (3 times 15 XMR)
Cheers!
# Expiration date
15 Sep, 2021
---
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: cp
title: "Proposal to Add Monero (XMR) as a Payment Option on the Tesla Website"
author: Natoshi Sakamoto
date: February 9, 2021
amount: 890
milestones:
- name: Payment for Monero public payment integration promise
funds: 890
done:
status: unfinished
payouts:
- date: 9 March 2021
amount: 890 (refund)
---
*Important donor and participant note: See the bottom of the document. This proposal is contingent on several factors and will be refunded if certain criteria are not met.*
Press contact: press@getmonero.org
# Proposal to Add Monero (XMR) as a Payment Option on the Tesla Website
**What:** Tesla recently announced that they may accept Bitcoin payment for Tesla cars at some point in the future. This proposal is to ***add Monero as a payment option for a new Tesla, along-side Bitcoin, by asking Elon Musk to accept payment in Monero for three new Tesla Model 3 vehicles (maximum expenditure by the Monero community of $50,000 USD equivalent per Tesla, $150,000 USD equivalent total).*** If he agrees, we purchase the vehicles using Monero through the front end of the Tesla website or Tesla store point of sale system, or Tesla accepts our Monero in some other way such as a special payment processing run. Vehicles will then be donated to our favorite Charities!
**Why:** Most existing cryptocurrencies, including Bitcoin and Ethereum, have transparent blockchains, meaning that transactions are openly traceable by anyone in the world and subject to mass surveillance by foreign governments and marketing agencies. Every Monero transaction preserves the privacy of its user because it obfuscates sending and receiving addresses as well as transacted amounts. Monero is unique among any major cryptocurrency in providing these basic levels of user protections.
Monero is a truly decentralized project entirely developed by a grassroot community of volunteers - to date, [more than 650 individuals have contributed to its source code](https://www.openhub.net/p/monero). All contributors spend time and efforts altruistically, largely unpaid except for a few specific tasks supported by a [dedicated crowdfunding platform](https://ccs.getmonero.org/). Similar to Bitcoin (and unlike most projects in the cryptospace...), there is no premine, no dev tax, no ICO, no venture capital, no nothing. Monero is a pure open source project whose community is aligned first and foremost toward its ideals of privacy & freedom.
With the recent announcement that Bitcoin may be accepted for Tesla purchases, members of the Monero community came up with the idea that it would be preferable to have Monero along-side Bitcoin as a payment option when purchasing a Tesla, given its privacy preserving properties. While some people rightfully want to brag about their brand new Tesla, this should be the owner’s choice, not revealed with an accidental purchase of coffee using the same Bitcoin wallet. You wouldn’t want your server at a restaurant to know the entire balance in your wallet when you pay would you? Why should your purchase of a car broadcast to the world all of the information that is leaked in a Bitcoin transaction? Plus, **the effect of showing up to a party in a brand new Tesla is diminished somewhat if all your friends already knew the moment you bought it because they were able to see the transaction on the Bitcoin blockchain!**
**Who:** This proposal encourages the Monero community to come together and to raise the funds needed, in Monero, to purchase three Tesla Model 3 vehicles and donate them to three worthy 501(c)(3) charities (or corresponding status for non-profits outside the US)! To be considered one of the Community favorite charities, the words “Monero” and the hashtag #Tesla4XMR should be in all Tweets.
**When:** Lets raise these funds now and provide an opportunity for Tesla to support freedom and privacy while simultaneously providing benefit to our favorite charitable causes!
**How:** We propose to ask Elon Musk to accept Monero as a payment option for three new Tesla Model 3 vehicles through Twitter. We are relying on the power of the Monero community (and the generosity of Elon and others - including wonderful charities) to make this happen. Please help us share this proposal and encourage Elon to promote essential cryptocurrency technology!
501(c)(3) charities (or corresponding status for non-profits outside the US) who are interested should express via social media (ideally Twitter) how the donation of a Tesla Model 3 will benefit them, as well as some message on the importance of privacy. Then, charities should encourage engagement on their end to raise awareness. The hashtag **#Telsa4XMR** and the word “Monero” should be used on all Tweets or social media mentions!
In order to be considered one of our FAVORITE charities, a charity should:
* Tweet about what privacy means to them, and why it is important!
* Tweet about situations in which lack of privacy would be a bad thing! Be creative!
* Tweet about how YOU enjoy privacy in your own life (ie: curtains on the window are closed at night, cellphone has a password on it, cash is kept in your wallet or purse and not carried around in your hand for all to see).
* Tweet other funny or serious hypotheticals related to privacy, or lack of privacy - we can’t stress this enough - get creative!
* Tweet about how receiving a donated Tesla Model 3 would benefit the charity.
* Tweet about how a Tesla Model 3 would be used by the charity.
*All Tweets should include the word “Monero” AND the hashtag #Tesla4XMR.*
The more Tweets and Retweets, the better, we need to get Elon’s attention to make this dream a reality! The Monero Community loves organizations who have an awareness of the importance of financial privacy, personal privacy, privacy of thought, freedom of speech, and freedom of expression.
We will be looking for charity engagement in this initiative, and to get Elon’s attention for twenty one days beginning 12:00 noon US Central time on the day the proposal is funded. That is, after 21 days from this time has elapsed, and if the success criteria below have been met, the Monero Community will select our three favorite charities to receive Teslas. The venue in which the three favorite charities will be evaluated and selected is TBA.
Note that selected charities will not receive a donated Tesla Model 3 if the success criteria below are not met. The goal is to actually pay Tesla, for Teslas, using Monero! For that, we need to get Tesla to accept Monero as a payment option!
**Define Success:**
The decision to pay out the Monero to Tesla for the three Tesla Model 3 vehicles will depend on two things occuring. A) Acknowledgement from Elon within twenty one days of a fully funded proposal, that Monero will be added or accepted for the purchase of three Model 3 vehicles, and B) The actual acceptance of the Monero for the vehicle purchases within six months of the date of a fully funded proposal.
More specifically, pay out of the funds to Tesla will occur if three of our favorite charities have been selected to receive a Tesla AND:
* Elon agrees via tweet or other public medium within twenty one days of a funded proposal to add Monero as a payment option, and it is possible to make the payment to Tesla in Monero within six months of the date of the fully funded proposal.
* Elon agrees via tweet or other public medium to accept our Monero as payment for three Teslas and it is possible to make the payment to Tesla, with Monero, within six months of the date of the fully funded proposal.
* Monero appears as a payment option on the Tesla website with no immediate announcement or correspondence from Elon, and this is accompanied by public correspondence from Elon within twenty one days of a fully funded proposal, acknowledging Monero has been added as a payment option, and it is possible to make the payment to Tesla in Monero within six months of the date of the fully funded proposal.
Funds will not be paid out to Tesla (and instead, refunded) if:
* There is no response or engagement from Elon within the twenty one days of a fully funded proposal.
* There is a response or engagement from Elon, but no commitment to accept Monero for payment within twenty one days of a fully funded proposal.
* Monero appears as a payment option within twenty one days of a fully funded proposal on the Tesla website with no announcement or correspondence from Elon (this would be indicative of Tesla already having planned to add Monero as a payment option).
* Monero is added as a payment option within twenty one days of a fully funded proposal alongside other coins or tokens or cryptocurrency (excluding Bitcoin), even if acknowledged by Elon. For example: Tesla adds Coin X, Coin, G, Coin, H, and Monero.
* There is no response or engagement from Elon within the twenty one days of a fully funded proposal and Monero is added as a payment option only by way of a batch implementation of more than just Monero and Bitcoin through the use of a Tesla vendor / payment processor, such as BitPay, etc.
* It is not possible to send Monero to Tesla, and/or Tesla has been uncooperative in receiving the funds as payment for three Model 3 vehicles within six months of the date of a fully funded proposal, despite any acknowledgement or indication from Elon that it will be possible to make this transaction.
Acceptable payment methods for the three Tesla Model 3 vehicles are: Tesla agrees to make a special payment processing run for the Community’s Monero, or Monero is spendable on the Tesla website, or at the Tesla store through the point of sale system. If, in the event of success (as defined above), six months has passed since the date of a fully funded proposal and it is not possible (Tesla becomes unresponsive, uncooperative, or it is not technically possible to send Monero to Tesla by no fault of the Monero community) to spend Monero on the three Tesla Model 3 vehicles in the above mentioned manner, refunds will be issued in accordance with the notes at the bottom of this page.
**Monero Price Fluctuations:**
Should the Monero price in USD rise between the time of a funded proposal, and actual pay out of the funds, the excess Monero that is not used to purchase the three Model 3 vehicles will be returned proportionally to the donors, in accordance with the notes at the bottom of this page.
Should the Monero price in USD fall between the time of a funded proposal, and actual pay out of the funds, so that the Monero collected is now insufficient to purchase the three Tesla Model 3 vehicles, further funding will be sought from the community in a follow up CCS proposal.
**Notes:**
A charity will certainly not be considered a friend of the Monero community if there is evidence that the nonprofit has a mission that is demonstrably not in line with our principles (e.g. advocating for government intrusions such as warrantless surveillance, tracing, suspected human rights violations, etc.). Charities that can be shown to have utilized Twitter bot farms or other forms of unfair manipulation to artificially increase their re-tweet counts will also be disqualified as a potential favorite of the Monero Community.
*This is not a sweepstakes or lottery. There is no purchase, payment, or consideration required to be provided by charities for participation. Charities and others who participate do assert that their participation represents non-consideration in the form of materials, opportunity cost, time, or person-hours, and that any efforts put forth to try and be selected to receive a Tesla are trivial and non-material. Participation by charities, Elon Musk, Tesla, Monero Community Members, or anyone else is purely voluntary. This initiative is void where prohibited, and entities residing in or governed by such jurisdictions shall not participate. This text and/or initiative creates no liability for any participant, including Monero Community members. The recipient(s) of any donated Tesla Model 3 must ensure they are able to fulfill any taxation obligation that accepting an award may present. The Monero Community is not liable for taxation liability, if any, associated with these donated vehicles.*
```
Important donor notes: For this proposal, refunds will be issued in the event that the funding is not satisfactory or the metric(s) for success are not achieved. This differs from the standard of excess or unused funds going to the general fund, because success in this case is dependent on an external event or events occurring.
To qualify for a refund, the donor must send their tx ID, amount, and return XMR address to luigi1111@getmonero.org (PGP fingerprint: FE6D D72A 19CD C5FC 6CB9 1696 BA18 1389 4EDD 58B9, full PGP key at github.com/monero-project/monero/blob/master/utils/gpg_keys/luigi1111.asc) NO LATER than ONE WEEK after their donation is made. Any remaining unclaimed funds (in the event that the proposal is not completed) will be sent to the general fund as usual. If refunds are to be issued, the funds will be returned via the provided XMR address.
In summary, the funds can be either:
Unclaimed, leading to the general fund receiving them in the case of a failed proposal.
Claimed within one week of the donation, leading to a refund in the case of a failed proposal (assuming you sent the email within the week window).
Note: The hope is that the refunds will not be needed, and the funds will be distributed in accordance with the success of the proposal. In the event of success of the proposal, refunds will NOT be issued. It is only if the proposal is not funded to satisfaction, or not successful, or as a volatility adjustment.
```
Tesla and Elon Musk have absolutely no affiliation with this Monero CCS proposal at the time this is written, nor can we say that they endorse or otherwise have commented on this CCS proposal or Monero.
---
layout: wip
title: Audit monero-serai and monero-wallet
author: kayabaNerve
date: October 11, 2024
amount: 1050 XMR
milestones:
- name: Audit of monero-[serai, wallet], including the FROST-inspired multisig protocol
funds: 1050 XMR
done:
status: unfinished
payouts:
- date: 3 December 2024
amount: 1050
---
monero-serai and monero-wallet are public-good libraries built by myself as part of my work on Serai DEX. Despite the "-serai" name, both libraries have always been intended to be usable and actually used by the Monero community as a whole. Development has been ongoing for over two years. During that time, I have hired developers to work on and review it (including j-berman who truly needs credit and acknowledgement for their contributions), yet have never seeked community funding for my work. Now that monero-serai and monero-wallet are ready for their 1.0 release, meaning they have reached the necessary milestone to be considered sufficiently developed and meaningful, I have decided to request the community's support for their audits.
monero-serai is a from-scratch reimplementation of the Monero transaction protocol in Rust. It originally also
included wallet functionality yet that was split out into the monero-wallet library to offer greater
flexibility to consumers.
monero-serai is used by Cuprate[[1]](
https://github.com/Cuprate/cuprate
)[[2]](
https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/405
)[[3]](
https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/422
)[[4]](
https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/431
)[[5]](
https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/456
)[[6]](
https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/469
)[[7]](
https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/484
) for its parsing/handling/stateless verification of Monero transactions. Specifically, included is:
- An implementation of v1 and v2 transactions
- Cryptonote ring signature, MLSAG, and CLSAG verification
- Borromean, Bulletproofs, and Bulletproofs(+) verification
monero-serai also underpins monero-wallet, a Rust library for sending and receiving Monero. It's intended to have a clean, high-level API, be usable in a variety of contexts (from desktops to embedded devices to web browsers), and support everything from traditional wallets to more novel use cases (such as atomic swaps). As part of this, it offers:
- Proving CLSAG, Bulletproofs, and Bulletproofs(+)
- Honest-sender outgoing view keys (deterministically derived transaction keys to simplify payment proofs and allow verifying transactions match an intent)
- A FROST-inspired multisig which has O(1) per-signer upload complexity and O(n) computational complexity, compared to Monero's multisig which has O(n!) complexity (where n is the amount of signers)
Potentially of most note is the work on multisig. FROST is a widely regarded, [IRTF standardized](https://datatracker.ietf.org/doc/rfc9591/) multisignature protocol for Schnorr signatures which I've applied to Monero's CLSAG (caveats apply). The application to CLSAG is built upon [modular-frost](https://github.com/serai-dex/serai/tree/develop/crypto/frost), a FROST implementation I wrote for Serai and have already [prior audited](https://github.com/serai-dex/serai/tree/develop/audits/Cypher%20Stack%20crypto%20March%202023).
Monero has historically had issues with its multisig which has a novel high-complexity DKG and a signing protocol which isn't formalized (though is currently Musig2-inspired). monero-wallet represents an opportunity to step forth with a formalized, proven, and audited multisignature implementation. One idea occassionally brought up has been to remove multisig from Monero proper, placing it in its own distinct repository, in order to not have multisig burden Monero. With the work done on monero-wallet, and the audit being funded here, completely deferring multisig to it would become a viable option.
monero-wallet has also been checked to have a matching decoy selection algorithm (specifically, a matching distribution of selected decoys), fee algorithm, and various other properties (such as TX extra) to ensure its transactions won't be fingerprintable.
There is interest by multiple wallets to use monero-wallet, and it's already being developed on top of by Serai, a user-facing multisignature use case, and an application premised on web technology (which compiles monero-wallet to WASM).
This CCS is to fund the formalization of the implemented CLSAG multisig protocol (already outlined), provide the necessary security proofs (derived from FROST), and audit monero-[serai, wallet]. The audit will be done by Cypher Stack (their quoted amount being the amount requested). The one milestone is to be paid directly, immediately, and in full, to Cypher Stack for their work.
After the audit, the plan is to transfer monero-serai into the newly created [monero-oxide](https://github.com/monero-oxide/monero-oxide) organization (head by myself and boog900 from Cuprate). This is to help ensure it stands as a public good and doesn't solely service a single project's needs. Additional discussions are ongoing regarding the future governance of monero-wallet.
---
layout: fr
layout: cp
title: A Monero Tip Bot for Telegram
author: HAH! Sun (omani)
date: July 10, 2019
......@@ -7,29 +7,29 @@ amount: 13
milestones:
- name: Collect Feature Requests and Prototype the Telegram bot
funds: 1
done:
status: unfinished
done: 1 October 2019
status: finished
- name: Implement Features
funds: 5
done:
status: unfinished
done: 1 October 2019
status: finished
- name: Intensive Testing of Bot on Stagenet Within Monero Telegram Groups / Bug Fixing
funds: 4
done:
status: unfinished
done: 1 October 2019
status: finished
- name: Delivering Bot to Monero Project Team
funds: 0
done:
status: unfinished
done: 17 October 2019
status: finished
- name: Maintenance and Support
funds: 3
done:
status: unfinished
done: 17 October 2019
status: finished
payouts:
- date:
amount:
- date:
amount:
- date: 1 October 2019
amount: 10
- date: 18 October 2019
amount: 3
---
# Monero Tipping Bot
......
---
layout: cp
title: Help an independent film featuring Monero get to the Oscars™!
author: markofdistinction_
date: January 20, 2023
amount: 154
milestones:
- name: upon approval
funds: 77
done: 25 September 2023
status: finished
- name: upon qualifying for Academy Award
funds: 77
done: 25 September 2023
status: finished
payouts:
- date: 5 November 2023
amount: 154
---
### Note: This proposal generated significant and thoughtful discussion; potential donors are invited to read it [here](https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/371).
![HorizontalPoster](https://raw.githubusercontent.com/markofdistinction/ccs/main/MarkOfDistinction_16x9_1280x720.jpg)
# Help an independent film featuring Monero get to the Oscars™!
### Who are you?
Hey all, my name is George Nicholas, an “award-winning” filmmaker and Monero enthusiast. You can see my IMDb profile here: https://www.imdb.com/name/nm11077440/
I was involved with making "Monero Means Money".
### What’s up?
I’ve written and directed an independent, 38-minute live-action film titled MARK OF DISTINCTION. The film is in Spanish and English and was shot in Tijuana, Mexico in July of ‘22 on 16mm Kodak film. It features Monero, but is not focused on it -- it is inspired by real events and tells the story of a 16-year-old boy who gets recruited by the Mexican cartel to smuggle liquid meth across the border. The boy dies tragically at the hands of U.S. Customs and Border Protection, who ask him to drink the liquid to prove that it’s not drugs.
You can see a report and footage of the incident here:
https://www.youtube.com/watch?v=7KsKtVnrRaM
And some behind-the-scenes photos from our shoot [here](https://twitter.com/markofdistinctn/status/1554237266460954625?s=20) and [here](https://twitter.com/markofdistinctn/status/1554237518098313217?s=20).
Government coercion over the individual is the reason I came to Monero and it is the reason I was driven to tell this story.
### How is this related to Monero?
Monero is featured in 3 scenes. As background, the protagonist, MANUEL, has found a physical Monero coin that his father had stashed away for him before his disappearance--
### Did you just say a physical Monero coin? gtfo
Yeah, a physical Monero coin, like this one: https://bitcointalk.org/index.php?topic=1502918.0
### OK, so what happens next?
So, Manuel is carrying the coin around in his pocket like an idiot, not realizing what he has. His friend, RODOLFO, sees him trying to shove it down a slot machine, but thankfully the coin is too big to fit. Rodolfo explains to him what he has and Manuel’s eyes light up. Outside the bar, the two get beat up because of an earlier incident and the hooligans make off with Manuel’s scooter and his coin. Manuel gets his revenge and recovers the scooter, but not the coin. Rodolfo later finds the coin and tries to give it back to Manuel, but it is too late…
Monero represents the boy’s potential – the unrealized wealth that every individual carries within, although not everyone finds the key to unlock it. The coin ends up with the person who understands its value, as often happens in real life.
### How can we help?
I self-funded the shoot and post-production (the budget was in the low six figures), which exhausted my personal savings. We need funds for the most crucial phase – the release of the film. This includes getting it in front of festivals and promoting it there, hiring a publicist, running an awards campaign. All this costs money and I am coming to the Monero community for help.
### What do we get in return?
##### 1. Exposure (the good kind)
The film has the chance of reaching hundreds of thousands and even millions of people. Not every viewer will become a Monero user, but they will all be exposed to Monero in a positive way. The community will also receive an acknowledgement in the credits, to the effect of "this movie was kindly supported by the Monero community" with the Monero logo and getmonero.org underneath.
Monero already gets exposure in the media and [even some TV shows](https://twitter.com/vikrantnyc/status/1616152774856540166?s=20), but almost always as a Ransomcoin. This is a story that shows Monero being used in the way most of us use it -- as a savings vehicle that we can spend or pass down to our loved ones outside of anyone else's control. Monero means money, but it also represents so much more -- a path towards personal freedom, away from coercion by the state or others. This is what the film tries to get across and hopefully it succeeds.
##### 2. Physical presence
With the community's help and the right release strategy, the film will play at major festivals across the world. Anytime the film plays, this will be an opportunity for an impromptu Monero meetup. Screenings can be publicized in the community beforehand to attract local Monero fans throughout the world.
##### 3. A cause to rally behind
I know we take the whole magic internet money thing seriously around here, which is why I love Monero. It is the reason no other coin was considered to take its place in the film. And I respect the more conservative view that the CCS should only be used to fund developer work. The number of undelivered, CCS-funded projects is dishearteninig, which is why I held off on asking for help until the film was actually made and ready to go.
Monero has the best p2p cash characteristics of any coin, but we could do a better job of celebrating that. This film will give us an opportunity to rally behind a cause that almost all of us agree with -- the right of the individual to remain free from oppression, especially from governments. We can go to festivals together or follow from home, celebrate the wins and mourn the losses. Consider it an exercise in community-building.
##### 4. Some cool GIFs, of course.
But you'll get them regardless, since the film is already made.
![CoinGIF](https://raw.githubusercontent.com/markofdistinction/ccs/main/coin_squeeze.gif)
Also, the idea to have a private screening for the community at MoneroKon was floated, which I'd be open to doing if there is interest.
### Alright, how much do you want? Spit it out.
###### We are looking to raise 154 XMR (the equivalent of $25K at Kraken’s current 20-day EMA)
### What's your Oscars strategy? (i.e. How are you going to spend it?)
Films under 40 minutes are considered live action short films by the Academy of Motion Picture Arts and Sciences. This is the category we're aiming for. There are two ways for a film to qualify:
1. The film must win an award at one of the ~130 Academy Award-qualifying festivals throughout the world:
https://www.oscars.org/sites/oscars/files/95aa_anim_short_festivals.pdf
Submission fees to these festivals are generally in the $50-$100 range, so that alone can eat up $10K.
2. The film must be publicly exhibited for paid admission in a movie theater in Los Angeles or New York City for
one week: https://www.oscars.org/sites/oscars/files/93aa_short_films.pdf
This is the cheaper option at about $3K, but films that qualify with a festival win are preferred by Academy voters, so we'll try the festival route first.
Once the film qualifies, the remaining funds will go towards hiring a publicist and running an awards campaign. Jim Dobson at Indie-PR has seen the film and loves it.
He ran the Oscars campaign for AUDIBLE, a short documentary that received a nomination in 2022. https://www.indie-pr.com/about
Another PR firm with extensive experience that has expressed interest is JJPR: http://joshuajasonpr.com/film-campaigns
I make no guarantees that we will win an Oscar or be nominated, but every industry professional who has seen the film thinks we have a good chance (and not just the publicists who stand to make money). We are taking this journey and I'd like the community to come along!
### Who else has seen the film?
I've reached out to some people I know in the community, who have kindly taken the time to see it. Here's what they had to say:
##### jberman said:
"This has the feel of something that would win a lot of awards."
"Was the idea of the friend chasing him to give the coin to him basically saying Monero represented an
alternative path to a better life/better system instead of the darker one he chose? That's how I read its place
in the story."
##### midipoet said:
"you don't need me to tell you, but for what it's worth, the production value is extremely high"
"it's pretty much feature length quality, as you were aiming for. what struck me most though was the quality
of the acting."
##### Vik Sharma said:
"Really, really well made."
##### Doug from MoneroTalk said:
"Captivating! Sunita and I loved it."
##### Johnny Mnemonic said:
"Awesome film! The Monero coin inclusion was great…
Touching story… I really feel for the kid at the end because he’s just trying to make things right with his grandfather.
I also liked that you included real footage at the end… really makes you feel how real it is. "
##### dsc said:
"that last scene had me on the edge of my seat!"
### What happens if Monero's price fluctuates in the meantime?
The amount we're raising is denominated in XMR. Any fluctuations in fiat value are at our own risk/benefit.
### When do you expect to be paid?
50% upon approval, 50% upon qualifying for the Academy Awards, as described above.
### Is the film on any social media?
https://twitter.com/markofdistinctn
https://instagram.com/markofdistinctionfilm
https://fb.com/markofdistinctionfilm
### Can I see it before I donate?
Yes, please send 1 piconero (0.000000000001 XMR) to the donation address as a captcha and email markofdistinction@proton.me with the txid and tx key and you'll receive a link back.
### OK, take my money! ;-)
---
layout: cp
title: "monerobull for website workgroup"
author: monerobull
date: 5 July 2024
amount: 30
milestones:
- name: 2 meetings + hours worked
funds: 10 XMR
done: 1 January 2025
status: finished
- name: 2 meetings + hours worked
funds: 10 XMR
done: 1 January 2025
status: finished
- name: 2 meetings + hours worked
funds: 10 XMR
done: 1 January 2025
status: finished
payouts:
- date: 30 January 2025
amount: 30
---
# Who, what, when, where?
Hi, I'm monerobull. I run monero.town & monerosupplies.com. I also never did any paid work for Monero before.
I was recently mentioned in a CCS proposal by geonic, famous Monero movie director. There's a lot of opportunity for improvement in the non-dev areas of the project, and not always enough hands to get it done. It was agreed upon that, were this to happen, this would be done through my own CCS proposal rather than through geonics. This moves me from being accountable to nobody, to accountable to the community.
A quick summary of what I'd be working on:
- Setting up / managing a Monero Website Workgroup, keep it up to date (our roadmap still mentions triptych)
- Joining the moderator teams for Matrix and helping along with discord
- Being a supportive figure in the Monero Community workgroup and helping that along as needed
- Keeping a finger on the "pulse of the community" in the various chat rooms and platforms (Telegram, Discord, not IRC, Matrix, Reddit, etc.)
- Aiding and assisting in event work as needed (part of Monerokon team since MK3)
# Why?
There's lots of non-dev stuff to do, and not so many people to do it. I am mostly capable and willing.
# How long? How much?
30 XMR for three months for half time work. Possibility of renewal depending on community sentiment.
# Deliverables
I will do all of the above in the beginning section, and give a monthly report to the community on what's been done, and tasks accomplished. Luigi does a lot of work, I'd like to take on some of that.
# COI
I would have never made this proposal without geonics preceding yolo proposal. In the past I've tried to stay away from the CCS due to all the drama surrounding it. This very proposal was born out of CCS drama.
---
layout: cp
title: Monero FM (community run radio project)
author: ajs
date: September 7, 2020
amount: 35
milestones:
- name: Payout for license acquisition, initial expenses
funds: 17.569028
done: 7 August 2021
status: finished
- name: Payout excess to genfund
funds: 17.430972
done: 12 February 2022
status: finished
payouts:
- date: 8 August
amount: 17.569028
- date: 12 February 2022
amount: 17.430972
---
# Monero.FM, the Monero community run radio station.
Ok, let's make this short and sweet. We want to start an online radio station for Monero, controlled, in part, by the Monero community.
## Why?
- It'll be super fun; a new way for the community to connect.
- We can see about monetizing the radio station with some ads or paid subscription (for higher bitrates) to make it self sustaining (after the initial CCS) and help the CCS and general fund.
- Low sunk costs! We can try it out for a while (the licenses are for a year) and if it's not popular then we don't have to renew.
- It can be used as a platform to get high quality information out to our listeners, both about upcoming updates (remember to update GUI), new CCS's to fund, and even teaching opportunities for newbies if it grows large enough.
- It's not as expensive as you might think to do all of this completely legally and above board. Don't believe us? Check it out below!
## Initial Estimated Costs
- Monero.FM Domain ($75-$100 Annual)
- SoundExchange Umbrella License ($500 Annual)
- ASCAP Performance License ($266-$1499[1])
- Server Hosting Fees ($250 Annual)
- Overages/Slush ($250)
- Music Aquisition Costs[2] (avg ~$1.33/track, 1000 tracks to start = $1300)
Asked from community initially via CCS: 100+500+266+250+250+1300 = $2667
At $82/XMR that is 32.5 XMR, with a 10% buffer that comes to 35 XMR.
Half of the funds will be released up front to secure the licenses. Only after the licenses are secured will the second half be released to cover music acquisition costs.
[1] Exceeding the $266 tier would require either >369,000 concurrent listeners, or >$24,600 in annual revenue. The former case is unlikely, and the latter would imply that the radio is already self sustaining.
[2] This is the most open-ended part of the proposal, and we will need to find some way to sustain the media library without the assistance of the CCS. Some ideas for future funding are users 'donating' licenses (by paying to have their favorite songs added to the library), running radio ads for vetted entities in the cryptocurrency ecosystem, premium subscriptions (for a higher bitrate/quality stream), selling subdomained stations to other projects (with access to our purchased media library) or something else.
## Management
- DJs can be picked from the community depending on interest and experience to handle time slots. It can be completely community run.
- There are several options for how to run it on the software side of things, all of them are FOSS. Some ideas are using something like AzuraCast (https://github.com/AzuraCast/AzuraCast)
- During non-DJed hours, a private IRC channel will allow vetted community members to collaboratively queue tracks, and a public IRC channel will allow unvetted community members to vote on them[1]. In the absense of DJ queueing, the library will run on a vote-weighted shuffle. This will be done via an IRC bot that is in development by needmoney90.
[1] For legal reasons having to do with licensing, the queueing room cannot be entirely public access.
## Specifics
- Cypher Stack (Diego's small design firm) will be the business that holds the license (as someonebody needs to do that). Cypher Stack will be disbursing 34% of the profits (beyond what is needed for self-sustenance) to the general fund.
- Part of what is considered self-sustenance is a paid position for continuous oversight, marketing, and general maintenance of the radio utility. needmoney90 has been chosen for this position. The salary will never be asked from the CCS givers, only from made profits.
## Profit disbursment
Once annual estimated costs are achieved for the year (totaling $2666 as denoted above), Monero.FM will go into "profit mode" which will see a splitting of the profits as follows.
- 34% will go to the general fund.
- 33% will go to the salaried position designated in the Specifics section.
- 33% will go to continued music acquisition.
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.
---
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 coding, july 2019
author: moneromooo
date: 01 June 2019
amount: 294
milestones:
- name: july
- name: july/august
funds: 33% (98 XMR)
done:
status: unfinished
- name: august
funds: 33% (98 XMR)
done:
status: unfinished
done: 31 August 2019
status: finished
- name: september
funds: 33% (98 XMR)
done:
status: unfinished
done: 30 September 2019
status: finished
- name: october
funds: 33% (98 XMR)
done: 31 October 2019
status: finished
payouts:
- date:
amount:
- date:
amount:
- date:
amount:
- date: 1 October 2019
amount: 294
---
**[note: milestones have been updated to reflect some vacation time]**
Hi all,
I'm continuing with more work on Monero. This is my request for donations for this work for the next three months.
......
---
layout: cp
title: "moneromooo: three months from November 2019"
author: moneromooo
date: 23 October 2019
amount: 395
milestones:
- name: first month
funds: 33.33% (131 XMR)
done: 1 December 2019
status: finished
- name: second month
funds: 33.33% (131 XMR)
done: 1 April 2020
status: finished
- name: third month
funds: 33.34% (133 XMR)
done: 27 June 2020
status: finished
payouts:
- date: 14 April 2020
amount: 262
- date: 28 September 2020
amount: 133
---
Hi,
I've been delaying this CCS because I'm going to have unknown time to work on Monero for the foreseeable future,
so I wasn't sure what to do. I've decided that the best is to continue as if normal, but the "months" may end up
taking more than a month, depending on how much time I spend on Monero. I cannot predict in advance how much of
my time will be spent on it. It may well be that I'll end up with full time on Monero, but there's no guarantee
of this at all. So, with this caveat clear to all, I apply for funding for the next three months' worth of work,
to cover November to January at least, and probably ending somewhat later than that. I'll still post monthly
updates along with how much time I put for that month.
Here's the link to my previous three months: https://repo.getmonero.org/monero-project/ccs-proposals/merge_requests/75
I have no particular things I'm planning to be working on as a definite, though I hope that CLSAG will be one of
them, if the audits get done. Dandelion was picked up by vtnerd. The new pay for service system could need some
more work. Otherwise it'll be whatever pops up at the time.
As usual, the target rate is $30 + 0.2 monero per hour, so with Monero currently at $53.63, we get 395 monero.
Thanks