Announcing REElay 😡: BIP 78-compatible Gullible (pre-serverless) Payjoin PoC

GitHub

REElay 😡: BIP 78-compatible Gullible Payjoin PoC (WebSockets) by DanGould · Pull Request #78 · payjoin/rust-payjoin

This proof of concept demonstrates the ability to receive a payjoin using a relay instead of hosting a public https or onion endpoint. I intend thi...

This proof of concept demonstrates the ability to receive a payjoin using a relay instead of hosting a public https or onion endpoint. I intend this to be an easy way to receive payjoin in testing environments and potentially as a BIP 78 payjoin v1 compatible fallback for a v2 Serverless Payjoin spec.

Considering running Apple silicon just for #[0]​. I want unified experience on desktop and mobile

Unlike single-source batching, multi-source optimizes payment flows requiring sequential transactions, like funding lightning channels from exchange withdrawals. Eliminating sequential transactions significantly improves on what was otherwise thought to be the upper limit of fee savings from payment batching.

Fees, BOB Radio, and Reinforcements

Just an update

Interaction can reduce fee spend and preserve privacy at the same time. ICYMI on bitcoin-dev:

Interactive Payment Batching is Better

Payjoin for More Than Privacy

When deploying a 402 payment required API should one - Accept Lightning - Accept service-specific ecash - ¿por qué no los dos?

Lightning Address is the best pay-to-endpoint UX in fact View quoted note →

Payjoin is growing. Get on this list if you support bitcoin privacy too.

The financial police can do next to nothing when the financial house is on fire. That’s what the fire department is for. #Bitcoin

Bitcoin privacy is counterintelligence

A mailchimp/substack hybrid to manage Nostr mailing (noting?) lists with btc subscriptions