monero-rs VS farcaster-node

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.

(There's an AwaitingFunding..(..) decrementing bug that we'll fix)

Currently, the farcaster-node is able to make public offers, and awaits for the counterparty peer to connect and take the offer. We successfully tested making and taking an offer over the wire from separate machines. Over the past month, most work went into farcasterd and swapd. farcasterd is the manager of swaps: it initiates them, and has information about all the running swaps and open offers that are running. farcasterd launches swapd that takes over the swap protocol for a particular swap - multiple swapd instances can be launched in parallel for parties that engage in multiple swaps simultaneously, like market makers. Work for the next month will be focused on completing the protocol run inside swapd. Currently, the remote peer connection does not support our protocol messages due to upstream limitations. To overcome that...

The Farcaster Core is used on the Farcaster Node. Yes, we started work on the node! Farcaster Node is a fork from lnp-node. So far, we've been busy with the necessary modifications and clean-up to transform a payment channel node (lnp) into a swap node (farcaster), such as integrating the swap protocol and other messages into the node's APIs.