Notes from today’s Fedimint dev call. Jotted down while listening in.

TAB Conf demos kicked off. Release candidate 4 was used to setup a fedimint about a dozen times with different configurations. Once 0.1 releases, docs from this evolution will be released.

Ben Carman made Mutimint - Mutiny is now an ecash wallet. 1/1 federation as an example.

FEDIMINT v0.1 RELEASING TODAY!!

Fixing a blocking RPC call during DKG.

Discussion around config encoding and surfacing the information via the API. Discussed creating a CLI command to view the client config. Additional discussions around adding and editing metadata during initial setup of a fedimint, but still cannot update a running fedimint. There’s some complications with hashing over JSON vs strings on the Rust side of the house that makes some of the config work tricky.

There was discussion around adding some data around Guardians information so clients can query and know “who” the Guardians are.

Can add meta fields of fedimintd using ENV VARS.

Docker tags now part of CI/CD.

Releases will be in a branch and tags will be made off that branch. This allows for backporting to the branch any changes that are relevant.

Devimint in a docker container! Discussing around running the UI for different users.

Investigation into running tests on android/iOS simulators was discussed.

GitHub actions won’t run on forked version of Fedimint.

Fedimint dev-tools container available on docker hub.

Added a shortcut command/alias to dump database for specific server in the regtest dev setup.

Fedimint gateway integration with LSP by adhering to LSP spec.

LDK dependencies were updated by the Mutiny team (benthecarman) to resolve an issue seen during TABConf hackathon.

CLN update to v23.08 is causing some CI failures but otherwise ready for merge.

DB compaction of outstanding LN contracts now make the audit summary way more performant.

Gateway web server now is long-lived so config and other things can be managed without tearing it down. Updating fees or gateway password can then be updated.

Version of consensus on master branch is u32::MAX to hopefully indicate that it should not be used. This is updated in release branches.

A couple of “good first issues” were labeled involving surfacing available modules via CLI.

A GH discussion will be started around how Cashu encodes mint information into a token so once exchanged, a user can know where to redeem said ecash.