Olaoluwa Osuntokun
Olaoluwa Osuntokun
Pushed a major bug fix, discovered during interop testing: https://github.com/lightningnetwork/lnd/pull/10063/commits/7fa6395416391ee0b9d6bb59dba46b53660af87f
> Stating that payload comprises the remainder of the message directly conflicts with there possibly being an extension in addition to said payload Yeah I think the wording here is...
Will hold off on merging this for now. We're regrouping a bit re the parallel block download feature for `btcd`.
dust limit req: * actually need to accept a higher value now post anchor chans splicing: * eclair has done full cross compat w/ LDK * only missing RBF cross...
Seems that we should be examining our various BIP 173 implementations for spec compliance. There might be a gap in test vectors we can help to contribute here.
Moving payments over to a proper SQL schema will resolve this. Today if you do time based indexing for the command, it still scans every payment 1:1 (has to decode...
Can you also share your postgres config?
Is your start up time improved if you try out this config? https://gist.github.com/djkazic/526fa3e032aea9578997f88b45b91fb9
The issue is how we create the server dial opts in `oracle.go`: https://github.com/lightninglabs/taproot-assets/blob/8719b4035391bf2fda2430c5bd07907b4d638824/rfq/oracle.go#L124-L135 This should inherit `dialInsecure` from the earlier context.
> So, it seems you are only giving the option of ceil vs floor as a rounding technique, but why not also allow rounding up if greater or equal to...