Proof exchange

Ecosystem / auths-proof-exchange

The exchange sequence is:

challenge -> one bound submission -> response

A submission repeats the Auths protocol, profile identifier/version, and challenge. Every mismatch fails before proof work. Exact negotiation never falls back to a different profile version.

Current transport adapters

• auths-proof-exchange-file
• auths-proof-exchange-https
• auths-proof-exchange-iroh
• auths-proof-exchange-memory
• auths-proof-exchange-tcp
• auths-proof-exchange-unix

These provide memory, Iroh, HTTPS, TCP, Unix-socket, and immutable offline-file transport surfaces.

Boundary

Exchange transports canonical body and proof bytes and exposes typed peer observations. It does not interpret grants, choose trust anchors, construct Auths verdicts, or execute commands.

Transport failure is not an Auths verdict. Exactly-once execution, replay claiming, and budget state remain application responsibilities.