meta VS tsqsim

Recommended Light Wallets on the Reddit sidebar and getmonero.org site should follow the Light Wallet API spec (https://github.com/monero-project/meta/blob/master/api/lightwallet_rest.md) and allow users to safely specify their own light wallet server URL in a very similar way that any other recommended wallet allows you to safely specify and use your own Monero node URL, otherwise, I believe these wallets should not be listed, or recommended. And, of course, the wallet should function in the same way with a user-provided URL as it does with the default, proprietary server, so long as the user-provided server follows the Light Wallet API spec.

Another big discussion planned for tomorrow, Wednesday, 8 March 2023: https://github.com/monero-project/meta/issues/808

A little late to the party; A long time ago I did some brainstorming about this myself:

Here you go, audit should be found here

correction. MoneroKon 2023 Planning Meeting is scheduled for Saturday 14th January 2023 @ 18:00 UTC

Hey Lynnaignet, it's very nice that you asked. My proposal is fully funded and I receive regular payments, as agreed, therefore so far I can't complain about this part. I do have a "tip" address, that can be found below, if you like: http://monerodevs.org/monero-research-lab.html But at the current stage, a nice word is enough. Not only for the emotional support, that I sometimes do need after being trashed by the restless troll(s). The thing is, that many Anons will simply never say a word, but will at most upvote comments as direct as yours. This alone gives me confidence, that I'm going in the right direction, despite the mentioned reviewing/merging resistance. It helps me plan the future proposals better. Then, after this non-verbal communication is done and the proposal is laid out, the Anons will just drop their Moneros in quite large quantities individually, onto the proposal's address. I find it quite interesting. What more can be done? I'd suggest that whenever you see a CCS Proposal of a Developer that sounds concrete and modest at the same time, like these: https://ccs.getmonero.org/proposals/seraphis-wallet-poc.html https://ccs.getmonero.org/proposals/j-berman-3months-full-time-2.html https://ccs.getmonero.org/proposals/tobtoht-feather-dev-2021-3.html https://ccs.getmonero.org/proposals/Rucknium-OSPEAD-Fortifying-Monero-Against-Statistical-Attack.html , then go ahead and fund them. These Devs with their social skills will typically be of a large value in whatever area that they focus on. Some time later they will stumble upon my PRs, after their high-priority tasks are done. So I hope at least. This would be a more passive way to help. An active way to help, that I'd normally not promote, as it sounds statist and bureaucratic, is to go to my PRs directly and show some support via emoticons, maybe writing some text to wake others up. If this doesn't help, then pinging potential reviewers directly (namely those, who are currently being funded by YOUR money after all) would be "The Last Card" here, but this should be avoided if possible, I think. Lastly other developers are indeed affected, indeed. Perhaps it sounds weird and I don't understand it fully, but they will usually accept the status quo, because they haven't yet seen a C++ project that compiles fast and delivers more functionality, than a typical C project would. I'm trying to prove that it's possible with my tsqsim project.

pip3 install statsmodels # New optional dependencies pip3 install darts git clone --recursive https://github.com/mj-xmr/tsqsim.git # Clone this repo (assuming it's not a fork) cd tsqsim # Enter the cloned repo's dir rm build/* -fr || true # Clear up previous configuration files git checkout benchmark # checkout the relevant branch ./util/prep-env.sh # Prepare the environment - downloads example data and creates useful symlinks ./util/deps-pull.sh # Download the maintaned dependencies ./util/deps-build.sh # Build and install the unmanaged dependencies (uses sudo for installation) ./util/build.py --benchmark --plot

I was very happy to work overtime in the 1st half of December, since I knew that family matters would slow me down later on. Therefore this month’s work was clearly divided into two portions. In the 1st one I was doing a lot of the necessary Continuous Integration (CI) work and made sure that the software works on all platforms, that are available on GitHub CI, which are:

For the whole month I’ve worked on being able to deliver the first public version of my Time Series Quick Simulator (dubbed "tsqsim"), that aims to support the Monero Research Lab in detecting and predicting transaction patterns, however the Researchers want to use them at a given time. The goal has been achieved and you can use the quite simple instructions written here, to see the first public version in action (so far Debian / Ubuntu 20.04 only):