Skip to main content

Mining Troubleshooting

Use this page when the Mining page is running but the current cycle, commit, claim, or recovery state does not match what you expected. Mining is an operating loop:
Each step has a separate blocker. A healthy Fased Agent can still submit a smaller cycle than the saved target when capital is locked, wallet SOL is low, or recovery is clearing older cycles.

Target max is high, but submitted commit is low

This is usually normal. Target max is the saved upper limit for later cycles. The actual submitted commit is capped by:
  • free miner capital;
  • locked capital from pending cycles;
  • wallet SOL fee reserve;
  • signer fee/rent buffer;
  • minimum-entry and erosion coverage;
  • recovery and claim state.
Common messages: If commit drops for one cycle and returns on the next cycle, Fased Agent likely kept participating with the safe available amount.

Locked capital clearing

Submitted cycle capital is not immediately free. It clears after the cycle is settled, distributed, claimed, and closed where applicable. Expected signs:
  • Locked is non-zero;
  • Withdraw is lower than total capital;
  • Fased Agent may submit a smaller cycle;
  • the claim/recovery worker keeps running;
  • later cycles can restore toward the saved target once capital unlocks.
Do not repeatedly press Stop to accelerate clearing. Stop blocks new submits. It does not make Solana settlement or claim state finish instantly.

Wallet SOL reserve reduced commit

Miner capital is not the same as wallet SOL. The mining wallet still needs SOL outside miner capital for:
  • transaction fees;
  • priority fees when configured;
  • miner-cycle account rent;
  • associated token account rent when needed;
  • retries after blockhash expiry, RPC timeout, or account lock conflict.
If the Mining page reports fee reserve pressure, top up the mining wallet SOL. Do not solve fee reserve problems by depositing all wallet SOL into miner capital.

Missed or skipped cycles

A skipped cycle means Fased Agent did not submit into that cycle from this wallet. Causes include:
  • free capital below minimum entry;
  • locked capital not yet clear;
  • wallet SOL below fee reserve;
  • RPC rate limit or stale state;
  • signer unavailable;
  • gateway restart during a submit window;
  • previous cycle still in a claim/recovery path.
What to check:
If mining is running and later submits resume, a short skipped range is not automatically a protocol failure. A long skipped range with enough free capital and wallet SOL usually points to RPC, signer, or recovery state.

Stop, clearing, and resume

Stop means no new cycle submits. If capital is locked, mining enters clearing:
  • no new submits;
  • claim and recovery can keep running;
  • capital returns as cycles settle and claim;
  • use Resume or Start after clearing when you want new submits again.
If you want to pause new risk but recover funds, use Stop and wait for clearing. If you want mining to continue, do not stop while old cycles are pending.

Claimable SAT is zero

Claim depends on settlement and distribution, not only on submit. Possible reasons:
  • current cycle has not settled yet;
  • distribution pages are still pending;
  • claim already ran;
  • claim backlog is waiting on an older ready cycle;
  • RPC returned stale account state;
  • the wallet is out of fee SOL for claim.
Use Mining history to compare the submitted cycle, settled cycle, claim record, and latest wallet SAT balance.

RPC stale, rate limited, or slow

Mining reads account state frequently. Public RPC can work for light tests, but long-running mining should use a reliable private or commercial RPC. Symptoms:
  • rate limited errors;
  • stale current cycle;
  • failed simulation after a transaction already landed;
  • delayed claim status;
  • missed submit window;
  • endpoint failover messages.
Use Solana RPC setup before serious mining. If the UI looks stale after a claim, refresh once and check history before retrying the same action.

Strategy outcome was not better

Strategy modes control mining decisions. Outcomes vary by cycle, crowding, fees, missed windows, and other miners. A single miner can prove that strategy selection submits valid cycles, but it does not prove one strategy outperforms another. Strategy performance needs multi-miner evidence with equal commits, rotated wallets, and recorded deterministic rebate, performance rebate, score versus benchmark, SAT earned, and net SOL cost.

Quick recovery checklist

  1. Confirm signer health.
  2. Confirm mining wallet SOL is above reserve.
  3. Confirm free miner capital is above minimum entry.
  4. Check pending and locked cycles.
  5. Check claim backlog.
  6. Check RPC rate limit/failover messages.
  7. Restart the gateway only after reading current status.
  8. Let recovery/claim finish before changing wallets or deleting local state.

Interrupted Mining replacement

Retry the exact same fased wallet retire command. The lifecycle reads the signer’s retirement receipt and resumes only the incomplete step. Do not choose a new successor ID during a retry, delete the receipt, reactivate the retired wallet, or manually edit registry assignment. If retirement reports live work, stale evidence, a recoverable balance, a wrong role/genesis, or an unready successor, fix that exact blocker first. The old Mining assignment stays authoritative until signer tombstone and successor readiness are both proven.

Mining

Return to the main Mining page guide.

Advanced mining

Understand capital safety, strategy, claim, sweep, and recovery.

Mining automation

Review chat, task, and strategy automation boundaries.

RPC setup

Configure reliable Solana RPC for long-running mining.