WelshDAG Node Kit 0.1.0
Check a chain-1404 node, verify BlockDAG Engineering's software before you install it, and learn why each setting exists. Every setting here comes from a failure on our own production pool.
Ships no upstream bytes
It records hashes of BlockDAG Engineering's release. It does not repackage it. You still download their software from them.
Read-only first
welshdag-verify installs nothing and changes nothing. Point it at a node's RPC and read the result.
Know your branch
Two chains share ID 1404 and the same genesis. The kit tells you which one your node follows.
What are you setting up?
Pick the one that matches your situation. The steps below change to match.
Get the kit
Clone it from GitHub, or use the checked download further down.
git clone https://github.com/Welshdag/welshdag-node-kit cd welshdag-node-kit
Run the ten checks
Needs Python 3 and nothing else. Use your own node's RPC address.
./tools/welshdag-verify --rpc http://127.0.0.1:8545
Read any FAIL before changing anything
Each check links to a section of WHY-EACH-SETTING.md, which explains what it prevents. The last three checks are the ones people get wrong.
Download upstream's release from upstream
Get the rc.65.6 pool-stack-docker-…-linux-amd64.zip from BlockDAG Engineering. We do not host it.
Check the archive as downloaded
Upstream publishes per-binary hashes but no archive hash. This one hash in the pin is ours.
./install.sh verify-archive pool-stack-docker-…-linux-amd64.zip
Unpack, then check every binary
Checks all 11 binaries and the ~1 GB image bundle against pins/rc.65.6.json. The pin is generated from upstream's own signed release lock, never typed by hand.
./install.sh verify /path/to/extracted-payload
It refuses to run on an already-installed upstream root. Those carry a hash-verified node.conf, and touching it breaks the next boot.
Verify the upstream software
Follow the “Verify an upstream download” path first. Only continue if every check passes.
Load the images
Runs docker load on the verified bundle. It starts nothing.
./install.sh load /path/to/extracted-payload
Apply the tuned settings
Start from tuning/welshdag.defaults.env. It contains the keys upstream upgrades silently put back, including the 600-second shutdown timeout and transaction inclusion.
Bootstrap from a snapshot
Skip weeks of syncing with the WelshDAG chain snapshot. Restore into an empty data directory, never over a running node. Then run welshdag-verify against the new node.
Get the kit
The same files, two ways. The download is a snapshot of commit dcf24e8, the commit GitHub serves today.
Source archive
welshdag-node-kit-0.1.0.tar.gz
- Size
- 23,054 bytes
- SHA-256
- 9e269b138b2239f816beb6100f4a46fb8b59d5ea73215a3eecaf6e8f60d00b44
- Platform
- Linux (AMD64 / ARM64), Python 3, Docker
From a terminal
Download, check the hash, and unpack. sha256sum -c stops if a single byte differs.
curl -fLO https://downloads.welshdag.co.uk/files/welshdag-node-kit-0.1.0.tar.gz echo "9e269b138b2239f816beb6100f4a46fb8b59d5ea73215a3eecaf6e8f60d00b44 welshdag-node-kit-0.1.0.tar.gz" | sha256sum -c - tar xzf welshdag-node-kit-0.1.0.tar.gz cd welshdag-node-kit-0.1.0
Why each setting exists
This is the real content of the kit. Each item is a failure that happened on a production pool, what it looked like, and the setting that prevents it.
MINING_NO_PENDING_TX means exclude transactions and is on when unset. Every block is empty and you lose every fee.command: alone is not enough.What has been tested
Working, tested on a live host
- welshdag-verify: passes against our node and correctly fails a node on the other branch
- install.sh verify / verify-archive: tested against the real payload; a single flipped byte is caught
- install.sh load: loads the verified image bundle and starts nothing
- Topology resolvers: pick the running node by project and role, never by name
- make-pin.py: generates the pin from upstream's signed lock
Not done yet
- Compose templates and a guided first-run install
- No clean-room install on a fresh host yet. Use
loadand later steps only on a machine you can afford to rebuild. - Not included: the payout engine and the burn. Those are pool-operator tools.
Independent, no warranty
WelshDAG is an independent hobby operation. It is not affiliated with or endorsed by BlockDAG. There is no WelshDAG chain and no WelshDAG coin: this is chain 1404, upstream's software and the BDAG coin. Our code is provided as-is. Running a node is your decision and your risk. Questions? Ask the operator.