Oddbean

the reality is that almost everybody uses custodial LN addresses because the requirements are so large; even the vast majority of the technically-competent end up in custodial LN so if we're going with a custodial model why not just use a faster and cheaper model? mind you, you can still run your own ecash mint and run fully self-sovereign

There will be a better solutions than ecash. Regarding custodial wallets vs ecash yes it might slightly be better but you can be rugged much more harder with mints vs let’s say one known custodial wallet like WoS lets say. “Run your own ecash mint” the same questions can be why don’t you run just a lightning node 🤷‍♂️

> Regarding custodial wallets vs ecash yes it might slightly be better but you can be rugged much more harder with mints vs let’s say one known custodial wallet like WoS lets say. why? it's the *exact* same trust model > “Run your own ecash mint” the same questions can be why don’t you run just a lightning node 🤷‍♂️ sure, but people don't, so if it's going to be custodial, why not just go with something that is far cheaper, faster and more reliable?

Why? Because there will be a lot of scam mints vs few custodial wallets that’s been in this space for a while. Sure, it’s better faster and more reliable but why not to focus on building something that can do the same but without having a trust model? Isn’t Satoshi created bitcoin to eliminate third parties ?!

Hold up, this isn't correct. A mint cannot rug you as easily as a custodial LN wallet. With custodial lightning, you're an entry in their DB. They can single you out, deplatform, and/or censor you. A mint cannot do this. A mint can't rug individuals, it's all or nothing. They rug everyone or no one. The reputational cost is vastly different.

The main problem for technically-competent users who run a home node is bypassing the home NAT and configuring a domain, because Tor is unstable and many smartphone wallets don’t support .onion addresses. That’s why we need http-over-nostr and lnurls/lightning-addresses that encode “.nostr” domains: https://vimeo.com/950881613 https://github.com/nostr-protocol/nips/issues/1276

Interesting, but doesn’t this need some centralized coordinator to match the clients to the servers (via the “connector” string)? What happens if I try running a server with the same connector string as someone else? Is it encrypted? The lnurl/lightning-address protocols are based on small json payloads. It will be simple for every smartphone wallet to send them as “nostr dms” (with a different ephemeral kind), it will be encrypted, and will also be reliable if you use multiple relays.

How? When I type “holesail holesailMCServer420” and then send a GET request to localhost:8989, how does it find the ip address of the server that used the same connector? Also, can the connector be a public-private keypair or a string/string-hash pair? Because I want others to send requests to my server without being able to try taking over other peoples’ the requests.

When you do holesail CONNECTOR, it generates a hash that is also your location in the distributed hash table, atm there are two public nodes run by hopepunch team which lets you in on the mesh network of peers. Anyone can run a public nodes, and it's only used for initially finding first few peers after that other peers tell you where your "peer" is located. To stop people from taking over, you need to use key, which are automatically generated. holesail --live 5000 will give you a key

Would be really cool to have an @umbrel app that creates reverse-proxy to the LNBits app, and some instruction how to build a project on Vercel or Firebase with a lambda function that forwards every request to your home LNBits. The major pain with LNBits behind NAT is to actually let others use it outside your home WIFI.