Dan Gould
Dan Gould
Not suggesting payjoin is the move here in the slightest, but I raise the concern that a naive swap all to LBTC and then swap back isn't really any better...
Just came to me while tweeting: If you *did* want to use payjoin for consolidation, instead of a swap service, you could queue up a consolidation to happen next time...
- [x] decouple typestates - [ ] decouple errors - [x] minimize SessionEvent variants
The session tests must not use v1::SenderBuilder. Use v2 with NoOp persister.
I wonder why this isn't tested by CI
This is expected behavior to me but perhaps improperly documented. Without `_manual-tls` I expect you to terminate TLS on your own with a reverse proxy, since `"http://" && not(".onion")` payjoin...
Ok, closing criteria for this issue is some obvious println on receiver startup when not using _manual-tls then
@chavic may you catalog the absolutely necessary issues that MUST be completed before we can release the 12/1 Bull Bitcoin Mobile integratation I know there is some checklist here https://github.com/Uniffi-Dart/uniffi-dart/issues/78
[BIP 77](https://github.com/bitcoin/bips/blob/master/bip-0077.md) Async Payjoin (v2) uses PSBTv0 (BIP 174) not PSBTv2 (BIP340) and is p2p coordinated. The sender and receiver rendezvous at a blind directory server that hosts mailboxes, but...
Payjoin spec doesn't restrict mixed script types but clients can, correct. It's just concerned with coordination between 2 parties, clients care about tx construction.