Participant Relationship Protocol

Back to matrix

D04-PN: Yes

Rationale

The selected PRP profile uses locally controlled identity key material independently of carrier locators. Architecture section 4.4 distinguishes IDENTITY SCIR public-key commitments from machine addresses. libprp exposes keypair generation and signing; the portable session configuration takes local identity material or a key handle separately from injected transport. Runtime documents identity storage protected by an application-held wrapping key. Additional identities therefore do not require additional host interface addresses or routes on an already authorized transport. This is a documented architectural/component capability, not a newly executed multiuser deployment.

Assessment method

Initial evidence inventory

Source context

Pinned architecture, hybrid identity API, portable session configuration and runtime documentation

Outstanding qualification

D01 remains Pending: full selected native/UDP endpoint operation and privileged helper dependencies are not qualified by this Yes. Existing carrier provisioning and access permission are assumed, not removed. Counterparties still decide whether to accept a newly created identity. The criterion does not guarantee quotas, protection from key theft, or zero resource interference between users.

Public sources

Editorial evidence references

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