farcaster-node VS rust-internet2

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

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

We started contributing upstream to rust-internet2, a project devoted to creating the networking components and runtime backbones for building trustless, censorship resistant, and private decentralized applications. We implemented the abstractions needed to support transmitting our peer protocol messages over the wire between the swap participants, and the rust-internet2 maintainer has been very welcoming.