F25-NS: Yes

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

A bounded two-relay NIP-01/WSS configuration meets the endpoint budget while preserving proactive copies on both selected relay paths. Count two fresh DNS A lookups, two complete TCP/TLS1.3/HTTP Upgrade connections, subscription and signed-event exchange on both, acknowledgments and conservative closure/control reserves. The inventory reserves 23 data-bearing TCP segments per relay at MSS 1,024, an ACK per segment, setup/shutdown, IPv4/Ethernet framing, DNS and fresh ARP: 63,020 bytes total. Each event carries 256 useful bytes encoded as base64, with event identifiers, author key, signature and WebSocket framing included.

Assessment method

Constructive full two-relay endpoint byte inventory

Source context

NIP-01 event/relay exchange, WebSocket, DNS and TLS formats

Outstanding qualification

Constructive documentary witness, not measured traffic or a bound for arbitrary public relays. Compact validated certificate chain <=2,048 bytes, bounded Hello/HTTP headers, known author and two preselected public relay hostnames; one bounded DNS reply each through the configured recursive resolver. Empty matching stored history and no unrelated matching events; small NIP-01 messages and timely acknowledgments. No tickets, resumption, online certificate fetches, redirects, retries, extra NIPs or optional TLS padding. Two relay paths and duplicate events are counted; infrastructure traffic not crossing the endpoint is excluded by F25. Event length placeholders do not test signatures. Nostr content remains publicly readable under this selected profile.

Public sources

Editorial evidence references

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

round324-budget.json
round324-sources.json