Zaps are super cool, but come on guys let's do it properly.

Down with custodial wallets!

Reply to this note

Please Login to reply.

Discussion

Whats an equally easy to WOS setup non-custodial option?

Phoenix

How do I get a LN address with Phoenix?

You can't. You can pay to other LN address though.

Thanks for confirming.

Is there an easy non-custodial solution that let’s you generate a LN address (like WOS) and lets you easily zap (like Phoenix)?

Not that I'm aware of mate.

#[5] opportunity for mutiny wallet:

Grandma mode ez non-custodial wallet with LN address

The web server is the difficult bit. Not sure mutiny could fix that in a sovereign manner for the user.

Is the webserver the bit that “hosts” the LN address, and listens for zaps?

Over simplifying here , but it basically listens for web requests name@domain.com and then pings your node for an invoice to pass to the payer

I'm zapping here from OBW! Doing my part, but we still don't have non custodial equivalent to lightning address, right?

Yeah, mines non custodial running on a node at home.

I’ve got a non-custodial LN node at home but the problem imo is LNURL seems difficult. Is there a better way?

Yeah that's the hacky part. I run BTCPay on the node at home with LN address enabled, then expose the onion version of it via a cheap Lunanode VPS so people can reach via clearnet to pay qna@tips.bitcoiner.guide.

It's by no means easy or foolproof, but gets the job done in a sovereign and inexpensive manner.

Here's a guide

https://docs.btcpayserver.org/Deployment/ReverseProxyToTor/

Thanks, I’ll check it out.

DM if you need support

Unfor we don't. But decentralization of custodial services is not too bad either. When balances are sub 50ksat?

Non custodial would be better, so I'm hoping for some form of async lightning payments.

Afaik AMP enables something similar, BOLT12 was another option, there may be something with trampolines...

Bolt12 would be lovely.

I think #[6] stated previously that once there’s an actual spec for BOLT12, NIP-57 will be extended to work with those.

Would be much better than running an LNURL server.

Agreed!

Zaps inherently have centralizing effects

One reason is receiver nodes are easy to DDoS: #[0]

What would you change about their design?

Top three:

- use a different protocol than LNURL, or at least make it backeward compatible w. LNURL

- do not keep state on the reciever (instead, push from sender when payment is done)

- make it less about sats and more about PoW (cannot be fakked, cannot be wash-zapped, can be bought w. sats for low power devices where PoW is unfeasable)

1 and 2 will soon be technically trivial, with LN SDKs making it easier for apps to natively integrate LN (access to preimage, LNURL primitives, etc -- without switching apps).

Appreciate the insight

I've been zapping with Alby on browser and Phoenix on mobile.

Alby connected to your own node? 😎

Yes but I ran over tor and it didn’t work.

Anyone tried #[2] solution for receiving lightning to email?

https://bridgeaddr.fiatjaf.com/

Nope, there's a few similar services knockong about though.