Monolythium/Build/Guides/Running an operator

Operator release checklist.

Public operator onboarding is unavailable. Development network 69420 was reachable but stale at height 74,907 when checked on 16 July 2026; this page records the evidence a future opening must publish.

· Current outcome

A readiness checklist, not a cluster slot.

Do not install an unsolicited binary, expose a host, submit identity documents, or send a bond based on this page. Wait for a dated, versioned operator release.

· Release evidence required

What you'll need.

ArtifactHardwareNetworkAdmissionEconomicsMonitoring
Version + checksum + signaturePublished supported matrixAdvancing head + peersVersioned public contractExact activated parametersDocumented health + alerts
· Steps

6 numbered steps.

01
Status

Confirm an advancing public network.

Verify chain id, genesis hash, head height, latest timestamp, and peer health. A reachable RPC or registered topology is insufficient.

02
Artifact

Verify the exact node release.

Require a canonical tag, checksums, signatures or provenance, an SBOM, upgrade notes, and a supported platform matrix. This page provides none of those artifacts.

03
Host

Follow the released hardening profile.

Do not guess CPU, memory, disk, ports, key storage, or snapshot requirements. Use the version-specific operator documentation and verify every downloaded input.

04
Admission

Use a public versioned path.

A legitimate opening must identify the admitting entity, cluster contract, selection rules, privacy terms, and support channel. Staff should not solicit operators by DM.

05
Economics

Read activated parameters before signing.

Bond, reward, slashing, unbonding, and delegation values require finalized state and a complete transaction preview. Historical design values are not terms.

06
Operate

Publish honest health.

Monitoring must distinguish process uptime, peer connectivity, source-head age, signing participation, and finality. Explorer labels alone are not operational proof.

· Verify

Current release gate remains blocked.

operator_onboarding: unavailable development_rpc: stale observed_height: 74907 observed_latest_timestamp: 2026-07-08T22:39:05Z mainnet: not_running send_bond: false

Replace this status only with a dated operator announcement, fresh advancing-network evidence, and verifiable release artifacts.

Wait for a dated opening.

This guide is not an onboarding offer. The public RPC is currently stale and the SLH-DSA emergency-key registry was removed. Wait for a dated operator release with signed software, current network-health evidence, exact economics, and a versioned admission path.