Neither does fedimint's ecash. The client associates the notes it holds with a federationId and can change that association the same way you do with the mintUrl.
It's more complex for the fedimint guardians to agree on an update to the config, creating the new federationId, but in principal it's the same. the approach to that consensus update process just needs to get agreed on and implemented as part of the next release or potentially a hotfix.
kodylow / Kody Low
npub1m6…2mzj9
2024-06-25 18:13:34
in reply to nevent1q…rh5r
Author Public Key
npub1m6yz8nwf0xl5cafjy0kurxn6hs67eleft8h4pj57n4tn4s8c8lgqd2mzj9Published at
2024-06-25 18:13:34Event JSON
{
"id": "3c406e3cd72ae3d2db7b94da4a1d590a86807234bf249b3bab64438e94653b63",
"pubkey": "de8823cdc979bf4c753223edc19a7abc35ecff2959ef50ca9e9d573ac0f83fd0",
"created_at": 1719339214,
"kind": 1,
"tags": [
[
"e",
"6e2ff096e25e47355400b528025695ef6d22b815539cbb9b20965ad1a76805fa",
"wss://relay.primal.net",
"root"
],
[
"p",
"ddf03aca85ade039e6742d5bef3df352df199d0d31e22b9858e7eda85cb3bbbe"
]
],
"content": "Neither does fedimint's ecash. The client associates the notes it holds with a federationId and can change that association the same way you do with the mintUrl. \n\nIt's more complex for the fedimint guardians to agree on an update to the config, creating the new federationId, but in principal it's the same. the approach to that consensus update process just needs to get agreed on and implemented as part of the next release or potentially a hotfix.",
"sig": "7a3c477580d7bb34b2b8bc5a80a15a890bdf9c912eaee434a9e060a2b2b95a0e4da5550018a0a3f53a00909357b1d8abda4b583d67edde63fc533b5178d812f8"
}