Nice. Would love to hear your thoughts on #payjoin.
nostr:note1008vxrz9xx0eptz79zp5j4ymzj0n4r2dn57nvqdcu8u50lrevwgszqx3qn
I've run my own #btcpay instance for several years (non-docker, not recommended in their documentation). I use it to receive Zaps for this #Nostr account without depending on a 3rd party. It can also be used to receive #payjoin payments although with recent developments btcpay will no longer be the only way to do that.
It is a nice Swiss Army Knife for on chain and lightning similar to what nostr:nprofile1qqs8u5uf0rd2p9wmdxxaznpn54tkq8wwspmljy0cjqw6jdgm5kv84dspp4mhxue69uhkummn9ekx7mq20qgpe has become but more geared toward receiving payments. I highly recommend it.
Discussion
It is pretty cool to look at a #payjoin transaction with a block explorer and see that it completely breaks the "common input ownership heuristic". When I setup my #btcpay server I tested it with Wasabi which was one of the wallets that supported payjoin sending at the time (there are quite a few wallets that support payjoin send now). It works but of course with payjoin v1 you need to have a publicly accessible btcpay server to receive. The new payjoin v2 sounds like it's much more accessible for non-server runners to be receivers.