mj’s dev report May-June 2022 (3/3)

Dear Community,

There has been an overwhelming dose of psychodrama in the last month of my CCS Proposal. I thought I'd write all the details, but in the end I decided to spare your time and only outline you the key points, without mentioning too many names:

  • I was being called a scammer for the whole 2 years of my work now, by a single annoying person, because people don't know how to verify my measurements properly, even though I tried to explain them. Some decisive persons were taking this propaganda seriously.
  • The same person has been attacking many other people too, but mainly those who cooperate with me in this or other way, especially in MRL – specialists who are paid twice as much as I do, essentially greatly wasting the money that YOU pay.
  • Luigi (the Gent, who's responsible for merging branches and managing the funds) has been accused by the same person of bribery, for paying me, "The Scammer", even though he always pays me after completion of the tasks, which are presented to and approved by the Community.
  • Moderators on Matrix/IRC were only partially helpful, because they didn't ban the mentioned Trojan Horse once and for all. Besides, whatever they do, he already has 10 sock puppets ready for this.
  • Also, other crucial members seem to be on the hook of the person's Crypto Knowledge. It sounds like a huge unhealthy case of Codependency, if you ask me. Why would they be investing any time into such unstable and arrogant person in the first place?
  • Since at my last Community Meeting that I ever attended, I was pushed so far by the same person, that I to handle the problem myself in my way, I exploded finally, said one or two sentences too much, and decided to leave these largely unmoderated channels for good. This made it easier for the Mods to handle the case, since they didn't have to decide anymore for how long to ban me. Fixed it for ya.
  • Shortly after I had left the Community channel, it was proposed there that I shouldn't receive any funds for this period, regardless of the state of completion of my work, until I publicly apologize for my behavior. I'm sorry to disappoint you, but I don't apologize for defending my basic human rights.
  • Luigi confirmed privately, that personal disputes are not a reason to influence the payments. Honestly, if it was different, this would open a can of worms on the whole CCS, when you think how many moral hazards, in form of other provocations, would suddenly be possible.
  • Regardless, in order to be eligible to receive the last and the current payment, I was asked by the Core Team to prepare hourly accounting for both periods. Each such tedious report cost me a day, where I couldn't do any productive work. Since I don't work for free, I include this time as work time and share the report as a text file. You decide if it was worth the money, that you paid to my CCS Proposal. Perhaps rightfully so!

If you'd like to have a sneak peak on what is going on, here's a cute little YEAR OLD Pull Request, that reflects the current schism. I have strong evidence, that the author (perfect-daemon) is the same person, who's been calling me a scammer all the time and undermining my work in all possible ways. More on this maybe on another occasion. I think he consumed so much time of so many people, mainly on the chat channels, that I feel like I've already written too much.

Summary of my May-June work period

I spent the contracted time on reviews, maintaining my still open branches and fortunately on Monero Research Lab's task of reimplementing the Decoy Algorithm.

Here's the full list of the PRs reviewed by me: – 83338337835283488356835983657760835983818382

This time I saw no need of opening any branches in Monero Core/GUI. I only focused on maintaining the already opened branches and trying to get them merged. However due to negative propaganda towards my work, it was so far impossible to do it and I spent a good deal of time on trying to prove my points. So far to no avail. See the recently updated (very technical) report under this PR. An outline of this entire discussion would be that: – it was being misunderstood all the time (for 2 years now?), that my speed improvements were targeted for developers, who are supposed to compile the code very often and very quickly, rather than users, who would compile the code from source only once in a quarter. – as such, even though I provided objective methods of measurements (the Clang Build Time Analyser script), their results were being doubted all the time and confronted with measurements done from the User's perspective. In case of 7217, these measurements were underestimating my measurements greatly. – I had to create special tooling here & here, that executes the appropriate build time tests on GitHub's servers, where nobody can tamper the results in neither of the two directions.

I obviously communicated these points at each possible occasion. Perhaps it will work another time.

Large ongoing tasks

Morero Core – libwallet tests

https://github.com/monero-project/monero/pull/8264 I wasn't able to deal with this as too much extra unplanned effort was requred from me. This included the hourly accounting and proving, that I don't cheat on the measurements. The branch itself is however nicely encapsulated in a way, that allows anybody to continue the work from freshly prepared and properly working an environment.

Monero Research Lab

Simulation of the fee increases.

For the same reasons as above I've never had time to touch it even.

Decoy algorithm

Now here's the good news finally. Together with u/Rucknium, we've finally been able to deliver a proof of concept of the decoy algorithm's reimplementation. As a reminder from my previous report:

Rucknium, J-Bermann and me are breaking down the decoy algorithm in order to better understand its flow by performing statistical tests on it. For this, we need to have an alternative implementation. Python was chosen to be the language, which offers a large variety of frameworks and is widely used among Researchers. My take is being documented here.

The new thing is, that as soon as the Python implementation was in place and Rucknium confirmed the validity of the results delivered by the re-implementation against the C++ original, using statistical tests, such as the Kolmogorov-Smirnov test, it didn't take long until he pushed his R reimplementation, based on the Python one, that passes the very same tests. This means, that:

  • Rucknium can finally continue his Decoy algorithm research, meant to provide the privacy that the coin promises
  • we've both found enough reasons already to be concerned about the current algorithm and will continue the research to mitigate the problems.

I can't disclose more than this, until the appropriate remedy is proposed, which (I believe) is in accordance to Monero's Vulnerability Response Process . Perhaps u/Rucknium himself would like to elaborate however.

SolOptXMR

I spent the agreed average of 10h/week on SolOptXMR to deliver the first Milestone and a Minimal Viable Product ASAP, as reported here already. This allowed me to gather feedback soon enough, which was mostly positive. Many people had been suspicious about the project at first, but as soon as the results were in place, they started to understand the whole point and had their individual Eureka Moments. I'm glad I could inspire y'all 🙂

Initially I was focusing much more on the SolOptXMR project at the beginning of this phase, but as soon as the MVP was released and published, I went back to the remaining contracted 30h/week work, only occasionally fixing small bugs of the SolOptXMR project as they were occurring.

Conclusion

With all the bad rap against my work that was only briefly mentioned at the beginning of this report, I conclude that the decisive persons don't require as many as 30h/week of the skills, that I'm able to offer. At the same time, I'd like to have my time occupied with something that I already know how to do well, rather than having to learn yet another new skills, just to be able to reuse them only for as long I agree to being pushed around like I have been. That's why my next CCS Proposal will be focused on MRL only, and its associated tsqsim project, which had been requested by u/Rucknium, yet it's still in an unfinished state. I don't think I will accept pulling me from the stated MRL Proposal back to Core/GUI, like it has been done previously, with a very short notice and having everything planned differently. It's been a hell of a pain in the neck this time, so thanks to everybody who supported me in any way possible! And now – I need a break…

mj

Accounting report for 2nd and 3rd milestones: “`

01-04-2022 : 14-04-2022 : Never counted

01-04-2022 : 14-04-2022 ~10h Preparing scripts for my laptop to be able to work remotely.

02-04-2022 dynamic libs ~4h https://github.com/monero-project/monero/pull/8235

03-04-2022 R: NanoS+ ~0.5h https://github.com/monero-project/monero/pull/8232

06-04-2022 R: GUI-bumb-windows-deploy 0.5h https://github.com/monero-project/monero-gui/pull/3879

07-04-2022 R: 0.15h NanoS+ – release https://github.com/monero-project/monero/pull/8239 0.25h RandomX: Update submodule https://github.com/monero-project/monero/pull/8240 0.1h RandomX: Update submodule release https://github.com/monero-project/monero/pull/8241 7h EPEE Cleanup Reorganized https://github.com/monero-project/monero/pull/8211

08-04-2022 R: 2.5h Update languagex.xml https://github.com/monero-project/monero-gui/pull/3853 0.15h Docker: Update zlib for android https://github.com/monero-project/monero-gui/pull/3875

12-04-2022 R: 0.15h Makefile: fix spelling of CMAKE_BUILD_TYPE value https://github.com/monero-project/monero/pull/8246 0.5h readme: small fixes https://github.com/monero-project/monero/pull/8247

14-04-2022 0.6h MRL: new repo https://github.com/mj-xmr/monero-mrl-mj

10+4+0.5+0.5+0.5+0.15+0.25+0.1+7+2.5+0.15+0.15+0.5+0.6 + = ~27h The above time has NEVER been taken into account when asking for payouts.

15-04-2022 – 15-05-2022 : Milestone 2

15-04-2022 0.2h .vscode to gitignore https://github.com/monero-project/monero/pull/8260

18-04-2022 1.5h Doc: Disable RPC ban for the private nodes https://github.com/moneroexamples/private-testnet/pull/9 18-04-2022 8h Tests: libwallet_api_tests fixing scripts https://github.com/monero-project/monero/pull/8264

23-04-2022 1h R: FutureScheduler: delete unused function declarations https://github.com/monero-project/monero-gui/pull/3888 23-04-2022 0.5h R: main: only update fiat price with open wallet https://github.com/monero-project/monero-gui/pull/3890 23-04-2022 0.5h R: Mining: only update mining status when page is open https://github.com/monero-project/monero-gui/pull/3889 23-04-2022 0.25h R: workflows: action-docker-layer-caching v0.0.11 https://github.com/monero-project/monero-gui/pull/3887

24-04-2022 1h R: build: prepare v0.17.3.2 https://github.com/monero-project/monero/pull/8273

25-04-2022 3h Reproducible builds

26-04-2022 3h Trying to fix stale Rep.Builds https://github.com/mj-xmr/gitian-builder-mj/tree/master

27-04-2022 1.5h Gitian: refresh the stale Monero dir via –setup switch https://github.com/monero-project/monero/pull/8296

28-04-2022 2.5h R: readme: arch/fedora deps + small fixes https://github.com/monero-project/monero/pull/8281 28-04-2022 0.25h R: Change "Github" to "GitHub" https://github.com/monero-project/monero/pull/8300 28-04-2022 0.5h R: Update year to 2022 https://github.com/monero-project/monero/pull/8297

29-04-2022 2h Update copyright to 2022 for Hardfork files (via script) https://github.com/monero-project/monero/pull/8302

30-04-2022 3h GUI Reviews https://github.com/monero-project/monero-gui/pull/3846 https://github.com/monero-project/monero-gui/pull/3903 https://github.com/monero-project/monero-gui/pull/3902 https://github.com/monero-project/monero-gui/pull/3883 https://github.com/monero-project/monero-gui/pull/3483 https://github.com/monero-project/monero-gui/pull/3560

01-05-2022
0.25h R: Doxygen: Hide anonymous namespaces from documentation https://github.com/monero-project/monero/pull/8301 0.5h R: readme: arch/fedora deps + small fixes https://github.com/monero-project/monero/pull/8281

02-05-2022 1.5h R: workflows: add caching for docker android https://github.com/monero-project/monero-gui/pull/3908

12-05-2022 0.35h Small reviews https://github.com/monero-project/monero/pull/8318 https://github.com/monero-project/monero/pull/8307 https://github.com/monero-project/monero/pull/8308

(SolOptXMR not counted)

MRL meetings between 14 Apr and 15 May (excl 18 May) 4 Meetings * 1.25h = 5h It's too hard to count how much time it all took, but this is what I've been doing for MRL every registered day for ~3 hours: https://github.com/mj-xmr/monero-mrl-mj/pull/1/commits = 3h * 11 days of work on this topic alone

0.2+1.5+8+1+0.5+0.5+0.25+1+3+3+1.5+2.5+0.25+0.5+2+30+0.25+0.5+1.5+0.35+5+3*11

= 96.3 h

20-05-2022
https://github.com/mj-xmr/monero-mrl-mj

https://github.com/monero-project/monero/pull/8232 took part in release testing!

MEETINGS! Przynajmniej 1 h tygdniowo + Community!

16-05-2022 – 18-06-2022 : Milestone 3

16-05-2022 Accounting for Milestone 2: April 15 – May 15 10:30 – 13:30 – 3h 15:00 – 18:00 – 3h

16-05-2022 – 18-05-2022 3 * ~5h MRL branch: decoy https://github.com/mj-xmr/monero-mrl-mj/pull/1

19-05-2022 – 20-05-2022 2 * ~5h Decoy algo's Python reimplementation https://github.com/mj-xmr/monero-mrl-mj/commits?author=mj-xmr&since=2022-05-19&until=2022-05-20

21-05-2022 0.75h R: Focus Doxygen documentation https://github.com/monero-project/monero/pull/8333 0.5h R: src, epee: fix a couple compiler warnings https://github.com/monero-project/monero/pull/8337

24-05-2022
0.75h R: epee: more dead code https://github.com/monero-project/monero/pull/8352 0.5h R: epee: http_server_handlers_map2 https://github.com/monero-project/monero/pull/8348

28-05-2022
1h R: wallet_api: add scanTransactions function https://github.com/monero-project/monero/pull/8356

30-05-2022 2h R: connection: fix implementation https://github.com/monero-project/monero/pull/7760

31-05-2022 1h R: GCC: unused warnings https://github.com/monero-project/monero/pull/8359 2h R: epee: fixed incorrect RNG usage https://github.com/monero-project/monero/pull/8365 1h R: connection: fix implementation https://github.com/monero-project/monero/pull/7760

27-05-2022 – 04-06-2022 Proving the continuously disregarded build time improvements about 2h each day https://github.com/mj-xmr/monero-patches/blob/master/src/monero-test-build-time.sh https://github.com/mj-xmr/monero-patches/blob/master/src/workflow-build-time-test.patch https://github.com/mj-xmr/monero-patches/commits?author=mj-xmr&since=2022-05-31&until=2022-06-04

02-06-2022 2h R: GCC: unused warnings https://github.com/monero-project/monero/pull/8359

03-06-2022 4h Reported the results of the build time test https://github.com/monero-project/monero/pull/7217

10-06-2022 1h R: Fixed get_block_template_backlog performance https://github.com/monero-project/monero/pull/8381 1h R: renamed and added comments to get_destination_view_key_pub(..) https://github.com/monero-project/monero/pull/8382

10-06-2022 – 19-06-2022 ~ 6h * 9 (still not done yet) MRL full time @ ~5-8h daily (rounded down to 6h). Topic: Decoy algo reimplementation and statistical tests with Rucknium. Deployment on gingeropolous servers.

17-06-2022 Accounting for May 15 – June 15 14:00 – 18:30 = 4.5h

18-06-2022 Reporting 6h

23+15+10+(0.75+0.5)2+1+2+1+2+1+28+2+4+1+1 + 69 + 4.5 + 6 = 129 h “`

submitted by /u/mjxmr
[link] [comments]

Leave a Reply

Your email address will not be published. Required fields are marked *