Just so everyone knows, you've all played your part in helping me encourage adoption and implementation of lightning as a dedicated donation channel for the project.

The following is an official project statement:

"We're in the process of determining the best way for us to host an always-on local Lightning node with a WireGuard tunnel from a cloud server. We also need to figure out hosting lnurl so that people can actually use it.

It's likely we'd get a lot more small Bitcoin donations if we added Lightning to avoid high fees and also for better privacy. We plan to do this, but it's quite difficult to do it properly without a custodial service or complex software that's likely not going to be reliable.

Most people are experiencing Lightning via custodial services or non-custodial wallets using lnd + neutrino with a focus on sending rather than receiving payments. Receiving is harder than sending with Lightning and we need it to be secure, robust and reliable which is also hard.

We need to have proper backups, etc. We could end up in a similar situation to the one we're having with PayPal if we set up Lightning poorly by using a custodial service or use software/hardware which ends up failing and doesn't have proper backups for the money in channels.

We don't see much point in using Lightning unless we're running our own Lightning node on top of a Bitcode full node with local hardware and proper backups. We want to do it but it's not easy to do it the way we want. We aren't simply going to deploy someone's Docker images, etc.

We run Bitcoin and Monero full nodes without pruning for use with our hardware wallet but we don't do it for other cryptocurrencies and it's not a serious deployment usable for anything public. Making a serious Lightning node is something entirely separate from what we have."

Reply to this note

Please Login to reply.

Discussion

Wish you the best! :)

May be worth checking out github.com/fort-nix/nix-bitcoin for stability and reproducibility

i think nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll lightning node could be a good option.

they are open source, and have a insanely good dev team.

Wishing you best.

Also the point of 'Sending bitcoin on lightning is much easier than receiving (non-custodial) is very true.

I tried with my owm website and didn't found a good solution.

Hoping people like nostr:npub1trr5r2nrpsk6xkjk5a7p6pfcryyt6yzsflwjmz6r7uj7lfkjxxtq78hdpu, nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx etc. are already looking into funding some projects which helps in receiving lightning bitcoin easier.

I will admit, I am tired and did not read the whole post...

I have made a lot of experience with Core Lightning (aka. C-Lightning, CLN). And after that, I recommend you invest time in looking into LND, a Go implementation that seems to be much more feature complete and offers additional functions that CLN does not.

As for lnurl - that should be just a plugin away that exposes a basic HTTP server. In order to set up a Lightning Address... Well, code speaks more than words:

-- Caddy:

zaps.birb.it {

reverse_proxy localhost:9876

}

birb.it {

handle /.well-known/lnurlp/ingwie {

redir https://zaps.birb.it/lnurl

}

}

--

And this should cover most to all the LNURL setup.

Since this is ment for donations, I don't think you need to set up #Nostr zapping (you need a plugin to publish the zap events). And as for wallet solutions, LNDHub seems to be good as well as LNConnect. Though, both use LND, hence my lack of experience there.

Hope this helps!

(PS. Nostr really needs markdown support... sorry if the Caddyfile snippet is ugly as heck. xD)

This is the way.

if donations were via nostr so that the lnurl can be dynamically updated and you regularly withdraw bitcoin i dont think custodial is a large risk, aswell ln providers are very maximal freedom