How to Run Your Own Dogecoin Node

Dogecoin Core descends from an older Bitcoin Core base (it versions as 1.14.x, not 0.21/2x), so a few flags and RPCs differ from modern Bitcoin — worth knowing before you copy a Bitcoin config. Dogecoin runs 1-minute blocks (the fastest of the family), has no supply cap (10,000 DOGE per block), and is merge-mined with Litecoin via AuxPoW, so its security rides on Litecoin’s Scrypt hashpower. This is the exact dogecoind setup we run on Ubuntu 24.04.

Hardware & disk requirements

The total chain isn’t huge, but 1-minute blocks mean there are millions of them to validate — so initial sync can feel slower than the size suggests, and an NVMe SSD matters. Budget for ~150 GB with txindex and growing.

Step 1 — Download and verify Dogecoin Core

Get the binary from the official dogecoin/dogecoin releases and check it against the published SHA256SUMS. Set VER to the current release (we run 1.14.9):

VER=1.14.9
cd /tmp
curl -LO https://github.com/dogecoin/dogecoin/releases/download/v$VER/dogecoin-$VER-x86_64-linux-gnu.tar.gz
curl -LO https://github.com/dogecoin/dogecoin/releases/download/v$VER/SHA256SUMS.asc

sha256sum --ignore-missing --check SHA256SUMS.asc
# -> dogecoin-$VER-x86_64-linux-gnu.tar.gz: OK

tar xzf dogecoin-$VER-x86_64-linux-gnu.tar.gz
sudo install -m755 dogecoin-$VER/bin/dogecoind dogecoin-$VER/bin/dogecoin-cli /usr/local/bin/
dogecoind --version | head -1

Step 2 — Dedicated user, data dir, and config

sudo useradd --system --no-create-home --shell /usr/sbin/nologin dogecoin
sudo mkdir -p /var/lib/dogecoin /etc/dogecoin
sudo chown dogecoin:dogecoin /var/lib/dogecoin
openssl rand -hex 32   # <- use as rpcpassword below

Create /etc/dogecoin/dogecoin.conf. Dogecoin’s default RPC port is 22555 (P2P is 22556). Because it’s an older Core base, stick to the well-supported options below — newer Bitcoin Core flags (descriptor wallets, some -rpc tunables) may not exist here:

server=1
disablewallet=1
txindex=1
prune=0

dbcache=1024
maxmempool=300
listen=1
maxconnections=64

rpcbind=127.0.0.1
rpcallowip=127.0.0.1
rpcport=22555
rpcuser=dogecoin
rpcpassword=<PASTE_THE_GENERATED_PASSWORD>
rpcthreads=8
rpcworkqueue=64

datadir=/var/lib/dogecoin

# ZMQ feeds (only needed for an indexer like Blockbook):
zmqpubhashblock=tcp://127.0.0.1:38332
zmqpubrawblock=tcp://127.0.0.1:38332
zmqpubhashtx=tcp://127.0.0.1:38332
zmqpubrawtx=tcp://127.0.0.1:38332

Lock down the config so the dogecoin user can still read it:

sudo chown -R root:dogecoin /etc/dogecoin
sudo chmod 750 /etc/dogecoin && sudo chmod 640 /etc/dogecoin/dogecoin.conf

Step 3 — systemd service

[Unit]
Description=Dogecoin Core daemon
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=dogecoin
Group=dogecoin
ExecStart=/usr/local/bin/dogecoind -conf=/etc/dogecoin/dogecoin.conf
Restart=on-failure
RestartSec=10
TimeoutStartSec=infinity
TimeoutStopSec=300
PrivateTmp=true
NoNewPrivileges=true

[Install]
WantedBy=multi-user.target

Step 4 — Start and watch the sync

sudo systemctl daemon-reload
sudo systemctl enable --now dogecoind

dogecoin-cli -conf=/etc/dogecoin/dogecoin.conf getblockchaininfo \
  | grep -E '"blocks"|"headers"|"verificationprogress"|"size_on_disk"'
dogecoin-cli -conf=/etc/dogecoin/dogecoin.conf getblockcount

Don’t be alarmed that blocks climbs far slower than the millions of headers early on — with 1-minute blocks there’s simply a lot to process. When verificationprogress reaches 0.9999… you’re at the tip — point your apps at http://127.0.0.1:22555.

Step 5 (optional) — Address-indexed API with Blockbook

As with the rest of the family, dogecoind has no address index — for address balances, full history, xpub scanning, and a REST/WebSocket API you need a separate indexer. Blockbook supports Dogecoin; it reads from your synced dogecoind over RPC + the ZMQ feeds and builds its own index. The mechanics — runtime libraries, the systemd unit, and the OOM-guardrail drop-in that stops a mid-build kill from corrupting the index — are identical to the Bitcoin guide’s Blockbook section.

The honest part: what running it actually costs

• The older Core base bites. Dogecoin Core lags modern Bitcoin Core, so you’ll hit missing flags/RPCs and have to track its own (slower) release cadence and consensus changes.
• Address queries need a second system. The index is another ~150 GB and its own sync, and it reindexes from scratch if it’s ever OOM-killed mid-write.
• One node is a single point of failure. Real uptime means redundancy + a load balancer — and it’s rarely just Dogecoin you need; every chain is another full stack.
• The real bill is engineer-hours, not the server — see Self-Hosted Node vs RPC Provider.