Participant Relationship Protocol

Archived criterion

F25-PI: Pending

Archived previous-definition assessment — revision 5.73. Retired in 5.82; excluded from the active matrix and counts. This historical verdict is not a current assessment.

Historical wake-traffic inventory (cutoff retired)

Rationale

The selected column still specifies wire-v4 with protected adjacency and E2E suite 0x0202. The effective wire-v4 document retains ONION and two-flight HS2. The author-approved no-ONION fast-path direction belongs to a separately described successor: the TPA proposal explicitly preserves the existing wire implementation and leaves successor encoding/migration unqualified. These are not interchangeable byte budgets. Rechecking legacy TLV widths for identity suite 0x0002 gives M1=1736 and M2=1778 bytes; two fresh exchanges total 7028 canonical HS2 bytes before framing. For 256 useful bytes split into two 128-byte directions, legacy OPEN/ACCEPT plus four E2E item headers, four RRL record headers and four list counts total 384 inner bytes. The older 640-byte candidate instead contained 512 useful bytes. Neither inner amount is a complete endpoint budget or automatically additive to historical link subtotals. The next source review locates an actual cover scheduler and padding policy: prp_session_cover_work_fn sends an empty two-byte RRL only for active adjacent TX sessions. For suite 0x0202 the unpadded protected unit is 30 bytes (12 nonce + 2 RRL + 16 tag). Its size is raised to the configured padding target, bounded by session capacity. The scheduler uses ceil(8*unit_bytes*10^9/cover_rate_bps) nanoseconds with a 1 ms floor, and schedules from the actual current time rather than replaying missed intervals. At a 256-byte target and 1024 bit/s, one stable TX adjacency sends at most 1+floor(T/2 seconds) automatic cover units over an active interval T. For one such adjacency in each direction and T=60 seconds, the conservative cover-only bound is 18228 native Ethernet byte-times or 19964 over IPv4/UDP/Ethernet. This is a conditional source-derived bound, not measured completion in 60 seconds.

Assessment method

Source control-flow review and conditional cover-byte bound; no runtime execution

Source context

Effective sibling specification files pinned by path and SHA256 in round474-sources.json; successor files include uncommitted proposals, not all attributable to the observed HEAD or public mirror

Outstanding qualification

F25 remains Pending. The cover-rate field is not a total interface shaper: real traffic is additional, and the separate TX_CREDIT path can emit extra cover units. The candidate therefore excludes manual credit requests, cover-policy resets and replacement adjacencies during its measured interval, with exactly one active TX adjacency in each direction and capacity at least 256 bytes. Ethernet is untagged; IPv4 has no options; 38 Ethernet byte-times and 28 IPv4/UDP bytes are counted per 256-byte unit. PHY-specific coding is not included. Target=256 is a padding floor, not a cap on larger real packets. The 60-second duration is an explicit candidate condition still needing a successful complete sequence, not a newly imposed F25 deadline. Actual bootstrap, route/relation controls, protected data wrapping and delivery time remain to be bounded together. Local admission method 0 permits direct HS2 without challenge/proof while retaining 0x0202; it is not a downgrade or a universal entitlement against a peer requiring PoW. The no-ONION successor is not substituted. No source binding here claims integrated implementation acceptance.

Public sources

Editorial evidence references

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