joschisan
joschisan
The only latency critical items we had / still have are signature shares, which is a strongly discouraged pattern since it’s very wasteful with respect to disk and compute consumption...
In my opinion https://github.com/fedimint/fedimint/pull/4766 is already quite complex; this pr is not worth the complexity imo, the mutex logic is hard to follow.
@m1sterc001guy with Pay-To-Pubkey I assume you mean receiving to someone else's pub key? If so that does not need to be tested separately as every regular receive is just a...
When you add a new parameter to the config you either have to set a default value or we need to do it manually when migrating to 0.4. I don't...
I see a few problems with this with respect to bandwidth and DOS. I have thought about it quite a bit and left it to the integrators for those reasons....
@elsirion what do you mean by offers?
This does not require consensus version votes, merely one additional consensus item and input variant.
This is resolved and will be shipped in 0.6. No It will not be possible to exceed the limit anymore as the only information included in the Fedimint transaction is...
Lnv2 fixes this.
A few comments: The history of transaction data should include the time it took to send the lightning payment. We need to track this to ensure our lightning source works...