Heads up: I might do some lightning node maintenance tomorrow. I'll pin a post about it before I do, if I do. It shouldn't be longer than 30 minutes but we'll see.

better attached wallet logs

@ek "supercharged" our attached wallet logs:
  • they update live as new logs come in
  • they capture more detail about failures
  • they have a warn log level (we'll be using log levels to derive wallet status soon)
  • log lines can be expanded to see payment/invoice details like the payment hash, preimage, etc

lnbits over tor and other tor for attached wallet improvements

@rblb added tor to sndev so we're able to troubleshoot wallet attachements that communicate over tor:
  • he added tor receive only support for lnbits
  • he reduced unnecessary outgoing tor proxy usage

bug fixes

  • hot sort in territories that didn't have many posts were displaying as if they were top sorted
  • zaps in rapid succession would occasionally conflict and pending zaps would be cancelled
  • device sync qr code scanning was broken
  • when a device was added to device sync, the device would need to refresh to see sync'd data
  • extraneous referrer notifications were being sent
  • changes to sending wallets from one tab were only showing after refresh in other tabs
  • blink attached wallet was broken
  • more but even more lame and unimportant


Since starting the Open Source Contributor Award Rules (OSCARs), we've paid a total of 13m sats to 31 contributors for 138 contributions! View an up to date list of contribution awards here: https://github.com/stackernews/stacker.news/blob/master/awards.csv

Previous release: #753592

350 sats \ 1 reply \ @Bee_Aye 10 Nov
nice job, i successfully sent and received using lnbits over tor 🤙
reply
0 sats \ 0 replies \ @ek 10 Nov
Thanks for letting us know!
reply
490 sats \ 3 replies \ @ek 9 Nov
LFG 👀
As you can see, you can now see when your wallet was used to request invoices unlike before. This means someone wanted to zap you.
Apparently, someone wanted to zap me but they didn't pay yet. It should show when a payment was received or if the invoice was canceled/expired.
reply
27 sats \ 2 replies \ @ek 9 Nov
reply
106 sats \ 1 reply \ @k00b OP 9 Nov
Looks like there's a rounding inconsistency 179 sats -> 180 sats on receive.
reply
134 sats \ 0 replies \ @ek 9 Nov
oh, you're right
edit: I think I'm accidentally adding the routing fee to received
reply
more but even more lame and unimportant
🤣
reply
Now it is really easier to attach an external wallet but there is always a problem when it comes to floor operations or even rounding of msats. I hope you can sort it out soon.
reply
20 sats \ 0 replies \ @ek 10 Nov
there's nothing we can do when your wallet doesn't accept invoices in millisats. most wallets don't seem to.
reply
Those aren’t a problem per se. It’s just us letting you know that your wallet doesn’t support fractions of a sat. If you’re cool with us keeping the fractions of a sat, you can ignore those messages.
reply
0 sats \ 0 replies \ @nym 10 Nov
Nice updates!
reply
I love the Open Source Contributor Award Rules (OSCARs)! Great innovation and creative thoughts. It’s been an interesting last year here. I hope adoption continues and big guests keep dropping by for AMA’s!
reply
10 sats \ 1 reply \ @nym 10 Nov
I haven’t heard about this before.
reply
Yeah looks cool. Lots of stackers here have got in the mix! https://github.com/stackernews/stacker.news/blob/master/awards.csv
reply