dstadulis
dstadulis
Revolves around manageutxo
Capturing root-cause analysis comments https://github.com/lightningnetwork/lnd/blob/f7b74426808c0305eb594bb0addbf4c1c035d9cd/lnrpc/invoicesrpc/addinvoice.go#L695 Initial assessment: >lnd would use the amt to decide what to place in the hop hint (most MPP), but maybe we had a regression there...
might need to extend unit test frame work
Ready for deployment modulo ~~when the subasta PR is merged.~~ Do not deploy until then Requirements for merge: - deploy the server side - gated by lnd 0.15.1 to certify...
⚠️ PR will need to go back to sprint as changes have been made to MuSig2 spec regarding x-only keys Deliverable outcome: - [ ] Modify the implemented MuSig2 spec...
Agree that versioning should be incorporated here to facilitate it being upgraded. Appears there was some misinterpretation about the code etc constrained/delayed by MuSig2 spec, which won't be the plan.
Fun idea! I'm envisioning something like "Click here to send a `$ pool order submit bid --allowed_node_id 021c97a90a411ff2b10dc2a8e32de2f29d2fa49d41bfbb52bd416e460db0747d0d` to your node over Lightning-Node Connect lnc-web" https://docs.lightning.engineering/lightning-network-tools/pool/orders#match-with-specific-nodes Brought this up with...
a more user intelligible description would improve the UX. Agree that the error message isn't great, most of it isn't high signal Suggested alternative: "Unable to submit order: Account needs...
after we get ZC and unannounced channels merged, we'll need 2x review on this with Roas to cap it out
Can we keep track of the output we are tracking in order to observe the fee? If we can't track this, then the delta wouldn't be able to be calculate....