A Fedimint federation operator deploying v0.11.1 on April 21 got a silent efficiency win: the recurring-payment daemon now sorts available Lightning gateways by fee before selecting one, rather than picking arbitrarily or leaving the choice to manual configuration. That sounds like internal plumbing, but it is the first time any production ecash stack has automated the economic routing problem that custodial wallets solve by default. When you route a payment through a cheaper gateway, the federation's markup on that transaction falls. Cheaper markup means more users stay inside the privacy perimeter instead of exiting to save a few satoshis.

Fedimint federations sit at the edge of the Lightning Network, connected through specialized gateway operators who also run Lightning nodes. A single federation can work with multiple gateways, creating natural competition on fee rates, but until now the software did not actually use that competition. The recurringd daemon, which handles recurring payments and fee estimation, would pick a gateway that satisfied the federation's liquidity constraints, it worked, but it was indifferent to cost. Version 0.11.1 changes that: recurringd now filters for available, vetted gateways and then sorts by fee, selecting the cheapest first. That is a one-line change in philosophy with real user-facing consequences. In a low-fee environment like the current one (2 sat/vB baseline), every percentage point of gateway markup saved is a percentage point of privacy cost reduced relative to custodial alternatives.

The v0.11.0 release formalized two experimental protocol modules, MintV2 and WalletV2, as opt-in rather than embedded. This is the engineering counterpart to the gateway work: as federations scale, they need flexibility in how mints encode state and how wallets structure transactions. Making these modules opt-in rather than default lets operators choose their stability-privacy tradeoff explicitly instead of forcing every federation to accept the same protocol version. LNv2 functionality was removed from the v1 recurringd daemon, pushing operators to migrate to recursingdv2, a deliberate push to consolidate the gateway codebase. Jemalloc, the memory allocator that improves performance under high throughput, moved behind a feature flag, keeping the dependency surface smaller for downstream crates that do not need it.

Here is what this actually means: Fedimint has been gaining real users because it solves payer privacy inside a self-custodial framework. But privacy has a cost. Every time a user routes a payment through a gateway to reach the broader Lightning Network, they pay a fee. That fee is a friction point, it gives users incentive to exit the privacy layer and use custodial wallets on the Lightning Network directly. Automating fee-optimal routing closes that friction. A user in a well-capitalized Fedimint federation now has no reason to choose a cheaper custodial wallet on privacy-cost grounds alone, because the system itself is now selecting the cheapest available path. That is not a guarantee that Fedimint becomes cheaper than custodial alternatives on every transaction, federation overhead and gateway markup are still real. But it means the privacy penalty is no longer hidden in arbitrary gateway selection; it is now transparent, optimized, and only as high as the actual cost of the routing service.

The v0.11 branch has been shipping since spring 2026, introducing gateway recovery via mnemonic, a critical operational feature for federation operators managing their Lightning infrastructure. This point release does not add a feature; it optimizes the existing one. But optimization at the protocol layer is where ecash infrastructure matures from experimental to viable. Watch for three markers: whether major federation operators upgrade to v0.11.1 within the next month (adoption speed), whether any federations deliberately run multiple competing gateways to surface the fee-sorting logic (architectural adoption), and whether the gateway markup as a percentage of total transaction cost visibly declines in federation audits (the measure that matters most). If none of those happen, the change is elegant but unused. If all three do, Fedimint has solved one of the last major economic barriers between privacy and convenience.