Dogecoin

Endpoint	https://rpc.au.ro/doge
Protocol	dogecoind JSON-RPC over HTTPS (POST)
Network	mainnet
Batch	✓

Dogecoin Core descends from the same bitcoind codebase (via Litecoin), so everything on the Bitcoin page applies verbatim with the /doge path: same methods (getblockchaininfo, getblockcount, getblockhash, getblock, getrawtransaction, sendrawtransaction, …), same 10-line JSON-RPC helper, same offline-signing flow.

Quick test

curl -X POST https://rpc.au.ro/doge \
  -H "apikey: $YOUR_API_KEY" -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"1.0","id":1,"method":"getblockchaininfo","params":[]}'

Dogecoin-specific notes

• Fees are not bitcoin-scale. Dogecoin's default relay/dust rules are denominated in whole DOGE, and estimatesmartfee reflects that — do not reuse a BTC fee heuristic. Query it rather than hardcoding:

  curl -X POST https://rpc.au.ro/doge \
    -H "apikey: $YOUR_API_KEY" -H 'Content-Type: application/json' \
    -d '{"jsonrpc":"1.0","id":1,"method":"estimatesmartfee","params":[6]}'

• ~1-minute blocks (vs Bitcoin's ~10): the same confirmation count is a 10× shorter wall-clock wait, and getblockcount moves ~10× faster — poll and cache accordingly.

• AuxPoW (merged mining with Litecoin): block headers carry an auxpow object. Standard block/tx queries are unaffected; header parsers written strictly against Bitcoin's 80-byte header need to account for it.

• bitcoinjs-lib needs Dogecoin network constants ({ messagePrefix, bech32: undefined, pubKeyHash: 0x1e, scriptHash: 0x16, wif: 0x9e }) — pass them as the network argument. Dogecoin has no bech32/SegWit.

Limitations

Same as Bitcoin: no wallet RPCs, no address index. Historical state is limited by node pruning.