Your services · Your data · Your choice

Install only what you need.

Run a node, a pool or a dashboard independently—or combine them. Keep the same verified RC2 binaries and choose your own configuration.

Step-by-step commands Guide for AI agents

No mandatory publisher signature, account, signing key or central approval. Verify hashes and Chain 1404 consistency before use.

Three independent options

Choose a service role

Mode: node

Your own node

Core and its supervisor, without Pool or Dashboard. Begin empty and sync from peers, or separately verify an owner-selected dataset. No PostgreSQL or payout address required for a non-mining node.

Node settings and commands

Mode: pool

Your own pool

Pool plus a fresh local PostgreSQL ledger. Supply your compatible Core endpoint, local RPC credentials, payout and fee. It does not silently start a node or copy another operator's accounts.

Pool settings and commands

Mode: redis-dash

Your own dashboard

Dashboard and managed Redis. Observe your selected services with limited credentials. No implicit local node, node lifecycle authority or Docker control socket.

Dashboard settings and commands

Want all three together?

Select all-in-one. The helper starts the node first, then Pool/PostgreSQL and Dashboard. You still supply your own settings, data, payout and network policy.

Prepare and start the stack

HTTPS IPFS first · HTTPS mirror fallback

Download once. Check every byte.

Use the HTTPS IPFS page and native IPFS links first. The direct HTTPS mirror is a labelled fallback; its browser links cannot force HTTP/1.1. Use the explicit curl --http1.1 commands or helper for the guaranteed request policy. The helper restores the full metadata layout, resumes transfers and checks complete size/SHA-256 before accepting a file.

Direct HTTPS mirror fallback: blockdagengineering.github.io. Original archive documentation is unchanged. Use this versioned companion for current v2 commands, independent roles and dataset choices.

Exact download commands

Resumable HTTP/1.1 helperPython 3; scoped HTTP/1.1 or native IPFS Role-aware installerPrepare / start / stop / status Actual service runnerUsed by the shipped v2 lifecycle Separate download manifestBound to the original release and full snapshot SHA Companion SHA-256 checksumsInspect before execution

Optional bootstrap, not permission

Which chain data should you use?

Keep existing valid data, start empty and sync normally, or import this bootstrap/your own verified copy. These are data choices, separate from the three service roles.

One snapshot, thirteen download pieces

The optional 13.93 GB format-4 snapshot contains both native chain and EVM state at native order 20,821,036 / EVM block 20,374,135. It is a bootstrap—not a complete historical archive claim. Catch-up is still needed.

The HTTP helper checks 13 ordered pieces and the complete assembled SHA-256. Parts are not standalone datasets.

Download the dataset

Hash integrity plus semantic validity

Verify the archive, import only to a new empty writable candidate, and inspect native/EVM consistency. No special folder name, matching source UID, official publisher or compulsory signature is blockchain authority.

Actual access, safe paths, one-writer locking, Chain 1404/genesis, peer and payout protections remain enforced. Keep rollback.

Exact validation and space guidance

Know what has actually passed

Running is not yet mining.

The guide distinguishes download, staging, service startup, chain synchronization and mining acceptance. Native VM install checks do not prove physical ASIC work, block/accounting progression, reboot or soak. The original AMD64 TesterD mining receipt remains separately available.

Original mining test AI-agent instructions Back to the community release page

Protected compatibility boundary

RC65 → RC2 migration is NOT QUALIFIED

Maintainer migration testing was not performed. Read the human guide or AI runbook. Staying on RC65 or making a separate fresh installation are the safe alternatives.