Dan Gould

That works for me. Thanks for the tip

To stay completely backwards compatible without requiring a new version or grace period, a sender explicitly ignoring mixed input script check also use a request uri parameter like `mixin=1` to...

> However there actually are such wallets and thus mixing inputs doesn't reveal it's a PayJoin, it actually reveals it's **not** a PayJoin - thus it leaks data. So that...

Any reason this shouldn't be re-opened? I started implementing the same functionality before I found this PR. I ran into a small issue where we're calling [`Response::do_from_stream` now](https://github.com/algesten/ureq/blob/2300a5b3787b1ac800314dc47f075f4850026bb3/src/stream.rs#L458) which takes...

> Are you having this issue while doing some kind of remote debugging ? The same behavior happens across remote or local debug > Do you have this issue when...

The [BIP-77: Payjoin V2](https://github.com/bitcoin/bips/pull/1483) proposal gets rid of the requirement for both parties to be online and the requirement to use TLS. It's authenticated with [Hybrid Public Key Encryption](https://datatracker.ietf.org/doc/rfc9180/) that...

Thanks for bringing up this issue. I see two sane approaches to integrating send support [as you mention on Telegram](https://t.me/blixtwallet/168967) ## 1. TypeScript bindings to ~WASM~ Swift/Kotlin Payjoin Dev Kit...

I've use this `+` feature to test building against a specific MSRV in the past. @dpc do you suggest running a new nix shell with a specific version for this...

> i tried to do a payjoin with a provided QR code, but got error 'receiver rejected our original PSBT'. > -- @Overtorment I don't have your exact set up...

Automated payjoin receivers must check that the "original psbt" transaction to be augmented can be broadcast as fallback in case the sender doesn't broadcast the payjoin they propose so that...