Payjoin-in-Potentiam lets someone else fund your channel in a single transaction.

It's an optimization over the non-interactive swap-in-potentiam protocol. I know when I send a transaction I tend to sit on the other side refreshing the page. This makes that refresh happen twice as fast.

I see it this way too. Scale would come from each transfer of sats from one utxo to another being a batch of multiple peoples' intents all at once.

sure, you can try in bdcpayservers testnet demo https://docs.btcpayserver.org/Development/TestnetDemo/

or use payjoin-cli with bitcoind https://crates.io/crates/payjoin-cli/0.0.2-alpha. I run it on mutinynet (mutiny signet) at https://mutiny.payjoin.org:4433/bip21

How would you approach getting a soft fork merged from assessment to activation?

How would you you recruit reviewers for a new BIP?

I wonder if there is a way to replace the lockup transaction & sweep with one transaction with payjoin interaction, or if that even makes sense since even a replace lockup will probably be saved by mempool.space and leak metadata that way.

Fake news. if you read Chinese, the draft bill is to prevent an SBF from happening in Taiwan.

Here's a summary of the primary source courtesy of chatGPT https://chat.openai.com/share/067d13bf-91ea-4711-8179-3530e51aee5b

"ill-informed, arbitrary, and bad-faith restrictions on Bitcoin privacy imposed by those who neither understand its benefits nor have any interest in preserving our right to privacy will become irrelevant." hits hard.

Love that you drew from such a broad context to tell the story from end to end.

Why not apple pay? Seems relatively privacy conscious in practice.

Nice surprise to see this Gospel on the top of SN this morning 🔥

Payjoin is a batched payment and consolidation transaction between sender and receiver. The result has some fee savings from batching and privacy benefits from the joint structure. Both sender and receiver contribute inputs and may create outputs. The result can look the same as normal transaction activity thus creates more indistinguishable transaction interpretations for all. Nothing limits payjoin to 2-input 2-output transactions.

My understanding is it's CONNECT-IP / MASQUE where the encrypted & HTTP encapsulated IP request is sent to Obscura and the details of the request are forwarded to what they're calling a "Blind Relay" which only knows Obsucra's IP.

2-hop onion routing with pre-defined routes. No Tor consensus. Very simple.

Elon twitter did bring another pole to discourse but not yet the multipolar ideal

Roy beats everyone at foosball with Breez SDK too, OP but can't be nerfed

The past weeks at TABconf and Bitcoin Park have led to significant improvements in the design

Serverless Payjoin feedback has been outsized. This is my attempt to make sense of it and shepherd the horde across the cybernetic steppe.

I hope this helps open up dialogue and am curious to hear what you think.

bc you're depending on a third party not to leak your info / metadata with each step of the way. or maybe you want to settle more money than you can effectively with these methods

"To keep your secret is wisdom; but to expect others to keep it is folly"

— Samuel Johnson

Payjoin Dev Kit has some funding from the first wave of OpenSats grants but not from Spiral or to the same level. The Rust Dev Kit idea is a great one for building a correct, easy to use API that can be embedded every where and was sorely missing for payjoin.

If you like what you see you can donate straight from your Stacker news wallet to the the geyser campaign or the payjoin endpoint shown there: https://geyser.fund/project/payjoin/

How the heck did you post this so fast??? 😄

A few questions to reach consensus on before this gets standardized:

If you think it's Nostr's time to shine or you want to see BIP 47 (or some alternate?) contact system baked in, now's the time to speak up so we have a unified front moving forward. The privacy wars are so yesterday.