maan2003

The `name_of_cx` function is very ugly but is simplest among the alternative I have tried out.

> Could we also reply to normal HTTP requests on the same port with our current setup @Maan2003? It is not possible with current setup. But migration should be easy...

Most of it is already possible. We have [`Database`](https://github.com/fedimint/minimint/blob/603e9d1259d8c3a9d71d305bd1c8d42ec3457e24/minimint-api/src/db/mod.rs#L37) and [`FederationApi`](https://github.com/fedimint/minimint/blob/603e9d1259d8c3a9d71d305bd1c8d42ec3457e24/mint-client/src/api.rs#L16) traits. We can provide the concrete impls [during initialization](https://github.com/fedimint/minimint/blob/603e9d1259d8c3a9d71d305bd1c8d42ec3457e24/mint-client/src/clients/user.rs#L47). There will be a separate `mintclient-web` crate which relies on...

this was discussed on telegram, we reached the conclusion: use `&mut self` in the method if it needs to restrict concurrency. The caller can put the Client in mutex if...

I vote for Rocksdb. - Rust bindings look well maintained - straight forward way to implement [prefix interator](https://docs.rs/rocksdb/latest/rocksdb/struct.DBWithThreadMode.html#method.prefix_iterator)

> This is because The JS runtimes on iOS and Android don't support wasm yet. that is not correct. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WebAssembly#browser_compatibility

Oh, that makes sense. > This approach compiles the rust code to native iOS and Android libraries and uses Java/Swift bindings to call into native code from the JavaScript environment....

Not having those settings is definitely better than not able to run the app. So I think releasing a new version, that supports

maybe it should depend on file extension, I wouldn't mind auto tracking *.rs or *.toml or *.sh files

https://github.com/fedimint/fedimint/pull/4557 upgrade most of deps