Skip to content

Releases: fedimint/fedimint

v0.3.2-rc.0

23 May 20:42
v0.3.2-rc.0
bcc85e8
Compare
Choose a tag to compare
release candidate v0.3.2-rc.0

v0.3.1: Forward, backward, sideward compatibility? II

08 May 19:16
v0.3.1
dbabb5f
Compare
Choose a tag to compare
  • Added Premetheus metrics
  • Utils for fetching meta fields and vetted gateways (#4856)
  • Minor fixes

What's Changed

  • Backport fix: bump wait_server_status timeout by @bradleystachurski in #4731
  • [Backport releases/v0.3] chore: add clap version command to all binaries by @fedimint-backports in #4739
  • [Backport releases/v0.3] chore(devimint): bump lnd polling to 60s by @fedimint-backports in #4741
  • [Backport releases/v0.3] chore(fedimint-cli): increase wait-block-count to 60s by @fedimint-backports in #4747
  • [Backport releases/v0.3] chore: make client task group available to modules by @fedimint-backports in #4770
  • [Backport releases/v0.3] chore: expose try_download_client_config by @fedimint-backports in #4774
  • chore(metrics): labeled grouped promethus metrics for wallet module (Backport 4697 to releases/v0.3) by @dpc in #4758
  • chore(metrics): labeled grouped prometehus metrics for wallet module (Backport 4696 to releases/v0.3) by @dpc in #4759
  • [Backport releases/v0.3] chore(devimint): increase default poll timeout from 30s to 60s by @bradleystachurski in #4833
  • chore: bump h2 [backport] by @maan2003 in #4857
  • [Backport releases/v0.3] chore(consensus): log items failing max size validation by @fedimint-backports in #4902
  • mass backport by @maan2003 in #4856
  • backport: feat: gateway filter for update_gateway_cache_continuously by @maan2003 in #4906
  • backport: fix: use u64 for attempts in fedimint retry by @maan2003 in #4933
  • backport: chore: auto update on list-gateways by @maan2003 in #4920
  • chore: backport #4876 (update jsonrpsee) by @elsirion in #4980
  • fix(recovery): can't recover without all server-side modules (backport v0.3) by @dpc in #4987
  • feat(nix): expose fedimintd NixOS module (v0.3 backport) by @dpc in #5062
  • chore: bump to v0.3.1-rc.1 by @elsirion in #5030

Full Changelog: v0.3.0...v0.3.1

v0.3.1-rc.0

10 Apr 08:50
v0.3.1-rc.0
446f967
Compare
Choose a tag to compare
release candidate v0.3.1-rc.0

v0.3.0: Forward, backward, sideward compatibility?

01 Apr 16:59
v0.3.0
a41e3a7
Compare
Choose a tag to compare

Upgrading

fedimintd

  • Stop all federation guardian fedimintds
  • Make a backup of the whole data dir (contains a bunch of JSON files and a database directory)
  • Verify that all fedimintds in the federation are off
  • Upgrade the fedimintd binary through the deployment method of your choice
  • Restart all fedimintds
  • Verify in the admin UI or via fedimint-cli that all of them are online again and making progress producing sessions

Note that, when upgrading from 0.2, you will not get the new Meta module, which otherwise gets added automatically to new setups now. In 0.4 we will add functionality that will allow retroactively adding the module. For compatibility with old clients it is still advised to use the meta_override_url field.

Clients

Just using the new version of the client library should do. There were some rust interface changes, especially around LN gateways, but nothing too major. Reach out on GitHub or Discord if anything is unclear.

Downgrading

Downgrading to previous versions is unsupported and will likely fail.

What's Changed

New Features:

  • Dynamic meta fields through the Meta module
  • Improved load-test-metrics for better performance insights.
  • Capability to pass --auth flag to fedimint-cli dev api.
  • Added recovery tool tests for enhanced reliability.
  • Enhanced LN payments privacy for LND.
  • CLI improvements and more configurable options.
  • Added support to pay a lnurls.
  • Implemented a special case descriptor for single-guardian instances for smaller on-chain transactions.
  • Introduced versioned Gateway API for backward compatibility.
  • Introduced a latency test for restore functions.

Fixes and Updates:

  • Introduced a simplification for always proposing block height and feerate votes.
  • Multiple fixes including singular naming in MintOperationMetaVariant, serialization of enums in snake case for API consistency and adjustment for HTLC processing.
  • Addressing warnings and errors for more robust operations and deployment.
  • Various fixes to ensure compatibility and optimization across different platforms, networking conditions and operational scenarios.
  • Database migrations for consistency and performance.
  • Client-side transaction size checks to prevent unexpected server-side rejections

Chore and Maintenance:

  • Several chores to clean up code, improve build and testing processes, and update dependencies.
    *Introduction of concurrency and latency optimizations.
  • Documentation improvements including more information on cargo packages and updating READMEs.
  • Refactoring efforts for cleaner and more maintainable code design.

Security:

  • Updated dependencies and code changes to address known vulnerabilities.

Detailed list of PRs:

Read more

v0.3.0-rc.3

25 Mar 22:40
v0.3.0-rc.3
c32bbe8
Compare
Choose a tag to compare
v0.3.0-rc.3 Pre-release
Pre-release
release candidate v0.3.0-rc.3

v0.3.0-rc.2

25 Mar 10:19
v0.3.0-rc.2
44f129b
Compare
Choose a tag to compare
v0.3.0-rc.2 Pre-release
Pre-release
release candidate v0.3.0-rc.2

v0.3.0-rc.1

21 Mar 13:40
v0.3.0-rc.1
c51ea0c
Compare
Choose a tag to compare
v0.3.0-rc.1 Pre-release
Pre-release
release candidate v0.3.0-rc.1

v0.3.0-rc.0

19 Mar 20:16
v0.3.0-rc.0
45c945d
Compare
Choose a tag to compare
v0.3.0-rc.0 Pre-release
Pre-release
release candidate v0.3.0-rc.0

v0.2.2: : Federate all the Things II

06 Feb 20:57
v0.2.2
a849377
Compare
Choose a tag to compare

This release fixes a lot of bugs, both client authors and federation operators are recommended to upgrade.

Guardian Upgrade Process

We recommend proceeding as follows:

  • Coordinate a time with all guardians
  • Everyone shuts down their fedimintd service
  • Make a backup of the data dir
  • Upgrade fedimintd to v0.2.2 (how depends on the deployment method)
  • Check that the version matches for everyone by running fedimintd version-hash
  • Everyone starts their fedimintd service again

While this is not a consensus upgrade and thus doesn't require coordination we recommend not running different versions of fedimintd together since it is not supported and hasn't been tested.

Highlighted Changes

For the complete set of changes see https://github.com/fedimint/fedimint/commits/v0.2.2/

v0.2.2-rc8

02 Feb 07:02
v0.2.2-rc8
d3e154e
Compare
Choose a tag to compare
release candidate v0.2.2-rc8