SN release: NWC & LNBits for sending, LND for autowithdraw, NSFW labels, & more
13.1k sats \ 104 comments \ @k00b 13 Feb meta
zaps forwarded to @btcbagehot (10%) @ek (70%) @mz (20%)

moar wallet attachments
sending with NWC and LNBits
You can attach wallets for sending now via @ekzyis. To start we support attaching Nostr Wallet Connect and LNBits. @ekzyis did a lot of work to make the UX as close to familiar as possible and I think it's stellar.
Note: The credentials are stored in the browser, so please set a budget on them. @ekzyis took a lot of care making the browser as safe as we can for storing these, but you'll want to be extra careful anyway.
autowithdraw to LND
In addition to autowithdrawing to a lightning address, you can now autowithdraw to LND. We support connecting to your node over Tor so you should be able to push out funds to your home node even if it doesn't have a public IP.
If you attach LND in addition to a lightning address, you can set a default and if it fails we attempt your other method.
expect more methods soon
There are a lot of wallets and ways to connect them, but we plan to support any method that makes sense as time goes on. We'll likely be adding CLN and Zebedee next.

NSFW territory labels
🚨 first time contributor alert
Territories can now be labelled NSFW and are visible on an opt-in basis unless visited directly via @mz.

improvements to domain searching
🚨 first time contributor alert
When you search with a url:example.com filter you should see less strict results via @btcbagehot.

bug fixes
  • wonky checkboxes on territory form via @mz
  • pinned posts now really do show up in home via @ekzyis

what's next
  • we have a nearly done nostr crossposting PR via @bitcoinplebdev that allows you to crosspost all post types and will likely be merged soon
  • a variety of territory enhancements
    • @mz is working on a top for territories
    • @byoungdale has a draft going for crossposting
    • I'll work on changing the territory billing period here shortly then sub-territories (unless someone beats me to either)
  • more thorough bolt11 deletion via @dillon will be merged soon
  • lots of random stuff I'm sure
Happy Valentine's!
write
preview
related posts
1891 sats \ 5 replies \ @nout 14 Feb
This could use a short video with a demo! It's hard to understand what is NWC and how does it relate to SN.
reply
217 sats \ 0 replies \ @k00b OP 14 Feb
I agree! We'll probably need docs for all of this. When I shared our plans for the wallet, @moneyball astutely noted how overwhelming it would be to the average person.
So we'll also want a "wizard" like experience at some point, eg "do you know the difference between custodial and non-custodial?" if yes then "do you run a node?" then "does it have a public IP address?" and so on.
Regardless, we can't expect the average person to stand for that kind of torture so we have a lower friction onramp planned where an attached wallet isn't necessary.
reply
217 sats \ 2 replies \ @ek fwd 14 Feb
Oh, great idea! I'll do one with Mutiny and share it here.1
We also thought about having specific cards for wallets which link to the same setup page if they use the same protocol (like NWC here) but include specific setup guides for these wallets. We could add videos together with some screenshots then there, too :)
Footnotes
  1. Great use case for pinned comments? 👀 ↩
