We are coordinating a coauthored LF x402 privacy-extension draft and want Bermuda/b402 in the author set.
Draft: https://github.com/goheesheng/zx402/blob/main/beta/docs/competitive/joint-x402-privacy-spec.md
Focus: additive extension fields + verifier API + compliance attestation hooks so private settlement implementations remain interoperable.
If aligned, we propose:
- 30-minute technical alignment call next week,
- shared conformance vectors,
- coauthored v0.1 submission into the LF x402 standards track.
Concrete review asks for Bermuda:
- Confirm extension field naming compatibility with b402 integration flows.
- Confirm preferred verifier/receipt API shape for provider interoperability.
- Flag governance path for submitting via LF x402 working track.
Happy to adapt this into a PR against docs if that is easier for your process.
We are coordinating a coauthored LF x402 privacy-extension draft and want Bermuda/b402 in the author set.
Draft: https://github.com/goheesheng/zx402/blob/main/beta/docs/competitive/joint-x402-privacy-spec.md
Focus: additive extension fields + verifier API + compliance attestation hooks so private settlement implementations remain interoperable.
If aligned, we propose:
Concrete review asks for Bermuda:
Happy to adapt this into a PR against docs if that is easier for your process.