monero-rs VS monero-lws

Good documentation on regtest took a while to locate. One of the challenges I've experienced is due to Monero's design with ring signatures, one-time-addr, etc any client library that wants to directly integrate against the Monero daemon basically ends up either needing to import wallet_api or reimplement a lot of core behavior. https://github.com/monero-rs/monero-rs is fantastic but it's not a complete solution for a lot of use cases. I think Javascript and Rust probably have the best Monero support libs outside of C/C++ ATM.

I haven't been following but somebody has started writing rust libraries: https://github.com/monero-rs/monero-rs

Is this the rewrite from the post or where can I find it? Is there a place where we list all rewrites?

I am a huge fan of rust for this kind of work, and the crate is very well made: https://github.com/monero-rs/monero-rs

Additionally, monero-rs and rust-internet2's new upstream releases include our PRs needed for Farcaster :)

Since we started the Farcaster project, two new releases of monero-rs came out to deliver features needed for the swap protocol, the latest release being v0.12.0.

I just wanted to share that I released a tool called 'Monero-LWS-Admin' a couple weeks ago that is a web-based GUI that taps into the newly-added admin REST API for VTNerd's light wallet server (https://github.com/vtnerd/monero-lws). Also important to note: this API is only available on the develop branch of vtnerd/monero-lws at the moment. The point of the monero-lws-admin app is to just make it very easy to add/update/deactivate Monero LWS accounts. Make sure to only expose it on a secured network and do not expose it publicly as it would allow anyone to add LWS accounts to your server. This is newly created software, so use at your own risk and please feel free to write up issues/feature requests at the repo below.

You could use the private view key with something like the mymonero rest api?

Also shoutout to all the other great monero payment projects with great things in the works, check them out: monero-lws, https://github.com/busyboredom/acceptxmr, https://gitlab.com/moneropay/moneropay, https://git.sr.ht/~anon_/shadowchat, https://github.com/monero-integrations/monerowp)

monero-lws is an awesome tool for individuals who run their own nodes and I want to help get it out there to more people. And the code is silky smooth and easy to read, major props to u/vtnerd. I think subaddress support will be huge because it will also make light wallets more compatible with other wallets. And agree a formal build process (and releasing binaries) + continuous tests would be sweet. I'm gonna look into setting up a test framework while working on subaddress support.

Informal audit of monero-lws

The sync time actually could be mitigated by the wallets themselves by finding the way how to move the sync process into the background to run it all the time. Of course, this is not so trivial to do as it sounds because some platforms have technical limitations e.g. iOS has a very limited policy for background tasks. Nonetheless, there are still ways how this could be bypassed, and one of them I'm using myself: MyMonero + monero-lws on a dedicated hardware which is running 24/7. With this setup I have instant status of my wallet status anytime, even after a month without sacrificing any(?) privacy. Of course, this is still miles away from being "friendly to use / good UX" because first and foremost it requires building "monero-lws" from the source code where most of the non-tech-savvy would immediately fail, there are other setup challenges as well but that's not the point. The point I wanted to make is that wallet sync time definitely has ways in which it can be improved, at least from the UX perspective. Sometimes solutions needs a bit more out-of-the-box thinking.

Also important to note from that post discussing the bugs: the initial reported bug turned out to be not as severe (i.e. you actually cannot definitively identify real outputs spent right after unlock because of the bug). We found that an alternative implementation of the algorithm (in monero-lws) did not have the bug and is widely used by at least one popular wallet (MyMonero). So that means anyone using MyMonero's transactions could have feasibly selected recent decoys, and therefore recent outputs on chain could be decoys.

We have now completed the necessary interfaces for communicating with both blockchains - something we termed syncers. The integration work in the node is mostly complete. For bitcoin, we are currently using the electrum protocol, while for monero we are communicating with the monero daemon and monero-wallet-rpc. Using the monero-wallet-rpc for multiple swaps at a time proved quite slow during our testing, so we are now exploring the usage of vtnerd's monero light wallet server. In contrast to the monero-wallet-rpc, the light wallet server can keep track of and scan for transactions of multiple distinct view keys at a time. Our work integrating the monero rpc interfaces also led to some pull requests to monero-rpc-rs in the monero-ecosystem project.

Technically, yes, but it’s fairly difficult and not user friendly at the moment. I believe it can be done with OpenMonero and monero-lws, both created by community members. Here’s the repo to lws: https://github.com/vtnerd/monero-lws