Participant Relationship Protocol

Back to matrix

F21-PN: Yes

Rationale

Wire-v4 HS2 authenticates both endpoint identities. The endpoint API exposes a provenance-bearing peer descriptor: Strong ID, public key, relationship/session references and transcript binding, only for an open relationship with established session. Application I/O is attached to that relationship. This supports reusing the authenticated final-peer identity without an application login/token exchange; it supplies neither civil identity nor application permissions.

Assessment method

Documentary/code analysis

Source context

Primary specification and application API

Outstanding qualification

Endpoint API/code review at c6bdd443ab031c55f5ed25c3c2d2615d9227d5a3, not executed end-to-end qualification. Bind the selected carrier to the final E2E relationship; test wrong-key rejection, reference mismatch, receive provenance, close/rekey and stale identity caching. Descriptor flags explicitly do not assert a remote identity generation. No universal application integration or transit-anonymity certification.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.