NU7 relay clients 5456ff5

NU7-ready relay clients from 5456ff5c10cf385a98554b17bbc4a0ee6b8b941d, using the exact Linux binaries deployed across Sovright's four production relay regions.

Install or build

• Download sovright-nu7-partner-upgrade-5456ff5.zip for the Luxor and Sluicey guides, shared upgrade/recovery procedure, source-build recipe, checksums and the verified binary archive together.
• Download bedrock-5456ff5c10cf385a98554b17bbc4a0ee6b8b941d-linux-amd64.tar.gz and its .sha256 companion for the original qualified package.
• Individual bedrock-p2p-ingress-linux-amd64 and relay-sidecar-linux-amd64 assets retain the previous client release's filenames. forge-sidecar-linux-amd64 is an identical sidecar alias. relay-node-linux-amd64 is for installations that actually run a mesh daemon.
• nu7-source-5456ff5.tar is the exact Git source archive used by the build; the handoff includes the pinned Docker/Rust recipe. The automatic GitHub source ZIP/tarball has different packaging and is not covered by that uncompressed archive's digest.
• release-SHA256SUMS covers the uploaded release assets; SHA256SUMS inside the original binary archive covers its extracted files.

Runtime: Linux x86-64 GNU/glibc >= 2.34. No ARM64/musl build is included. Source builds pin Rust 1.97.1, the original builder image digest and Cargo.lock; record and qualify your own output rather than assuming byte-identical rebuilds.

Upgrade the components you run

bedrock-p2p-ingress includes the Full-role pool submitblock gateway and P2P bridge. relay-sidecar receives relay blocks and optionally submits them to the local fullnode. A partner running both must update both; replacing the receiver does not replace the pool gateway.

Preserve existing authentication identity/role, relay peers, FEC, fullnode endpoints, proxy/pool RPC routing and submission gates. Have a tested direct-node/redundant submission fallback before stopping an active pool gateway. Do not enable new submission paths or unreadable-body bypasses as part of this upgrade. Mainnet forwarding uses protocol 170190; observer-only admission is a separate policy.

Ingress does not implement --help/--version; those flags do not prevent daemon startup. Use the safe loader checks in the handoff. Sidecar CLI flags do not override a supplied TOML file.

Fullnodes independently need NU7-capable software and chain agreement. Mainnet NU7 is scheduled at height 3,543,405, branch 77190ad9. At/after activation or when height is unknown, an old/pre-NU7 reader is not a valid rollback: preserve the working node submission fallback and fix forward.

Qualification

The original Linux release qualification passed 879 tests, zero failures, three explicitly ignored tests. It covered the selected ingress, relay and sidecar packages, then rebuilt production binaries after tests. The immutable original archive and all executable hashes were independently verified before release publication.

Live preactivation checks established exact running hashes, protocol 170190, canonical block forwarding and successful/duplicate submissions across all four relay regions. See the east4 qualification and regional rollout evidence.

A second clean Linux build ran the documented source recipe: 879 passed, zero failed, three ignored, and all four executable hashes matched the deployed release exactly. This evidence is recorded in release-provenance.json. Neither test/rollout evidence nor a connected session establishes partner-specific delivery, mining origin, sustained lossy 25-second load, controlled activation/reorg recovery or uninterrupted future activation. The live authenticated NU7 submission, scheduler benchmark and concurrent-sender stress tests remain separate gates. Sovright's new local health timers record status; operator paging remains unconfigured.