Chain ID 1404 · Develop prerelease · Linux AMD64 + ARM64

BlockDAG 2.1.0-rc.2

Download the consolidated node, pool and dashboard release, choose your Linux architecture, and inspect every file before you run it.

HTTPS IPFS pageHTTPS mirror fallbackChoose your pathSee verification

Primary: HTTPS IPFS/IPNS. Fallback: direct HTTPS mirror. Browser links are convenience links and cannot force HTTP/1.1; use the explicit curl/helper path for that guarantee.

01Existing data stays putReuse your current node and retain rollback; no automatic migration is performed here.
02Choose your architectureUse the verified Linux AMD64 or ARM64 package that matches your machine.
03Inspect before runningEvery download exposes its CID, path and SHA-256 before you copy a command.

Choose the shortest safe path

What are you setting up?

Use the page to select and verify a download only. It does not ask for wallet, MAC, host or service settings, and it never changes a node.

Recommended for upgrades

Existing node

Download the matching release beside your current stack. Keep your node data, payout, accounting and rollback under your own control.

New node

Start from the dataset

Download the optional Chain 1404 bootstrap snapshot into a new empty destination, verify it, then catch up from ordinary peers.

Component path

Inspect one component

Choose Core, Pool, Dashboard, Stack or the full runtime ZIP for a focused review before you configure anything.

Choose your download

Pick your architecture and payload

Start with the Linux machine you will inspect, then choose the full stack or one component.

Release verification is required before actions unlock.
Selected payloadWaiting for verification
Size
—
SHA-256
—
IPFS path
—

HTTPS IPFS is the primary browser convenience link. The mirror button is a browser fallback and cannot force HTTP/1.1; use the copied curl --http1.1 command or downloader for protocol-controlled retrieval. Native IPFS is separate.

Choose your chain data

Normal bootstrap or full archive?

The normal RC2 dataset is the practical starting point for most new nodes. The full archive is a separate, much larger archive-node dataset for historical access and recovery; it is not required for ordinary nodes, pools, or dashboards.

Normal RC2 bootstrap dataset

Start a new node safely

The accepted Chain 1404 bootstrap snapshot is separate from the software. Import it only into a new empty destination, then catch up from compatible peers; it is not a complete historical archive.

Recommended for ordinary nodesblockdag-chain1404-order20821036-20260907.bdsnap
Boundary
Native order 20821036 · EVM 20374135
SHA-256
8f7b093b73a7fe390d53d275f5d4b7d69d32aea96220b19a3e2cc54804a5d608
CID
bafybeigui73pb3fnbwee5jeww3bi2c2nzkjvk4ifzafky5yyjqwilpvw2u

Open the normal dataset with an IPFS client · HTTPS gateway

Verify first

New empty destination

Download the 13,931,299,738-byte snapshot, compare the displayed SHA-256, then follow the reviewed dataset guidance in README.md. Ordinary peer catch-up remains necessary.

Dataset commands remain locked until the exact acceptance record is verified.

Operator-maintained archive

RC2 full archive

This is an immutable backup of the RC2 archive node, published on 23 September 2026. Complete historical coverage and independent restore qualification are not yet verified. It is separate from the software and bootstrap dataset, and it is published through a mutable IPNS pointer to an immutable publication record.

Snapshot published 23 September 2026Full archive via IPFS
Dataset CID
bafybeifrdwvhj5lm5wggjgr6qu6leb2xblhlophvm73dnl5u76c3bbwgpe
IPNS record
k51qzi5uqu5dk34tmn07pm0kiew7jtupqhrngaqk5117fpohmok058y1xup5gq
Generation
20260923T145230Z-7afb3b5b
Latest IPNS publication recordDataset gateway
Operator verification

Read before importing

Fetch the publication record first, verify its manifest hash and dataset CID, then retrieve the dataset with a native IPFS client. Import only into a stopped, new or separately recovered archive destination. The IPNS name is mutable; the dataset CID is immutable.

The snapshot links below are fixed. For later weekly updates, resolve the latest publication record and use its dataset_cid. Do not assume the fixed snapshot shown here is the newest.

