pull down to refresh
383 sats \ 29 replies \ @siggy47 19 Aug \ parent \ on: SN release: Blink sending wallet, and fixes for LNC, profiles, invoice retries meta
Success! Damn, that was satisfying.
Wow with send and receive now active no longer need this hosted wallet!
reply
Congratulations!
reply
I feel oddly compelled to try as many wallet connections as possible
reply
The idea is if one fails we’ll try another, so not that odd.
reply
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?
reply
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?
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.
reply