elsirion
elsirion
tl;dr: this comment is only relevant in the Fedimint context. LND has an API call [`SendPaymentV2`](https://lightning.engineering/api-docs/api/lnd/router/send-payment-v2) that allows only supplying the amount, payment hash, destination and payment secret to make...
https://github.com/fedimint/fedimint/actions/runs/3953265674/attempts/1
https://github.com/fedimint/fedimint/actions/runs/4087609870/jobs/7048326190#step:5:7789
The trait still exists and isn't used anymore, good reminder.
No progress on a real TS/JS wrapper unfortunately, but @Kodylow built [`clientd`](https://github.com/fedimint/fedimint-clientd), which runs as a daemon and provides an API and comes with API wrappers for go, python and...
TODO, needs research for correct bounds and changes in a lot of other places to not accidentally break consensus. An easier first step would be to limit user input (e.g....
To which degree does this work now and how much is it tested? @m1sterc001guy @okjodom
@dpc I like that approach, we shouldn't worry about DynaFed for now imo. Not sure if we want more use of `threshold_crypto` for such things where we could use secp...
As discussed last Thursday: sending also isn't viable rn, since we can't enforce how much the GW actually sends when we leave routing to it. To enable amountless payments it...
I think we can close this as a duplicate of #559 since it seems like the only practical way of achieving proper amountless invoice payments and receives. Related technologies like...