HRC 0.2.2

Optional self-service invitations let a host send one private invitation in advance. Recipients join with locally generated keys without returning request or registration files. Manual approval remains available and hosting starts disabled.

• Separate pinned TLS 1.3 admission listener with finite invitation and work limits.
• Ordinary member access and an independent read-only Page identity.
• Automatic same-ID access renewal within existing consent, with history and drafts retained.
• Exact interrupted-operation recovery, per-recipient revocation and explicit offline controls.

Linux x86_64; GNU libc 2.39 or later. Core 0.10.4 and Suite 0.10.3 remain the supported native pair. No native protocol or conversation schema change is required.

Read Documentation/SelfServiceInvitations.md and Documentation/Installation.md in the archive. Verify SHA256SUMS.sig against the independently pinned publisher fingerprint before checking the downloads:

SHA256:XaKyGFow6q4DkZee5rQLUXN66AxQogVEtWb1sQS6m24

Signature principal: HyperNetPublisher. Namespace: HyperNetRelayChatRelease1.

HyperNet Relay Chat 0.2.1

HRC 0.2.1 adds a server-enforced allowlist for creating rooms, private groups and direct conversations. Older clients obey the same policy; agent accounts cannot inherit an allowed human operator's identity.

Page links can open through a separate admitted reader selected in Settings > HyperNet Pages, while chat stays connected. One browser may use each reader profile at a time.

The supported native pair is Core 0.10.4 and Suite 0.10.3, which correct route voucher renewal and updates to approved Pages. Existing chat schemas and identities are retained.

Download the binary and source archives, SHA256SUMS, SHA256SUMS.sig and PublisherKey.txt. Follow Documentation/Installation.md to verify the independently pinned publisher and every checksum before installing. Linux x86_64 requires GNU libc 2.39 or later; the existing platform and workload qualification limits still apply.

HyperNet Relay Chat 0.2.0

HRC 0.2.0 adds a desktop Operations workspace for creating or joining HyperNets, hosting chat, inviting accounts, enrolling agents, and controlling local models and bots. The application-menu launcher and setup controls work independently of an LLM.

This release includes fourteen light/dark JSON themes, consistent controls, Classic message dividers and optional bubbles, bounded persistent model context, and the external setup/operations assistant harness. HyperNet Page links retain complete destinations behind compact labels and open the configured Suite browser with the selected HRC palette.

Native hosting uses signed Core 0.10.3 and Suite 0.10.2 packages with explicit finite consent and same-identity renewal. Existing Page routes and reader permissions apply. External provider discovery is not newly qualified; previous performance evidence retains its recorded versions and workload.

This remains a private Apache-2.0 Linux pilot. Start with the installation guide, desktop hosting, bot setup, and release notes. Verify the signed checksum inventory before installation.

HyperNet Relay Chat 0.1.0

HyperNet Relay Chat 0.1.0 is the first qualified Linux pilot: native chat over mandatory HyperNet transport, with GUI, TUI, CLI and an agent API. It includes persistent conversations and indexed history, explicit independent/delegated agent participation, deterministic moderation, encrypted confidential direct conversations and private groups, and explicitly shared rooms between independently administered HyperNets.

Requires HyperNet Core 0.10.2 and HyperNetSuite 0.10.1. There is no direct Internet transport fallback.

The qualified native Ubuntu 26.04 x86_64 profile has eight interactive controllers, twelve HRC accounts, two admitted client applications, twelve receiving streams and two authority connectors. All 375 offered normal messages committed uniquely, with direct acknowledgement samples and no observed refusal.

Measurement	Normal traffic	Defined hostile workload
Established-message p95	335.110 ms	768.295 ms
Direct samples / offered messages	150 / 150	225 / 225
Client-completion p95, reported separately	528 ms	3350 ms

Message timing runs from an encoded message write on an established authenticated stream to receipt of the complete committed acknowledgement. Setup, client queueing, persistence and UI time are excluded. The normal 500 ms and approved hostile 1000 ms p95 limits pass; the original hostile 500 ms comparison does not. These are bounded pilot measurements, not universal latency guarantees.

Moderation completes in 899/686 ms, recovery in 4.401 seconds, and all five boundary checks pass. Peak HRC service RSS is 34,676,736 bytes, excluding HyperNet processes. The integration profile records the exact workload, started and missed hostile offers, resource limits and evidence boundaries. Simultaneous federation load, independent-host failure, full Wayland and screen-reader coverage are not qualified.

Download all five assets and follow installation and signature verification before unpacking. The binary requires GNU libc 2.39 or newer and the documented shared libraries. The corresponding source archive, Apache-2.0 licence and dependency notices are included. Repository and binary access remain private; website manuals are published separately.

Publisher fingerprint: SHA256:XaKyGFow6q4DkZee5rQLUXN66AxQogVEtWb1sQS6m24. The checksum signature uses principal HyperNetPublisher and namespace HyperNetRelayChatRelease1.

Conversation setup covers admission, service and client profiles. Operations covers retention, recovery and upgrades. Confidential conversations retain explicit device membership and future-only history by default.