Even though Lightning payments are not publicly broadcasted and it’s not possible for a Lightning payment recipient to know which the initial channel in multi-hop route a payment came from, it’s always considered good privacy hygiene to first obfuscate your traces on the blockchain via mixing or self-sends before funding any Lightning channels. Ideally, we would like no one except ourselves to know the status of these coins. For added security, you can store the keys to your assets on a Trezor hardware wallet, making it easy to upgrade from one to the other if you decide to go pro. This way, you can also use MetaMask with a Ledger, which is the most well-known hardware wallet. Wasabi Wallet is designed to make you aware of which UTXOs you are using when you are making a transaction and it also allows you to see whether this is an output that’s been previously mixed or not, which can help you achieve your goal of privacy. A problem with the self-sending alternative when you are dealing with multiple UTXOs in your wallet is that you must weigh the advantage of the deniability you gain versus the disadvantage of consolidating outputs and thus losing privacy due to the common-input-ownership heuristic. If you absolutely cannot run a full node, an alternative approach may be to look up your address in a handful of different block explorers using the Tor browser. This will allow you to generate an address and validate that the bitcoins have arrived securely without searching for your address in a block explorer. Static donation address: Even if you use Wasabi Wallet and mix the coins you receive in CoinJoins and transmit your transactions via Tor, everyone who saw the address you provided will still be able to tell how many coins you received to that address, regardless of what you do with them after. However, if your work is controversial and risking exposing your identity via your IP address is unacceptable and you cannot trust a cloud provider to keep your details safe, then it’s probably better to receive donations to a static donation address. One way to send bitcoin, then, is to simply copy the recipient's address to your clipboard, then paste it in the send field of the Bitcoin wallet app you're using. While it is possible in theory to attain a relatively high degree of privacy using Bitcoin, there’s still a long way to go in terms of user-friendliness if this degree is to be accessible to everyone. First, we need to receive transactions continuously, so ideally we would have some way of obscuring the total aggregates of what we are receiving. You should now be able to browse to the explorer by IP address or domain name without the need for specifying the 3001 port any longer. Your responsibility will be to provide an address and assure yourself that the coins have arrived securely. Another problem with this approach is that if you chose to cloud deploy your BTCPay Server for the sake of convenience, the hosting provider will have the ability to learn about your Bitcoin addresses and your identity. And if you chose to self-host for this reason, although Tor support for BTCPay Server is being worked on, it’s still difficult to guarantee that you’ll be able to hide your server IP address from your visitors. Fresh addresses via BTCPay Server: Although BTCPay Server is fairly well-documented, not every writer is going to want to run a server just to receive donations. address wallet It’s built on the Lightning Network Daemon (lnd) which you can configure to run over Tor. Android users can use Orbit to allow their smartphones to communicate over the Tor network. Do we try to hide that there may be multiple Layer 2 networks you're interacting with and automatically try to use the best network for the task at hand? Further, keep in mind that while the deniability self-sends provide may give you an “out” in a working legal system as long as there’s no other evidence tying you to the transaction, a suspicious person might still place a high probability on that you were the sender of the subsequent payment and act accordingly. Further, each of the wallets currently supporting BIP47 are mobile wallets that leak your addresses to their back-end servers. For one, if a crypto exchange knows who you are (via “know your customer,” or KYC identification), they could pass that information along to law enforcement should they ever come knocking with a warrant. Say someone steals a large amount of bitcoin from an exchange.