dvdmining
HomeSeedsCheckerNetwork MapCanon Defender
⚠️ These builds are outdated. They're no longer current and aren't kept in sync with the live network — kept here for reference only. Don't use them to run a node you depend on.
BlockDAG · node builds

Two builds. Run them. Decide for yourself.

Two independent BlockDAG node builds, packaged as one-command installers. Both bootstrap from the same canonical snapshot and ship the same status dashboard — so you can run either (or both, on separate machines), watch how each tracks the chain, and draw your own conclusions.

No verdict from us. We're not labelling one "right" and one "wrong" here — the point is for you to test independently. Each build reports its own live status; compare them against each other and against the public explorer, and see what you find.
Build A
pool / relay line
pool-v6.5.7
  • RuntimeDocker container
  • ModeFollower · --acctmode (accounting)
  • ConsensusFollows heaviest chain from peers
  • BootstrapCanonical snapshot (~9.6 GB), then P2P sync
  • Dashboard127.0.0.1:8092 · EVM RPC :18545

Install · Linux

curl -fsSL https://seed.dvdmining.com/canon-defender/setup-node.sh | EXTERNAL_IP=YOUR-IP bash

Install · Windows (Docker Desktop)

powershell -ExecutionPolicy Bypass -File setup-node.ps1 -ExternalIp YOUR-IP
setup-node.sh setup-node.ps1 docker image (127 MB)
Build B
1.2.0 dev line
1.2.0-rc.8
  • RuntimeNative binary (systemd, no Docker)
  • ModeEnforcing · no --acctmode
  • ConsensusAuthorizedMining + EVM state guard (rejects blocks that fail its guard)
  • BootstrapSame canonical snapshot (~9.6 GB)
  • Dashboard127.0.0.1:8092 · EVM RPC :18545

Install · Linux

curl -fsSL https://seed.dvdmining.com/canon-defender/setup-node-rc8.sh | sudo EXTERNAL_IP=YOUR-IP bash

Install · Windows (Docker Desktop)

curl.exe -fsSL -o setup-node-rc8.ps1 https://seed.dvdmining.com/canon-defender/setup-node-rc8.ps1
powershell -ExecutionPolicy Bypass -File setup-node-rc8.ps1 -ExternalIp YOUR-IP
setup-node-rc8.sh setup-node-rc8.ps1 raw binary (47 MB)

How to compare them

The interesting question is whether the two builds derive the same EVM chain from the same data. To check for yourself:

  1. Install each build on a separate machine (or one at a time). Let it finish bootstrapping.
  2. Open its dashboard at http://127.0.0.1:8092 — it shows the node's EVM head, the canonical tip, and a live hash comparison.
  3. Pull a block hash directly from each and compare:
    curl -s --data '{"jsonrpc":"2.0","id":1,"method":"eth_getBlockByNumber","params":["0xc1d878",false]}' -H content-type:application/json http://127.0.0.1:18545
    (0xc1d878 = block 12,700,000). Do the same against the public explorer's RPC and see if they agree.
  4. Or paste either node's address into the Checker, and find both on the Network Map.

Both builds are the real, unmodified node software (Build B carries one small patch that turns a startup crash into a graceful block-reject — noted for transparency). Bootstrapping downloads ~10 GB, so use a box with room to spare. Found something we didn't? That's the whole idea — tell us what you see.