Bump payjoin directory 0.0.2 (#649)

Use standard Oblivious HTTP Key Configuration bootstrapping and
decentralize directory operation

Author: DanGould

Cargo-minimal.lock

@@ -1651,7 +1651,7 @@ dependencies = [
 
 [[package]]
 name = "payjoin-directory"
-version = "0.0.1"
+version = "0.0.2"
 dependencies = [
  "anyhow",
  "bhttp",

Cargo-recent.lock

@@ -1651,7 +1651,7 @@ dependencies = [
 
 [[package]]
 name = "payjoin-directory"
-version = "0.0.1"
+version = "0.0.2"
 dependencies = [
  "anyhow",
  "bhttp",

payjoin-directory/CHANGELOG.md

@@ -1,5 +1,15 @@
 # payjoin-directory Changelog
 
+## 0.0.2
+
+- Do not log ERROR on directory validation errors [#628](https://github.com/payjoin/rust-payjoin/pull/628)
+- Use payjoin 0.23.0 (056a39b8a8849451ee605dc7ae786f9cda31ace5)
+- Announce allowed purposes (6282ffb2c76a93e1849ecc1a84c9f54ccf152cc5)
+- Serve `/.well-known/ohttp-gateway` as per RFC 9540 (6282ffb2c76a93e1849ecc1a84c9f54ccf152cc5)
+- Rely on `payjoin/directory` feature module [#502](https://github.com/payjoin/rust-payjoin/pull/502)
+- Introduce db-module-specific `Result` [#488](https://github.com/payjoin/rust-payjoin/pull/488)
+- Return bound port on listen for test stability (d4fa3d440abd102fcbb061b721480dee14ff91dc)
+
 ## 0.0.1
 
 - Release initial payjoin-directory to store and forward payjoin payloads using secp256k1 hpke

payjoin-directory/Cargo.toml

@@ -1,14 +1,15 @@
 [package]
 name = "payjoin-directory"
-version = "0.0.1"
+version = "0.0.2"
 authors = ["Dan Gould <[email protected]>"]
-description = "A directory server for Payjoin V2 coordination"
+description = "A store-and-forward and Oblivious Gateway Resource directory server for Async Payjoin"
 repository = "https://github.com/payjoin/rust-payjoin"
 readme = "README.md"
-keywords = ["bip78", "bip77", "payjoin", "bitcoin", "relay"]
+keywords = ["bip78", "bip77", "payjoin", "bitcoin", "ohttp"]
 categories = ["cryptography::cryptocurrencies", "network-programming"]
 license = "MITNFA"
 edition = "2021"
+rust-version = "1.63"
 resolver = "2"
 
 # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

payjoin-directory/README.md

@@ -1,15 +1,18 @@
-# payjoin-directory
+# Payjoin Directory
 
-## Payjoin v2 Directory Server
+[BIP 77](https://github.com/bitcoin/bips/pull/1483) Async Payjoin (v2)
+peers store and forward HTTP client messages via a directory server in order to
+make asynchronous Payjoin transactions. This is a reference implementation of
+such a server
 
-Payjoin v2 peers store and forward HTTP client messages via a directory server in order to coordinate an asynchronous Payjoin transaction. Version 1 Requires the receiver to host a public HTTP server and to set up security using either HTTPS or Onion Services above and beyond typical HTTP client operation.
+V2 clients encapsulate requests using
+[Oblivious HTTP](https://www.ietf.org/rfc/rfc9458.html) (OHTTP) which allows
+them to make payjoins without the directory being able to link payjoins to
+specific client IP. Payjoin Directory is therefore an [Oblivious Gateway
+Resource](https://www.ietf.org/rfc/rfc9458.html#dfn-gateway).
 
-V2 clients use Hybrid Pubkey Encryption established in the bitcoin URI payment request for security instead, allowing lightweight clients secure communication without the burden of setup, which is done by the operator of this third-party directory server. This directory only sees OHTTP encapsulated, encrypted requests to prevent it from collecting metadata to break the privacy benefits of payjoin for messages who follow the spec.
-
-This directory *only* accepts v2 payloads via Oblivious HTTP (OHTTP) and requests used to bootstrap OHTTP, preventing it from identifying IP addresses of clients.
-
-## Architecture
-
-The directory is a simple store-and-forward server. Receivers may enroll by making a request to a pubkey identified subdirectory. After success response, they may share this subdirectory as payjoin endpoint to the sender in a bitcoin URI. The sender may poll the subdirectory with a request posting their encrypted Fallback PSBT expecting a Payjoin Proposal PSBT response. The receiver may poll the enroll endpoint to await a request, later posting their Payjoin Proposal PSBT for the sender to receive, sign, and broadcast.
-
-The directory does depend on a second independent Oblivious HTTP Relay server to help secure request/response metadata from the Payjoin Directory.
+Payjoin Directory also behaves as an [unsecured public-facing HTTP
+server](https://github.com/bitcoin/bips/blob/master/bip-0078.mediawiki#unsecured-payjoin-server)
+in order to provide backwards-compatible support for [BIP
+78](https://github.com/bitcoin/bips/blob/master/bip-0078.mediawiki) Payjoin (v1)
+clients.