reply
0 sats \ 1 reply \ @ek fwd 17 Feb
I'll do one with Alby and Mutiny when we deployed this fix: Fix NWC support detection
reply
0 sats \ 0 replies \ @k00b OP 17 Feb
deployed
reply
0 sats \ 0 replies \ @ek fwd 17 Feb
Created one now in #428781
reply
612 sats \ 1 reply \ @leo 14 Feb
Very cool! How come some options are either send OR receive? Couldn't LNbits or LND Accounts (over LNC) be both?
reply
30 sats \ 0 replies \ @k00b OP 14 Feb
Yes! We just need to tease apart permissions so we’re not storing spending perms on the server (without them being encrypted) but still have perms to generate invoices on the server.
We’ll iterate to these “duplex” permissions eventually.
reply
1210 sats \ 2 replies \ @benthecarman 13 Feb
Mine is stuck on this red light
reply
859 sats \ 1 reply \ @k00b OP 13 Feb
NWC? I don't think we validate the string yet (PR pending). Console say anything interesting?
reply
0 sats \ 0 replies \ @benthecarman 14 Feb
Yeah for nwc, console didn't have any logs
reply
1979 sats \ 0 replies \ @TheWildHustle 13 Feb
Great updates, auto-withdraw to LND and adding NWC is pretty wild.......
reply
1254 sats \ 2 replies \ @BitByBit21 13 Feb
Great work guys, you're shipping awesome features! I intend to attach my LND and my LNBits. Wondering why it is "non-custodialish"...
reply
21 sats \ 1 reply \ @ek fwd 13 Feb
If it's non-custodial depends on what LNbits or NWC provider you use.
You could be using https://legend.lnbits.com for example or Alby with NWC but in a custodial way.
It's just possible to use it non-custodial.
reply
937 sats \ 0 replies \ @BitByBit21 13 Feb
Oh, I get it. I'll be using it from my Umbrel node.
reply
2036 sats \ 19 replies \ @TonyGiorgio 13 Feb
NWC! LFG. Will set that up with Mutiny tonight to see how it goes. Very nice work!
reply
3366 sats \ 18 replies \ @TonyGiorgio 13 Feb
A few of them have gone through but hard to tell if it's being slow on the SN side or on the Mutiny side. Perhaps someone with alby or lnbits could test out too to see how it goes.
The comments are kind of painful to sit there and wait for. I wish it could just act like it went through but have some pending UI for it.
reply
859 sats \ 0 replies \ @k00b OP 13 Feb
It could b because we poll on the client for the invoice being paid which probably adds 500ms of latency on average.
Great feedback.
reply
0 sats \ 10 replies \ @saunter 13 Feb
Unfortunately doesn't work for both self-custodial NWC app and Alby hosted NWC
reply
0 sats \ 9 replies \ @k00b OP 13 Feb
It's meant to work. We probably have a bug.
What errors are you getting in your console?
reply
3234 sats \ 8 replies \ @saunter 13 Feb
Uncaught (in promise) EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules'".
at bakeCollection (content.7f229555.js:2064:98610)
at Object.u (content.7f229555.js:2064:93234)
at Object.g [as call] (content.7f229555.js:2064:93437)
at es.o [as emit] (content.7f229555.js:2064:85238)
at es.stop (content.7f229555.js:17:30157)
at es.eoseReceived (content.7f229555.js:17:31755)
at content.7f229555.js:17:8787
at Array.forEach (<anonymous>)
at T.eoseReceived (content.7f229555.js:17:8754)
at content.7f229555.js:17:11970
reply
0 sats \ 7 replies \ @k00b OP 13 Feb
@ekzyis looks like the nostr library violates CSP
reply
0 sats \ 6 replies \ @ek fwd 13 Feb
Mhh, interesting, I tested NWC when we launched and I could generate NWC requests 🤔
reply
0 sats \ 5 replies \ @k00b OP 13 Feb
I think it might be that the library uses wasm, some browsers probably don't support it, and we allow unsafe-eval-wasm but not unsafe-eval
view replies
0 sats \ 5 replies \ @ek fwd 13 Feb
hard to tell if it's being slow on the SN side or on the Mutiny side.
We poll every second if the invoice was paid, so some slowness is definitely on our side.
The comments are kind of painful to sit there and wait for. I wish it could just act like it went through but have some pending UI for it.
What do you mean? You should see toasts that show if payments are pending.
update: Oh, you mean the toasts in the right bottom corner with comments? no, Tony didn't.
Perhaps someone with alby or lnbits could test out too to see how it goes.
Tested with LNbits: lnbits_zap.mp4
reply
1010 sats \ 1 reply \ @TonyGiorgio 13 Feb
Comment box just sits there if a payment was needed for a reply
reply
0 sats \ 0 replies \ @ek fwd 13 Feb
Ah, I see. You literally meant "comments" with comments, haha. Makes sense!
reply
453 sats \ 2 replies \ @k00b OP 13 Feb
He means to just post it optimistically, storing it on backend like a "draft" until it succeeds, which is closer to the ideal (we "absorb" the wait for them). For "failed drafts," we'll probably want to send them a notification. For "successful drafts" we'd do nothing and yay.
reply
937 sats \ 0 replies \ @nout 14 Feb
Yay for optimistic UX. Great latency saver...
reply
0 sats \ 0 replies \ @ek fwd 13 Feb
but have some pending UI for it.
We could style the text with text-muted while the payment is pending
reply
1037 sats \ 0 replies \ @saunter 13 Feb
If anyone wants to learn about NWC, add it to your website or contribute, there's a fresh website: https://nwc.dev/
We also started a Discord for builders integrating NWC (apps and wallets). Join us here: https://discord.gg/PS7EhpyF
reply
937 sats \ 0 replies \ @anon 13 Feb
Can yall build NWC into LNbits though. That is the question 😅
reply
457 sats \ 8 replies \ @ek fwd 17 Feb
This video demonstrates how to connect your Mutiny or Alby wallet via NWC with SN:
https://files.ekzyis.com/public/sn/sn_nwc_tutorial.mp4
It should work with any wallet that supports NWC though. Paste the connection string that starts with nostr+walletconnect:// into the NWC input here and you should be good to go!
reply
0 sats \ 7 replies \ @nout 17 Feb
Super cool! Yeah, I'd say it would be better to switch to optimistic UX - just make it look like it's been zapped immediately and only pop up any dialog when the payment actually fails (it could also just be a SN notification).
reply
0 sats \ 6 replies \ @k00b OP 17 Feb
We're going to house an abort button on the toast eventually, but should probably make it lower contrast than it currently is.
reply
0 sats \ 5 replies \ @nout 17 Feb
I guess my question is why is the toast even needed in the success case? Why should user care? In the nostr apps that use NWC the status of the lightning icon just updates...
reply
0 sats \ 1 reply \ @ek fwd 17 Feb
I think the main issue is the blocking nature on anything that does not use the default zap, no? So if you comment, post or even just select a custom amount, the UI currently blocks until the payment failed or was successful.
If that's true, the toast isn't the problem afaict. As @k00b mentioned, it only exists so one can cancel pending payments.
In the nostr apps that use NWC the status of the lightning icon just updates...
You mean like showing a spinner instead of the lightning icon? Mhh, I see. Maybe we can do that instead of toasts and clicking the spinner would cancel the action. But that's a bigger lift, not sure if it's worth it if the toast is not the real problem.
reply
0 sats \ 0 replies \ @k00b OP 17 Feb
The toast is easy to remove in cases where we don't want it so I wouldn't overthink that part yet. The hard part will be optimistic actions.
reply
0 sats \ 2 replies \ @k00b OP 17 Feb
They accidentally zapped and want to abort the payment. You've expressed wanting to abort custodial zaps in the past (which we are also working on). Have your feelings around that changed or did you have something else in mind?
reply
3524 sats \ 1 reply \ @nout 17 Feb
Yeah, you are right and I'm sorry for pulling you back and forth on this. Cancellation is a fair counter point. Please take my inputs just as hopefully constructive feedback / brainstorming. I'm likely to be wrong on stuff...
I think the cancellation is a bit separate problem from the zapping solution itself.
  • zapping:
    • internal wallet zap (no latency, low chance of error)
    • connected wallet zap (medium to high latency, has a chance of error)
  • cancellation:
    • removing / cancelling the "WoT" vote
    • getting sats back on accidental click/zap (see below, I think this one is not that important)
