HomeValidators

Validator Network

Qualification pending

Known infrastructure, signed execution evidence and off-mainnet operator qualification. Native consensus and rewards are inactive; independent operation is not yet demonstrated.

Join ComputeNet — Operator Qualification

Independent operator qualification — source, instructions and evidence requirements (off-mainnet)

Validator Responsibilities

Proposed operator responsibilities below are architecture guidance, not claims of independently administered live consensus.

Receipt Validation

Validators receive and verify compute receipts from the network.

Consensus Participation

Proposed native consensus participation; activation and security qualification remain pending.

Peer Propagation

Maintain peer connections and propagate validated receipts.

Uptime Reporting

Report telemetry and maintain high availability.

Fraud Detection

Identify and report dishonest or malformed execution.

Configured infrastructure · reference only

Known infrastructure hosts

Two configured hosts. Reachability and latency have not been independently measured here.

Historical Explorer

ComputeNet Seed

seed-uk-1

Unmeasured

Reachability: Not measured
Latency: Not measured
Independent administration: Not demonstrated

ComputeNet Gamma

validator-gamma

Unmeasured

Reachability: Not measured
Latency: Not measured
Independent administration: Not demonstrated

Source: the application's configured host list, not a health probe or an independent-validator roster. These initial hosts share one administration. Explorer readings describe historical ledger data; they do not establish live consensus or rewards.

Attestation Model

Current bounded jobs are re-executed by separate processes and signed under a pinned policy, initially under one administration. Independent operators and live native consensus are not demonstrated. The steps below describe execution evidence, not weighted consensus votes.

Receipt received

Validator receives compute receipt

Re-execution

Workload is independently re-executed

Hash comparison

Execution hashes are compared

Evidence signed

Policy-bound execution signature is checked

Evidence check

Required signatures and output commitments are checked

// Historical read API observation

chain_id:computenet-mainnet-1

block_height:—

historical_issued:—

max_supply:21,000,000

valid_chain:—

read_api_status:legacy API unavailable

Node Endpoints

Supported HTTPS reads and configured host names; this is not a consensus peer-discovery or activation interface.

Endpoint	Configured role	Status	Latency	Last Poll	Copy read path
https://www.compute-net.org/api/computenet/status	Seed Node	Not measured	—	Never
Gamma — private contained endpoint	Known Gamma host	Not measured	—	Never

Open participation · safe first step

Join ComputeNet — Operator Qualification

The original simple joining experience, backed by a hash-pinned qualification starter. Download, generate your own identity, run a private TLS rehearsal and inspect an acceptance report. No founder credentials, financial deposit or mainnet activation.

Review the qualification boundary

The starter creates only a local disposable qualification environment. It does not install a daemon, expose a host port, connect to Gamma/Seed, activate consensus, issue rewards, import a wallet or move funds. Building initially downloads signed Ubuntu OS packages; application wheels and the legacy codec runtime are hash-pinned.

I understand this starter is unsigned and qualification-only, on my own authorized machine, with no production joining or reward promise.

Get the qualification starter

One browser download contains the launcher, verified source/runtime/dependencies and clear instructions. A browser cannot silently install software on a server. You run the reviewed command locally.

ZIP SHA-256 · 43.7 MiB

9a592e32294e940b1401fadc8fb901e4e95f2af7439819f369263dd41eb4b503

Integrity pinned · publisher signature unavailable

This ZIP is not publisher-signed and has no verified build attestation. Its hashes check byte integrity, not publisher identity. Compare the checksum through an independently trusted channel before running it; a checksum from this same page is not an independent trust anchor.

Checksums Version / manifest Complete installation and recovery notes

Install and follow real progress

The terminal streams actual checks: source/runtime integrity → fresh identities → useful execution → private TLS synchronization → restart recovery → signed acceptance report. This website does not pretend to monitor a remote installation.

Linux · checksum-checked download · qualification only

# Download the ZIP using the button first. Use your ordinary Linux user.
printf '%s  %s\n' '9a592e32294e940b1401fadc8fb901e4e95f2af7439819f369263dd41eb4b503' 'computenet-operator-starter.zip' | sha256sum -c -
# Use a fresh extraction destination; do not merge with an existing folder.
test ! -e computenet-operator-starter && unzip computenet-operator-starter.zip
cd computenet-operator-starter
python3 join.py --bundle-file qualification-bundle.tar.gz \
  --directory ./my-qualification --accept-qualification-only

If something fails

Keep the directory and starter.log. Correct the exact Docker/platform/digest prerequisite and choose a new private directory. Never disable guards, reuse unexpected state, upload keys or use the obsolete mainnet installer. The starter never restarts Docker or host services.

python3 join.py --directory ./my-qualification --inspect

Check your acceptance report

Select only my-qualification/state/operator-acceptance.json. The browser checks its signature and source/bootstrap scope locally. Nothing is uploaded; never select private identity or wallet files.

Public signed acceptance report

Ready for genuine outside-host qualification?

Keep your own credentials. Publish only a public alias, separate-administration statement and consenting resource/evidence link in the official intake. WAN/peer exposure requires a separately qualified TLS edge and explicit peer consent; this starter opens no port.

Open the existing volunteer intake

Learn More

Explore the technical documentation to understand the validator architecture, consensus mechanism, and network topology.

Validator Docs Architecture Whitepaper