elsirion
elsirion
Ideally with the new LN client code we can just make the user buy the preimage directly from the federation if the route hint is a GW of the federation....
I think we can close this now that we have the operation log.
> @elsirion: remind me what the problem was with having the gateway sign BOLT12 invoices instead of the federation? You'd trust the GW to set the same required amount in...
**tj;dr:** *It's a very similar problem to why amountless invoices were broken in the early days.* @TheBlueMatt Let's simplify a bit, for this case we can think of the recipient...
But why do offers at all then? I always thought having the option of recurring payments was the point of adding an additional round to the payment protocol. It's one...
I have a similar problem: `bitcoind` crashes from time to time (unreliable fs cache, need to fix) and `clightning` stops but starts again, but `clightning-rest`, `rtl` and `spark-wallet` stay in...
Likely related to https://github.com/fedimint/fedimint/issues/3826#issuecomment-1904679332
I ran int the same issue and was able to reproduce the problem in your `idb` test suite by adding some sleeps: ``` panicked at 'id should be ok: failed...
Yeah, it's not a bug in this crate, just insane semantics of IndexedDB transactions :cry: My best bet is probably to build an ACID-compliant transaction abstraction on top and then...
> This ticket is about Rust Futures being inherently incompatible with indexeddb API. I agree, given the lack of guarantees about rust future execution and the IndexedDB behavior I don't...