2023-08-28 Fedimint Dev Call Summary

https://habla.news/u/EthanTuttle@learnfedimint.com/1693241710650

For more details, please view the recording here: https://bitcointv.com/w/4MDVgBucaxPZJvbBZaoPNG And find the list of PRs/Issues here: https://github.com/fedimint/fedimint/wiki/August-28,-2023

For fedimintd, there were a some flaky tests resolved. One test was flaky due to how the consensus was formed around block height. There was also progress announced for audit summary; the summary is not available via API.. Discussion occurred around optimizing the auditing code by compacting LN contracts for gateways and around looking into database encoding/decoding optimization. The database work has not been done yet but a background task was added to compact LN contracts; which is in draft PR status. There is a new UI Issue filed to add the this audit information to the Guardian dashboard. Another flaky test was fixed using environment variables to manage db migrations.

A few LN related PRs were made. One to enable to gateway to configure and register the number of route hints. Another was completed to allow LND to pay <1 sat invoices in tests. The sub-1 sat invoice payment involved updating the channel configuration since the LND default is 1 sat. A commit hash was pinned for the ldk-node dependency; this will be updated once a release is complete for LDK node.

Some extra documentation and explanations were added to Client code for serialization/deserialization and metdata, and outcomes for operations.

A PR was merged to prefix ecash notes with the fedimint id for better external consumption.

Progress has been made for TOR support. This PR for jsonrpsee will enable it to use TOR as the underlying communication layer. Once this upstream code lands, the RPC client can be updated in fedimint to enable TOR.

There is now a tagged v0.1.0-rc1 commit in the main fedimint repository. Moving forward there should be a "release" every 1 to 2 months with periodic backports for bug fixes. As time progresses a more stable release cadence will be established with long term support releases for fedimint. It is recommended that developer peg to this release and file any issue or bugs in the main fedimint repository. Any fedimints using this release tag should expect no backwards compatibility or database migration with the next release and will need to shutdown and restart any mint they have running to migrate.