Mining Troubleshooting
Mining failures usually come from the wrong algorithm, stale jobs, bad credentials, out-of-sync nodes, malformed AuxPoW commitments, or payout policy misunderstandings.
This page is a checklist. For protocol details, use AuxPoW Integration.
Miner Cannot Connect
Check:
- pool host and port;
stratum+tcp://vs TLS endpoint if the pool requires TLS;- username and worker format;
- firewall and outbound connectivity;
- whether the pool is mainnet or testnet;
- whether the pool is currently in pre-AuxPoW or post-AuxPoW mode.
Shares Are Rejected
| Symptom | Likely cause |
|---|---|
| Wrong algorithm | Miner is using yespower instead of YespowerTIDE, or scrypt against a pre-AuxPoW pool. |
| Low difficulty errors | Miner or proxy is submitting shares for an old job. |
| Duplicate share | Miner retried the same nonce/extranonce combination. |
| Bad extranonce size | Miner and pool disagree on Stratum extranonce handling. |
| Time too old or too new | Miner clock or submitted ntime is outside pool policy. |
Recheck the exact miner command supplied by the pool.
High Stale Rate
- Check network latency to the pool.
- Use a geographically closer endpoint if available.
- Ensure the miner receives new jobs quickly after parent or Tidecoin tip changes.
- Avoid overloaded proxies.
- Compare stale rate across multiple miners to distinguish local from pool-side issues.
AuxPoW Submission Fails
For pool operators:
| Failure | Check |
|---|---|
block hash unknown | Tidecoin candidate cache is stale; refresh createauxblock. |
auxpow-invalid | Coinbase commitment, merkle branch, chain index, or byte order is wrong. |
auxpow-chainid | Block version or parent chain ID conflicts with Tidecoin chain ID 8. |
auxpow-parent-pow | Parent scrypt hash does not meet Tidecoin target. |
auxpow-pre-activation | AuxPoW is not active at that height. |
| RPC transport error | Treat submit status as unknown and reconcile from chain. |
Verify that the parent coinbase contains exactly one fabe6d6d marker and that
it is immediately followed by the aux-chain merkle root.
Payout Is Missing
Pool payouts may wait for:
- coinbase maturity;
- minimum payout threshold;
- batch interval;
- fee policy;
- reorg safety depth;
- manual review if the payout address is malformed or quarantined.
Check the pool’s payout policy and verify your payout address. Do not mine to an exchange deposit address unless the exchange explicitly supports pool payouts to that address.
Node-Side Checks
For a Tidecoin node used by a pool:
tidecoin-cli getblockchaininfo
tidecoin-cli getmininginfo
tidecoin-cli getnetworkinfoFor AuxPoW:
tidecoin-cli createauxblock "<tidecoin-payout-address>"If this command is unavailable, AuxPoW may not be active for the next height or the node may not be synced/connected.
See also: Pool Mining, Miner Software, AuxPoW Integration, Node Troubleshooting.