10 sats \ 9 replies \ @k00b OP 17 Aug \ parent \ on: SN release: autowithdraw fixes. Trouble with attached wallets? Ask here! meta
It looks like it's charging SN to open a channel, but it might also be poor support for msats in lnbits. We are trying to pay you 2,762 sats and it wants us to pay 27,878 sats.
write
preview
0 sats \ 7 replies \ @fed 17 Aug
Shouldn't be a channel charge, that phoenixd instance got plenty inbound liquidity. Weird, it's like the invoice further multiplies the sats by a thousand before charging.
reply
103 sats \ 2 replies \ @k00b OP 17 Aug
It looks like lnbits doesn't support msats: https://github.com/lnbits/lnbits/issues/2009
reply
100 sats \ 1 reply \ @ek 17 Aug
The price needs to go higher for enough people to care about msats, lol
reply
0 sats \ 0 replies \ @k00b OP 17 Aug
I know, but the lightning specs are all in msats, so all these non-msat APIs will have to be rewritten eventually, and it's weird to have APIs acting like they're receiving direct user input.
reply
21 sats \ 2 replies \ @k00b OP 18 Aug
I've submitted a fix that doesn't use msats with lnbits. Let me know if that finally does the trick.
reply
1057 sats \ 1 reply \ @fed 18 Aug
I can confirm, auto withdrawal worked now. Thanks!
reply
0 sats \ 0 replies \ @k00b OP 18 Aug
Thanks for your patience/help troubleshooting!
reply
0 sats \ 0 replies \ @k00b OP 17 Aug
It'd be a pretty obvious msats/sats confusion if it were 1000x as much, but maybe it's doing something else funky. It works fine in our testing with lnd, but maybe phoenixd doesn't like msats.
I'll review this deeply tomorrow and see if there's something we can do.
reply
10 sats \ 0 replies \ @fed 17 Aug
deleted by author
reply