Skip to content

Merge Mining (AuxPoW)

Soqucoin supports Auxiliary Proof-of-Work (AuxPoW). Litecoin and Dogecoin miners can mine SOQ simultaneously at zero additional hardware or electricity cost.

How It Works

┌──────────────┐     ┌──────────────────┐     ┌──────────────────┐
│  Your Miner  │────▶│   LTC/DOGE Pool  │────▶│  Soqucoin Node   │
│  (Scrypt)    │     │  (Parent Chain)  │     │  (Child Chain)   │
└──────────────┘     └──────────────────┘     └──────────────────┘
                              │
                    Creates AuxPoW proof
                    valid for both chains
  1. Your miner solves Scrypt work for Litecoin or Dogecoin (the "parent chain")
  2. The pool includes Soqucoin's block template in the parent chain's coinbase transaction
  3. When a block is found, the proof validates on both chains
  4. You earn LTC/DOGE and SOQ from the same work

No additional hardware, no extra electricity, no firmware changes. AuxPoW is active from genesis.

For Miners

SOQUPOOL merge-mines SOQ with LTC and DOGE and pays all three from a single stratum connection. Other pools that merge-mine SOQ pay it out the same way.

Pool mining setup →

For Pool Operators

SOQ merge-mines through AuxPoW in the Dogecoin format. The pool integration guide in the soqucoin repository is the reference for a pool that adds SOQ; questions go to dev@soqu.org.

For reference, Soqucoin's AuxPoW chain ID is 0x5351 (decimal 21329). Strict chain-ID checking is enforced on mainnet, testnet, and regtest (fStrictChainId = true; stagenet does not enforce it), so on those networks the parent (LTC/DOGE) block must not itself carry chain ID 0x5351.

A SOQ block that spends ordinary sq1p outputs carries a PAT block attestation in its coinbase when the node assembled the coinbase, or when your pool copied the commitment output from the template's coinbasetxn. A coinbase built from getblocktemplate fields alone carries none; such blocks are valid today and will be rejected from a height a future release announces. Take your SOQ block from createauxblock, as SOQUPOOL does, or follow the block attestation section of the pool integration guide, which covers each template path and a check you can run on your own blocks.