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 (although this one is arguable)
• regenerating and extending my Monero health report
• 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 tool for Monero Research Lab's OSPEAD 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, 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, 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
• Report 02
• Report 03
• Report 04
• Report 05
• Report 06
• Report 07
• Report 08
• Report 09

Previous CCS Proposal Postponed CCS Proposal (tsqsim)

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. 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