pull down to refresh
0 sats \ 24 replies \ @siggy47 19 Aug \ parent \ on: SN release: Blink sending wallet, and fixes for LNC, profiles, invoice retries meta
That's what I'm thinking too. If we all keep trying different combinations maybe we'll hit the sweet spot. Do you think any type connection should give better performance than the others?
NWC probably has the best overall performance without a ton of other complications.
LNC has a bunch of limitations. LNBits requires a public ip and cert, and so on.
reply
It would be great if someone on SN would build a basic, secure, NWC connect wallet, like @supertestnet is doing. But, will NWC always require a fedimint/cashu type custodial mint?
reply
You should be able to run NWC on your node! Or you can use alby hub or something like that. It’s totally independent of ecash.
reply
Yes, I was talking to @ek about the problem I was having on Umbrel, using Oak node app, because Umbrel doesn't have https. I am starting a Start9 node, so I should be able to connect it there. I know there are a lot of Umbrel users, so I wonder if there is a workaround?
reply
I looked into the source code of Oak Node and I see how they appear to only generate a secret but I didn't really understand why or how that secret is supposed to get used.
I think we need to get a hold of someone from Oak Node to understand how they implemented NWC. I found out that ok300 is the Github account and they have a forum and ticket system at oak-node.net but I didn't create a ticket since I don't run it and thus don't feel like I have enough information.
Do you mind creating one in which you describe your problem in detail? They have anonymous login.
reply
Sure. I'll do that. In the meantime, I used the Alby Hub this morning and it was simple. They have a dedicated NWC app. For people running their own nodes, this is the much simpler way to go. Do you anticipate setting up NWC send and receive?
reply
Yeah, I am going to use Alby Hub to test my PR for NWC receive today. It already works, just need to add some checks so permissions to spend from your wallet don't accidentally land on the server.
It might also only work with Alby Hub since they are the only ones that allow to set permissions per connection. For example, cashu.me only allows a single connection and you can't set permissions. That's going to be annoying but we really want to keep spending permission away from the server. We'll have to bother the wallets to support multiple connections and restrictions if they don't yet.
reply
Yeah. That's important. It would kind of defeat the whole purpose 😀
NWC does not require a custodian. I opted for using custodians in Bankify because it's useful in some of my experiments and workshops to display a basic wallet interface that "just works" right away, with send and receive already enabled from the get-go, and an easy API to hook it up to some of my other apps (and third party apps like Stacker News). Ecash mints are probably the best available solution right now for that specific problem. But enabling NWC for more self custodial wallets is on my to-do list.