npub1m6…2mzj9 on Nostr: This is also possible in principle with the fedimint client, there's more complexity ...
This is also possible in principle with the fedimint client, there's more complexity for doing the upgrade because the client associates its notes to the federation id which contains the original endpoints and the guardians have to first agree on the new config then the client has to acknowledge the new config.
99% of the complexity for fedimint here is the consensus not the ecash. But there's (potentially, still confirming implementation options) a short term fix for existing federations to allow a DNS rotation by a guardian and that being acknowledged and reflected in an updated client to reassociate its notes with the new config. Plus a longer term solution to remove the DNS dependency for new federations entirely.
99% of the complexity for fedimint here is the consensus not the ecash. But there's (potentially, still confirming implementation options) a short term fix for existing federations to allow a DNS rotation by a guardian and that being acknowledged and reflected in an updated client to reassociate its notes with the new config. Plus a longer term solution to remove the DNS dependency for new federations entirely.
quoting note1dch…2qvmBecause there is much chatter going on right now:
Cashu Token Proofs / Signatures do not encode a mints URL. If a mint would loose its domain, wallets could simply update the URL and spent the token there. 🥜🫡