elsirion

> BOLT12 support I think that's independent of TR but needs FROST/ROAST, right? I also talked to @real-or-random about ROAST yesterday, key points: * Without a central coordinator, meaning every...

I think after Tim's talk at TABConf I now understand the concept sufficiently well. We can (and probably shoudl) essentially use ROAST inside HBBFT. It would proceed as follows (for...

What is your proposed alternative action? Crashing might be the right thing to do (although maybe with better logging/error reporting) to tell people to set up `bitcoind` first. Alternatively we...

Generating such invoices securely will require BOLT12. Paying them should be easier but we have to see how the payment secret plays together with our current sending scheme.

Feels related to the module interconnect too, might be worth taking a look at that when building the API mock. https://github.com/fedimint/fedimint/blob/3c60fb65e58e11f2f7bf94c2920f9acace0e9d8c/fedimint-api/src/module/interconnect.rs#L5-L16

Stability on guardian set changes seems like premature optimization to me right now. There are still many things to figure out, adding one to the list won't hurt too much.

Right, one could also include the hash of the previous config. If you have the full config chain from genesis to current and each step is signed you know that...

There should probably be a check when generating config that you need `1msat` as a denomination since we assume that each amount can be constructed without change (so just having...

My initial concerns were unfounded as explained above, let's iterate on master.

We need to distinguish the trust model and how we distribute config. ## Trust model Users fundamentally have to trust the one who is giving them the join QR code...