Dan Gould

> By running an OHTTP relay, could anyone use that to connect to any other OHTTP gateway? In [section 8.2](https://ietf-wg-ohai.github.io/oblivious-http/draft-ietf-ohai-ohttp.html#name-resource-mappings): "The relay will only forward for Oblivious Gateway Resources that...

edit: [ohttp-relay](https://github.com/payjoin/ohttp-relay) is now available as a docker container here: BYO ssl cert and the rest just workstm FYI standing up a relay is as simple as adding a couple...

This should now be receiving v2 payjoins, however the persistence and asynchronous completion is still a bit janky in this form factor. It does not seem like `resume_payjoins` is properly...

This is now based on the `payjoin-0.13.0` release, persists receive payjoin sessions, and adds pending transactions to the `wallet` using `insert_tx` and `cancel_tx` before they hit mempool. Though tracked payjoins...

While I've left a few TODOs that are in progress, this change is ready for deeper review

Adding the ability to send payjoin from bdk using [rust-payjoin](https://crates.io/keywords/payjoin) was [~a 200 line change including test for BitMask](https://github.com/diba-io/bitmask-core/pull/121). Receiving payjoin can be done securely using a relay. A second...

> I think that would be really great to add. I think the only thing I see as a problem is that we use no-std rust-bitcoin and need default-features =...

Sounds awesome. Fetching OHTTP Keys via CONNECT method in a crate shared between payjoin-cli and tests might be the simplest start that can be closed in a single PR

yes. keep it open until such a solution is actually shipped. That crate is still unreleased.

This is done (as a feature) pending merge of #272