ipfs name resolve k51qzi5uqu5dk34tmn07pm0kiew7jtupqhrngaqk5117fpohmok058y1xup5gq · ipfs cat /ipfs/bafybeihn3w3tzhsr5lxedl5jhfrsaurav2ndozxlir77xvzhh2jpxatkpe/publication.json · ipfs get /ipfs/bafybeifrdwvhj5lm5wggjgr6qu6leb2xblhlophvm73dnl5u76c3bbwgpe

Full archive use and size

The full archive is approximately 382 GiB (410.6 GB) for the generation shown and is intended for archive operators who need historical access, archive queries, or archive-node recovery. It is not the normal bootstrap dataset. Read the IPNS publication record, verify its manifest hash and dataset CID, and import only into a stopped, new or separately recovered archive destination.

Native IPFS full archive · HTTPS full archive gateway · Current IPNS publication

Three independent options

Run only what you need

Each role is independently installable. The full runtime ZIP supplies the dependencies; your chosen mode decides which services run. You can also run all three together.

Node-only

Keep your own chain

Run Core and its supervisor. Sync normally from peers, use this optional bootstrap, or validate your own copied dataset. No pool database or dashboard required.

Node installation
Pool-only

Connect miners to your node

Run Pool with its own PostgreSQL accounting database. Supply a compatible node endpoint and your own payout configuration. Do not copy another pool's ledger or identity.

Pool installation
Dashboard-only

Observe your services

Run Dashboard with its managed Redis. Supply read-only monitoring endpoints. It neither starts a local node nor receives Docker control authority.

Dashboard installation

All-in-one installation · Instructions for AI agents · Plain-text operator guide · RC65 migration: NOT QUALIFIED · Publisher statement

Your data, your choice. No mandatory publisher signature, GitHub account, signing key or central approval. Select hashes you trust, verify the bytes, and retain Chain 1404/genesis and native/EVM consistency checks. This does not remove transaction or consensus signatures.

A second way to download

Resumable downloads, the same bytes

Checking the separately hash-bound mirror manifest…

Optional dataset: 13 parts

The 13,931,299,738-byte bootstrap is also available as 13 pieces of at most 1 GiB. These are pieces of one snapshot, not different datasets. The helper checks every piece, assembles them in order and verifies the original full SHA-256. Allow about 28 GB for download plus assembly, then additional space for import.

Resumable dataset workflow
Show individual browser download links and hashes

    The original release record is an immutable historical receipt and therefore still says no mirror was published at that time. The separate distribution manifest describes this later download companion. Browser convenience links cannot force HTTP/1.1; explicit curl/helper commands do. Optional public IPFS gateways remain best effort.

    Trust, made inspectable

    Verify before installation

    The browser checks the exact release record bytes against the bound SHA-256. Repeat the same checks locally before unpacking anything. Content integrity, attributed publisher identity and migration compatibility are separate claims.

    sha256sum records/release.json
# After downloading the records directory, compare
# with the bound record hash shown alongside.
# Check each downloaded package with its chooser command.
    Exact release recordBound SHA-256: checking…Software SHA-256 checksumsAll ten release artifactsMining test resultsAMD64, three ASICs and the 120-second observationDataset acceptanceNative/EVM checks and byte identityAdvisory bootstrap observationsDiscovery hints, never chain authorityRC65 community archivePreserved earlier rich release page

    Keep independent infrastructure healthy

    Build, test and share what you learn

    This release is a develop prerelease for independent operators. Run a node or miner only after your own review, report reproducible issues, and contribute improvements through the community.

    This page is informational, not a promise of returns or future uptime. It does not grant publisher authority, replace local review or change an existing node.

    Support the communityLearn about miningExplore Chain ID 1404Contact the community

    Protected compatibility boundary

    RC65 → RC2 migration is NOT QUALIFIED

    Maintainer migration testing was not performed. Do not perform an in-place upgrade or swap binaries against old data. Read the human guide or AI runbook; stay on RC65 or choose a separate fresh installation.

    Immutable history

    Earlier community work

    RC65 rich pageCommunity participationInstallation notes