It was too easy to get a nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg dev environment running. I thought bitcoin/rust/wasm was harder. Mind blowing
Payjoin sent from nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg Mutiny Wallet 
It was great Nests with nostr:npub1tvqc82mv8cezhax5r34n4muc2c4pgjz8kaye2smj032nngg52clq0rkrq4, nostr:npub1hqaz3dlyuhfqhktqchawke39l92jj9nt30dsgh2zvd9z7dv3j3gqpkt56s, nostr:npub1lrnvvs6z78s9yjqxxr38uyqkmn34lsaxznnqgd877j4z2qej3j5s09qnw5 now I have materials for posting on Nostr for next few days just to catch up with links from our discussions.
First up, background for nostr:npub167n5w6cj2wseqtmk26zllc7n28uv9c4vw28k2kht206vnghe5a7stgzu3r fiat airdrop with nostr:npub1au23c73cpaq2whtazjf6cdrmvam6nkd4lg928nwmgl78374kn29sq9t53j.
How it started:
https://www.youtube.com/watch?v=9C7mJxl15wI
How it's going:
what a tale🤠
It’s some MASQUE connect-ip based protocol. Message is encrypted to the blind relay, send to obscura (who can see only destination blind relay ip, not content) who forwards to relay where it is decapsulated and forwarded so the blind relay can’t see origin ip. All encapsulated in HTTP. https://datatracker.ietf.org/doc/draft-ietf-masque-connect-ip/
for validation, sure. But broadcast from your own ip is making links you may not want
The default floor of bitcoin privacy needs to be brought up from underwater for the ceiling to have any significant value
The greatest automotive film of all time in one take: C'était un rendez-vous
I understand how 2 could be relatively insignificant, but I definitely would not describe any aspect of it as cheating. The sender can specify their minfeerate and maximumadditionalfeecontribution to pay for 0 or more receiver inputs for privacy as well as their input + the overhead. A sender won’t sign any response that isn’t within sender-defined fee parameters.
There are two opportunities unique to payjoin to reduce fees beyond opportunistic consolidation (consolodating the incoming sats w/ existing sats can share the overhead of 1 tx)
1. transaction cut-through or forwarding: if you spend the incoming sats to someone else straight away in the same tx, you are never encumbered by fees to spend a utxo since you never take one
2. Overhead. Though indeed receivers do pay to add inputs to a payjoin, the marginal cost should be less than if they were to create their own tx to spend them since the sender is paying for the overhead of the tx header, making batching even more cost effective.
I have written the mechanics of how this could be coordinated here on substack. A few enterprise wallets have expressed interest especially since it hits their bottom line.
https://payjoin.substack.com/p/interactive-payment-batching-is-better
An opportunity to have fees subsidized in the moment of receipt is an even greater incentive. Someone else is willing to pay fees for you to transact, so consolidation or batching in that moment is cheaper than it would be without sender contribution.
trad platforms do boost new accounts to get them hooked. Facebook famously targeted 7 friends in 10 days for new users as a KPI. Nostr clients could do similar.
A story of momentum building and aiming the future of Bitcoin. Great listen. nostr:note16ukrcvc6rewyy6vlht3aln07m8ljf2qrlxjtru6jhs7txfrggyds95w22w
