Skip to main content

Set up merged mining

To add Syscoin to a Bitcoin pool, the template server requests a candidate from Core v5.1.3 and includes two commitments in the parent coinbase. When a miner finds a header that meets the Syscoin target, the pool submits the auxiliary proof to the Core node that issued the candidate. How Core validates merged work

Prepare the template node​

Use the platform release of Core v5.1.3 with its matching managed sysgeth v5.1.0. Give the pool's template server private local RPC access. Wait until Core and NEVM have caught up, verify the network and current tip, and confirm that the pool's Syscoin payout address belongs to that network. Use the release's normal Core configuration. If the pool configures a distinct NEVM beneficiary, verify the configured recipient on an accepted NEVM block. With the bundled sysgeth v5.1.0, set gethcommandline=--miner.etherbase=YOUR_NEVM_ADDRESS in syscoin.conf, replacing YOUR_NEVM_ADDRESS with the pool’s NEVM address. The release still uses this flag for actual Syscoin block building even though the flag is marked deprecated. Core release notes · Managed client fee-recipient option

syscoin-cli getblockchaininfo
syscoin-cli getnevmblockchaininfo
syscoin-cli help createauxblock
syscoin-cli help submitauxblock

Build and submit a job​

  1. Request work with the pool's Syscoin payout address.

    syscoin-cli createauxblock "$SYS_PAYOUT_ADDRESS"
  2. Record the returned candidate hash, chainid, height, previousblockhash, target bits, and coinbasescript together. The bits field is the compact Syscoin target. The response also includes a deprecated _target field in reversed byte order.

  3. Add the candidate hash to the auxiliary-chain Merkle tree and commit to the resulting root in the parent coinbase input script. Add the returned coinbasescript as the script for a separate, zero-valued parent coinbase output. It contains Core's expected sys reference for this template. Build the parent transaction Merkle root after both changes.

  4. Retain the candidate hash, parent coinbase, both Merkle branches and their indices, and the solved parent header to serialize the CAuxPow proof. If the header meets the Syscoin target, submit the proof to the Core node that created the candidate. Evaluate Bitcoin acceptance independently against the Bitcoin target.

    syscoin-cli submitauxblock "$SYS_TEMPLATE_HASH" "$SERIALIZED_AUXPOW"

When the Syscoin tip changes, fetch fresh work and replace the template's proof inputs and reference output together. Treat a Core restart as a template refresh too. If the pool has redundant backends, monitor the candidate origin per worker. Core stores the candidate locally, and a solver can otherwise send the proof to a backend that has never seen that candidate. Mining RPC definitions · Template cache and reference builder · AuxPoW serialization

Confirm accepted work​

The Syscoin AuxPoW mining dashboard shows indexed pool activity, estimated shares of Syscoin blocks over several time windows, and Bitcoin-side commitment counts. Its JSON endpoint also reports the indexed Syscoin height.

curl --fail --silent --show-error https://status-api.syscoin.org/mining |
jq '{as_of_utxo_height, pools: [.miners[] |
{name, last_syscoin_block, share_24h, share_7d, share_30d, syscoin_commitments}]}'

Pool shares here describe indexed Syscoin production. Use Core and actual Bitcoin headers when you need direct evidence for an individual accepted block or coinbase reference.

syscoin-cli getblockhash "$SYS_BLOCK_HEIGHT"
syscoin-cli getblock "$SYS_BLOCK_HASH" 1

Verify the active block hash at the submitted height and inspect its auxpow object. For a job also mined on Bitcoin, match the hash of the attached parent header against the Bitcoin block hash. The visible sys output references an ancestor, so it can repeat across several valid jobs. A persistent mismatch calls for comparing the output in each worker's dispatched job with that worker's current createauxblock response. Accepted-block test · Core RPC reference