rich1.0MetropleX [GrapheneOS] ⚡🟣 (npub1gd…7cn8c)https://yabu.me/npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8cnjumphttps://yabu.meJust 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."