Zaplocker.com: a non-custodial lightning address server (no node needed!)

Oh yeah and you can also use it so people can zap you at normal bitcoin addresses (no lightning wallet necessary) -- with no address reuse!

https://stacker.news/items/234331

Reply to this note

Please Login to reply.

Discussion

Check out the github for more info: https://github.com/supertestnet/zaplocker

Or try it out: https://zaplocker.com

do you need a master key on alby?

I don't know what that means

Interesting πŸ‘€

But I understand that there is a time limit to move sats from zaplocker to your wallet, right?

Yeah if you don't come get the money within 16 hours it returns to the sender

Also the address doesn't receive small amounts like zaps from 21 sats for example, right?

This is awesome, I’m gonna try it!

Also this might qualify for the HRF 2BTC bounty.

Well shoot.

Ok I think I fixed that error

The server was hanging because before giving out an invoice it queries mempool.space for the latest feerates and uses those to calculate minimum "receive" amounts

But I got rate-limited by mempool.space (I think) for querying for feerates too often, so the server would time out and give an error message, causing services to think it doesn't support lnurl

I changed the logic so it only queries mempool.space a maximum of once every 10 seconds

Try again and let me know if you encounter any more bugs

ιžδΏθ­·γƒ©γ‚€γƒˆγƒ‹γƒ³γ‚°γ‚’γƒ‰γƒ¬γ‚Ήγ‚΅γƒΌγƒγƒΌοΌˆγƒŽγƒΌγƒ‰δΈθ¦!οΌ‰

nostr:nevent1qqs2wzfg2qhngvr02nxn24y9ccqr487kgdrz9fy86nmj0wy2hp6cvdgpr4mhxue69uhhyetvv9ujumn0wd68ytnhd9ex2erwv46zu6ns4h9v48

I can't zap you! Getting an error but I can with everyone else (amethyst)

"Could not assemble lnurl from lightning address"

Ok I think I fixed that error

The server was hanging because before giving out an invoice it queries mempool.space for the latest feerates and uses those to calculate minimum "receive" amounts

But I got rate-limited by mempool.space (I think) for querying for feerates too often, so the server would time out and give an error message, causing services to think it doesn't support lnurl

I changed the logic so it only queries mempool.space a maximum of once every 10 seconds

Try again and let me know if you encounter any more bugs

I still have the error and can't zap you

What lightning address are you using?

I'm just using the zap button on amethyst. So it has to be your LN details setup on your profile

lol maybe I should upgrade my old zap lnurl to a zaplocker one!

Check out this dope noncustodial lightning address tool

nostr:note15uyjs5p0xscx74xdx42gt3sq820avs6xy2jg048hy7ug4wr4sc6s68qftu