Zapping
Just brainstorming, but what about behavior like this that's the same for both internal and connected wallet:
  1. when user clicks on lightning, then the lightning icon keeps "pulsing" (some animation) until confirmed. And maybe when confirmed you do the fullpage lightning animation?
  2. when confirmed it turns yellow (or whatever the final color).
  3. when there's error/timeout, then show toast with actionable button(s) that allow the user to "try again" or "debug" (or something like that).
When zapping with internal wallet, user only sees (2) or (3)
Cancelation
The main issue I hit was that I clicked/tapped by accident on lightning when I didn't mean to. I don't mind losing the sats since that was my mistake (i.e. fair game), but I'm mainly worried about providing a wrong signal to the system and sorting that post higher (even when I don't like it). So the one solution idea that would resolve my issue would be if the post tripledot menu had "Cancel upvote (leave sats)" or perhaps for plus points, but really low priority: when the icon is still "pulsing" (= unconfirmed), I can tap&hold and in the dialog there could be option to cancel?
reply
0 sats \ 0 replies \ @k00b OP 17 Feb
Interesting and helpful as usual.
Sounds like there's a principle in there: don't do a toast/popover for frequent actions if you can avoid it. Toasts are a sledgehammer and we can probably find a better, more specific tool for the job.
reply
367 sats \ 0 replies \ @Eobard 13 Feb
gj ek
reply
248 sats \ 1 reply \ @ek fwd 13 Feb
We also allow 50 MB free images per stacker per day now. Before, it was 10 MB per day.
/cc @Natalia 👀
reply
1 sat \ 0 replies \ @Natalia 14 Feb
oh let me test it 👀
reply
503 sats \ 0 replies \ @sn 13 Feb
You can attach wallets for sending now
👀
reply
200 sats \ 0 replies \ @WeAreAllSatoshi 13 Feb
Oops, I guess I did a soft reveal of the new contributors the other day. Welcome to the club!
reply
0 sats \ 9 replies \ @Design_r 30 Apr
Howdy @k00b @ek I am having some issue attaching my CLN node via Tor and getting the following error:
------ start of logs ------
1s	[cln]	ERROR	could not connect to CLN: request to https:/xxx.onion:2100/v1/invoice failed, reason: getaddrinfo ENOTFOUND xxx.onion
1s	[cln]	ERROR	failed to attach wallet
Look's by default is looking to https connection. I tried to use http:// when inserting the rest host and port without success. There's any configuration I need to set in my node to enable HTTPS connection via tor? or can I somehow enable the connection via http?
reply
0 sats \ 8 replies \ @ek fwd 30 Apr
It's a known bug. We're enforcing HTTPS even for Tor in the backend but this breaks how our Tor name resolution works. I'll fix it today.
reply
0 sats \ 6 replies \ @Design_r 5 May
@ek, have noticed the issues 1107, 1136 and 1133 have been merged but still getting the same error. Anything I need to do differently?
reply
20 sats \ 5 replies \ @k00b OP 5 May
They haven't been deployed yet. I'll deploy them tomorrow.
If you're ever curious what version we're on you can click the running XXXXXX in the footer.
reply
218 sats \ 3 replies \ @Design_r 7 May
Not sure why it still give me error:
could not connect to CLN: invalid json response body at 
http://xxx.onion:2100/v1/invoice reason: Unexpected token < in JSON at position 0
failed to attach wallet
I also tried to use the one in position 0 and the input validation obviously give back rune must be restricted to method=invoice only
anything else I could try?
reply
0 sats \ 2 replies \ @k00b OP 7 May
That error is pretty vague sadly so I can’t tell what’s wrong. I’ll put up an issue on GitHub
reply
0 sats \ 1 reply \ @Design_r 7 May
Look's is looking only at the rune in position 0 in the JSON. There's maybe a way to define the rune position in the form? Or maybe having the script to look at all runes in the file for a match? Just ideas...
reply
0 sats \ 0 replies \ @k00b OP 7 May
This isn’t about the rune. We reach your node but it’s not returning json.
reply on another page
0 sats \ 0 replies \ @Design_r 5 May
amazing, thanks for the update. I'll try again tomorrow.
reply
0 sats \ 0 replies \ @Design_r 30 Apr
Thanks much appreciated
reply
0 sats \ 0 replies \ @justBrian 18 Feb
a cool feature,btw would be to set withdrawals to your node happen randomly for random intervals of sats and maybe randomly in time...make it hard to papertrail sats you are zapped on here and where they go.. just a cool idea obviously not needed.
for example set so a third of my stacker news wallet gets withdrawn at a random time every 7 days to my lnd node.
reply
0 sats \ 2 replies \ @RocketNode 14 Feb
Why does attaching LND need address and onchain permission macaroons? https://github.com/stackernews/stacker.news/blob/master/lib/macaroon.js#L61
Shouldn't invoice:write be sufficient for auto withdrawls?
reply
0 sats \ 1 reply \ @k00b OP 14 Feb
It doesn't need them, but I didn't anticipate people baking their own macaroons with granular perms. I assumed people would use the default macaroons.
If you wouldn't mind opening an issue I can narrow the perm check.
reply
1468 sats \ 0 replies \ @RocketNode 14 Feb
https://github.com/stackernews/stacker.news/issues/827
reply
0 sats \ 1 reply \ @cryotosensei 14 Feb
Erm what’s a Nostr Wallet Connect?
reply
412 sats \ 0 replies \ @BitByBit21 14 Feb
Nostr Wallet Connect (NWC) is a way for applications like Nostr clients to access a remote Lightning wallet through a standardized protocol. For instance, you can link your Alby account with any other application using this feature.
https://nwc.getalby.com/about
reply
0 sats \ 1 reply \ @JuanMiguel 14 Feb
Can someone explain what NWC is and how it works?
reply
0 sats \ 0 replies \ @BitByBit21 14 Feb
See my answer to the comment above from cryotosensei
reply
0 sats \ 2 replies \ @justBrian 14 Feb
Cant get nwc to work with my start9 nwc connection FYI.. shows red light
reply
0 sats \ 1 reply \ @k00b OP 14 Feb
What browser?
reply
166 sats \ 0 replies \ @justBrian 14 Feb
I tried with vanadium and Mozilla on graphene OS
reply
0 sats \ 10 replies \ @sudocarlos 14 Feb
Why am i seeing a red status indicator. I'm using NWC on Start9
reply
42 sats \ 9 replies \ @k00b OP 14 Feb
Mind checking your console for errors and sharing which browser you're using?
Some browsers don't like some of the security settings we are asking it to enforce.
reply
2255 sats \ 6 replies \ @sudocarlos 14 Feb
iOS 17.3.1 - Safari (PWA). Not sure if my string is good: nostr+walletconnect://<long-alphanumeric-string>?relay=wss://relay.getalby.com/v1&secret=<secretstring>
reply
42 sats \ 5 replies \ @k00b OP 14 Feb
The string might be bad. We don't validate it to check. I'll run some more tests in all the problem browsers tomorrow and see if I can fix it.
reply
987 sats \ 4 replies \ @ek fwd 14 Feb
Going to add the validation tomorrow.
However, there should be a toast with some error message if the credentials are no good1:
The form also shouldn't close if the info event wasn't found. And if it was found, the wallet indicator should turn green.
But maybe the error is CSP + browser combination again which throws an error at a location which isn't toasted.
Footnotes
  1. That check only verifies everything up to but not including the secret since a correct secret is not required to receive the info event unfortunately. ↩
reply
0 sats \ 3 replies \ @sudocarlos 14 Feb
CSP?
reply
42 sats \ 2 replies \ @ek fwd 14 Feb
Oh, sorry, I mean Content Security Policy. This is supposed to tell your browser what code is good to run and which should get blocked. It might be blocking too much depending on the browser.
reply
0 sats \ 1 reply \ @sudocarlos 14 Feb
Gotcha. Also, shouldn't it say "detach" instead of "unattach"? It's your app, but feels more natural
view replies
0 sats \ 1 reply \ @sudocarlos 14 Feb
Is there a way to see console data on ios without connecting to a mac/xcode?
reply
42 sats \ 0 replies \ @k00b OP 14 Feb
No it has to be connected to a Mac afaik.
reply
0 sats \ 1 reply \ @justBrian 26 Feb freebie
any update on improvements on connecting things like ln address or lnd node over tor to receive auto withdrawals? happy to help test when you need it 🤙
0 sats \ 18 replies \ @justBrian 18 Feb freebie
i am trying to link up my lnd node running on start9.. i keep getting "invalid input" for my cert.. im copying it from node properties page and have successfully used it for linking up with alby, so i am pretty sure i have the cert right. seems to just not be accepting the cert.. anyone else ran into this issue?