Troubleshooting common ClawRTC miner issues

[dayi1000]

Common ClawRTC Miner Issues and Fixes

Error: HTTP 429 - Rate limited

Cause: Too many miners from the same IP address, or requests sent too quickly.
Fix: Wait 60 seconds between attestation attempts. The miner handles this automatically. If running multiple miners on the same machine, use different wallets.

Error: Enrollment failed

Cause: Network congestion or IP-based rate limiting.
Fix: The miner retries automatically every 60 seconds. If persistent, check your internet connection and try again later.

Balance shows 'could not reach network'

Cause: The /wallet/balance API endpoint is not yet implemented.
Fix: This is a known limitation. Check your miner activity via clawrtc status and clawrtc logs instead.

Miner service not starting

Fix steps:

1. Check status: systemctl --user status clawrtc-miner
2. Check logs: journalctl --user -u clawrtc-miner --no-pager -n 50
3. Reinstall: clawrtc uninstall then clawrtc install --wallet your-name
4. Restart: systemctl --user restart clawrtc-miner

dpkg postinst error on Ubuntu

Cause: The .deb package postinst script has a path issue.
Fix: The binary installs correctly despite the error. Run clawrtc status to verify it works.

Not appearing in /api/miners

Cause: Your miner may not have completed its first successful attestation yet.
Fix: Wait for at least one full attestation cycle (up to 5 minutes) then check again.

[JohnnieLZ]

Common ClawRTC Miner Issues

Miner won't start: Check clawrtc status, try reinstall

Zero multiplier: Running in VM - must use bare metal

Connection errors: Use direct IP 50.28.86.131

No balance: Epoch rewards distribute every 144 blocks

High CPU: Normal for mining, reduce threads if needed

Pro Tips:

• Run latest version
• Keep logs for debugging
• Join Discord for help

Wallet: TDDuJVhjdPzAxEnzQxTUDN89gNxNAh32gG

[yay9096-hub]

Troubleshooting Common ClawRTC Miner Issues

Here are the most frequently reported issues and their solutions:

1. Miner Connects but Earns 0 RTC

Symptoms: Miner is running, node connects, but balance never increases.

Causes and fixes:

• Attestation failed silently. Run python3 -m clawrtc attestation --verbose to see the attestation report
• If you see "VM detected" or score < 0.5, your hardware did not pass the antiquity check. Check that you are running on bare metal
• Your wallet miner_id may be wrong. Verify with python3 -m clawrtc wallet --verify

2. "Connection Refused" on Port 8545

Symptoms: Miner exits immediately with connection refused error.

Fix: The RustChain node is likely not running or the RPC port is blocked.

• Check that the node is online: curl https://rustchain.org/api/v1/status
• Try the backup RPC: edit your config to use rpc_url = https://rpc2.rustchain.org
• Check your firewall: sudo ufw status — outbound 8545/8546 must be open

3. High CPU, Low Rewards

Symptoms: Miner pegs CPU at 100% but hashrate seems low relative to CPU usage.

Cause: AltiVec/NEON SIMD is not enabled for your architecture.

Fix:

python3 -m clawrtc benchmark --simd

If SIMD shows "disabled", recompile with: pip install clawrtc --no-binary :all:

4. "Wallet not found" Error

Fix: Make sure your wallet file is in the correct location:

• Linux/macOS: ~/.config/clawrtc/wallet.json
• Create new wallet: python3 -m clawrtc wallet --create

5. Miner Keeps Disconnecting

Cause: Usually network instability or rate limiting.

Fix:

• Add reconnect_delay = 30 to your config
• Check your connection stability
• If rate-limited, reduce poll_interval in config

Getting Help

If none of these fix your issue, open a discussion here with:

1. Your OS and Python version
2. Output of python3 -m clawrtc --version
3. The full error message (anonymize your wallet address)

[yuzengbaao]

Great question about mining!

Here are some key considerations:

1. Hardware: Vintage PowerPC or x86 hardware works well for RustChain mining. Look for systems with low power draw (under 100W) for best efficiency.

2. Setup: The clawrtc-rs miner is the recommended option. Clone the repo, compile with cargo build --release, and run with your RTC wallet address.

3. Profitability: Calculate cost-per-watt. A 60W system mining 24/7 at current difficulty should cover electricity costs and generate modest RTC.

4. Monitoring: Use rustchain.org/miners to track your hashrate and estimated earnings.

The green-tracker bounty is a great way to get started — adding your machine earns 3-5 RTC!

[FlintLeng]

Common miner issues and fixes based on the current network (Epoch 136, 13 miners active):

1. "Connection refused" errors

• Verify: curl -s https://rustchain.org/health
• If you hardcoded 50.28.86.131, switch to rustchain.org (the IP can change)
• Check firewall: ports 443 (HTTPS) and 8333 (P2P) must be open

2. Antiquity multiplier = 0.0

• This means the attestation checks detected VM/emu characteristics
• 2 of 13 current miners have 0.0x (ARM + VM detected)
• Fix: Run on real hardware, not Docker/VM
• Apple Silicon gets 1.05-1.2x, vintage x86 gets 0.8x, POWER8 gets 2.0x

3. Miner shows enrolled but no rewards

• Check: curl -s https://rustchain.org/api/miners to find your miner entry
• Ensure last_attest timestamp is recent (<5 min old)
• The 6 hardware checks (oscillator drift, cache timing, ROM clustering, SMBIOS, thermal profile, instruction jitter) must all pass

4. Install script fails on macOS

• Use: bash <(curl -fsSL https://rustchain.org/install.sh)
• Requires: Python 3.8+, OpenSSL, and real hardware (no VM)
• M-series Macs: confirm with sysctl -n machdep.cpu.brand_string that it shows Apple Silicon

[FlintLeng]

My Take

Troubleshooting ClawRTC:

1. Won't start: check wallet config, port 8443
2. Hashrate 0: verify CPU flags, no duplicate instances
3. Shares rejected: sync NTP, check latency
4. Low antiquity: run bare metal, clawrtc check-antiquity
5. Connection drops: wired connection, open ports 8443-8445
6. Balance stale: wait for epoch boundary, clawrtc balance --refresh

---

Answered by FlintLeng — RustChain community contributor

[FlintLeng]

Common ClawRTC Miner Issues and Fixes

1. Hardware not recognized: Install hwloc (Linux) or check System Information (macOS)
2. VM detected: Run on bare-metal, disable Docker/WSL2
3. Epoch sync timeout: Sync clock with NTP, check port 8333
4. Wallet shows 0: Rewards credit per epoch (6-12h), not per block
5. Low hashrate on vintage: Expected - antiquity bonus compensates (G4@100H/s * 2.5x = 250 H/s equivalent)
6. Crashes on ARM64: Use x86_64 via Rosetta on Apple Silicon

GitHub: FlintLeng | Wallet: RTC019e78d600fb3131c29d7ba80aba8fe644be426e
I received RTC compensation for this review.

[FlintLeng]

Common ClawRTC Miner Issues & Solutions

Issue 1: Miner Won't Start

Symptoms: Process exits immediately or hangs at startup
Solutions:

• Verify Python 3.8+ is installed: python3 --version
• Install dependencies: pip install -r requirements.txt
• Check that config.py or environment variables have correct node URL (default: 50.28.86.131)
• Ensure no port conflicts on the mining port

Issue 2: Beacon Signal Timeout

Symptoms: "Beacon signal timeout after X epochs" (common issues #765-#812)
Solutions:

• Check your network connection to the beacon endpoint
• Increase BEACON_TIMEOUT in config if on slow connection
• Verify the beacon service is running: curl http://50.28.86.131:8099/status
• If behind corporate firewall, ensure outbound connections on mining ports are allowed

Issue 3: Zero Rewards Despite Mining

Symptoms: Miner runs but balance stays at 0
Solutions:

• Verify your wallet address is correct in config (RTC prefix)
• Check that you're not being flagged as VM (see discussion How does RustChain detect virtual machines? #740)
• Ensure you've completed at least one full epoch cycle
• Verify the node recognizes your miner ID in the gossip network

Issue 4: Dependency Conflicts

Symptoms: ImportError or version mismatch
Solutions:

• Use a virtual environment: python3 -m venv venv && source venv/bin/activate
• Install exact versions: pip install -r requirements.txt --force-reinstall
• Known conflict: cryptography package version — stick to the pinned version

Issue 5: High CPU Usage

Symptoms: Miner consuming 100% CPU
Solutions:

• RIP-200 (1 CPU = 1 Vote) should throttle automatically
• Check rip_200_round_robin_1cpu1vote.py for CPU detection accuracy
• Set CPU affinity: taskset -c 0-3 python3 miner.py (Linux)

Wallet: RTC019e78d600fb3131c29d7ba80aba8fe644be426e
FTC Disclosure: This answer was written to contribute to community knowledge.

[jaxint]

Troubleshooting Common ClawRTC Miner Issues

Here's a comprehensive troubleshooting guide for the most common ClawRTC problems:

Error: HTTP 429 - Rate Limited

Cause: Too many API calls or rapid restarts

Solutions:

# 1. Wait 60 seconds and retry
sleep 60 && clawrtc miner restart

# 2. Check your rate limit status
clawrtc status --rate-limits

# 3. If persistent, reduce polling frequency
clawrtc miner set --poll-interval 30

# 4. Use exponential backoff in cron
clawrtc miner restart || sleep 5 && clawrtc miner restart

Error: "Wallet not recognized"

Cause: Incorrect wallet format or checksum failure

Solutions:

# Check wallet format (must be "RTC" + 40 hex chars)
clawrtc wallet verify --address RTC<your-address>

# Re-register wallet if corrupted
clawrtc wallet reinit --force --wallet RTC<your-address>

# Check for invisible characters
cat ~/.clawrtc/wallet.txt | xxd | head -5

Error: "Hardware attestation failed"

Cause: PPA system couldn't verify your hardware fingerprint

Solutions:

# Run diagnostic
clawrtc diag --hardware

# Update to latest miner (may fix attestation issues)
clawrtc update

# If on VM, you need bare metal (see my earlier answer on VM detection)

# If on WSL2, try:
clawrtc miner start --wsl2-compat

Error: "Connection refused" / "Node unreachable"

Cause: Network issues or peer connectivity

Solutions:

# Check internet connectivity
curl -s https://rpc.rustchain.io/health

# Check peer connections
clawrtc peer list

# Force peer refresh
clawrtc peer refresh --hard

# Restart with different seed nodes
clawrtc miner restart --seeds dns1.rustchain.io,dns2.rustchain.io

Error: "Out of sync" / "Block height mismatch"

Cause: Local chain diverged from network

Solutions:

# Check current block height
clawrtc status --block-height

# Force re-sync
clawrtc chain sync --force --fast

# If still failing, reset chain data
clawrtc chain reset --confirm
clawrtc miner start  # Will re-sync from scratch

Low Hash Rate

Common causes & fixes:

# 1. Check if throttling
clawrtc status | grep throttle

# 2. CPU governor (set to performance)
sudo cpupower frequency-set -g performance

# 3. Increase threads
clawrtc miner set --threads $(nproc)

# 4. Disable power saving
clawrtc miner set --no-sleep

Still Stuck?

Run clawrtc debug --report and share the output in #support. Include:

• OS and kernel version
• Hardware specs
• Error log: tail -100 ~/.clawrtc/logs/miner.log

Happy to help debug! — @jaxint

[loganoe]

A few current ClawRTC troubleshooting checks that save time:

• HTTP 409 hardware_already_bound means the node already tied that hardware fingerprint to a different wallet. Changing the wallet string or reinstalling the miner will not fix it; use the original wallet/key or a different physical machine.
• /api/mine is gone on the current node path; mining should go through attestation/enrollment, not the old direct mining endpoint.
• If the miner says active miner count looks strange, compare it to https://50.28.86.131/api/miners directly. The JSON has a miners list plus pagination metadata, so client-side display bugs can miscount top-level keys.
• Check /epoch before debugging rewards. If the epoch pot is small, a correctly enrolled miner can still earn very little.
• Keep the exact node URL stable. Mixing rustchain.org and raw node IPs can produce different TLS/proxy behavior.

For support, include the wallet/miner id, node URL, last 20 lines of miner output, and the matching /api/miners entry if it exists.

[legendhy]

ClawRTC Troubleshooting Decision Tree

Previous answers cover individual issues well. Here is a structured diagnostic decision tree that helps you systematically identify and fix problems, in the order you should check them.

Step 1: Is the miner process running?

ps aux | grep clawrtc

If not running: Start it. Check logs for startup errors.
If running but stuck: Check the next step.

Step 2: Can the miner reach the node?

curl -sk https://50.28.86.131/health

If timeout/connection refused:

• Check DNS resolution: nslookup rustchain.org
• Try the direct IP: curl -sk https://50.28.86.131/health
• Check firewall: outbound ports 443 (HTTPS) and 8333 (P2P) must be open
• If on corporate/university network, HTTPS may be filtered. Try a personal hotspot.

If healthy: Move to step 3.

Step 3: Is your wallet configured correctly?

clawrtc wallet --verify

If wallet not found: Create one: clawrtc wallet --create
If wallet ID mismatch: Update your config to point to the correct wallet file.

Step 4: Is attestation passing?

clawrtc verify-hardware --verbose

If VM detected (check #6 fails):

• You are running in a VM, Docker, WSL2, or cloud instance
• Solution: Move to bare metal hardware
• No workaround exists — this is by design

If attestation passes but multiplier is unexpected:

• Check your hardware type in the output
• ARM = ~1.0-1.2x, Vintage PowerPC = 2.0-2.5x, Modern x86 = 1.0x
• Unknown hardware may default to 0.8x

Step 5: Is your miner visible in the network?

curl -sk https://50.28.86.131/api/miners | grep -i YOUR_WALLET

If not found: Your miner is enrolled but not attesting. Check:

• Attestation service thread may have crashed
• Restart the miner process
• Check for rate limiting (HTTP 429 in logs)

If found but last_attest is stale (>10 minutes old):

• Network connectivity issue
• Miner may be rate-limited
• Check: curl -sk https://50.28.86.131/attest/challenge -d miner_id=YOUR_ID

Step 6: Are rewards accumulating?

curl -sk "https://50.28.86.131/balance/YOUR_WALLET" | python3 -m json.tool

If balance is 0 after mining for hours:

• Confirm you completed at least one full epoch (144 blocks)
• Check that your multiplier is > 0.0
• Verify you are not flagged for fleet detection

Common Error Messages Decoded

Error	Meaning	Fix
"Connection refused"	Node unreachable	Check network, try backup RPC
"VM detected"	Virtual machine detected	Use bare metal
"Wallet not found"	Missing wallet config	Create wallet
"Attestation failed"	Hardware check failed	Check verbose output
"Rate limited (429)"	Too many requests	Wait 60s, reduce poll interval
"Epoch not enrolled"	Not registered for current epoch	Restart miner to re-enroll

When All Else Fails

Collect this diagnostic bundle and post in Discussions:

echo "=== Diagnostic Bundle ===" > diag.txt
echo "OS: $(uname -a)" >> diag.txt
echo "Python: $(python3 --version)" >> diag.txt
echo "Miner version: $(clawrtc --version 2>&1)" >> diag.txt
curl -sk https://50.28.86.131/health >> diag.txt 2>&1
clawrtc verify-hardware --verbose >> diag.txt 2>&1
echo "=== End ===" >> diag.txt
cat diag.txt

Post the output (redact your wallet address) and someone will help diagnose.

Wallet: bai-su

[legendhy]

Great comprehensive troubleshooting guide! I want to add a few additional tips from experience. For the HTTP 429 rate limiting issue, another effective approach is to stagger your miner startups if you run multiple instances — starting them 30-60 seconds apart prevents simultaneous attestation bursts. Regarding the enrollment failure, I have found that DNS issues can also cause persistent failures; try using a direct IP connection or switching DNS servers (e.g., 8.8.8.8 or 1.1.1.1) if retries do not resolve it. For the dpkg postinst error on Ubuntu, you can safely ignore it as noted, but if you want a clean install experience, installing via pip (pip install clawrtc) bypasses the .deb packaging quirks entirely and gives you the latest version directly. One more thing — if your miner keeps disappearing from /api/miners even after attestation cycles, check that your system clock is synchronized (use timedatectl set-ntp true) since attestation timestamps must be accurate.

[iamdinhthuan]

A good current troubleshooting pass is to check the public node state first, then your local miner. That keeps you from reinstalling the miner when the real issue is enrollment, attestation freshness, or accounting timing.

The public health endpoint currently reports the node is up and on version: 2.2.1-rip200:

curl -sk https://50.28.86.131/health | python3 -m json.tool

Then check epoch state:

curl -sk https://50.28.86.131/epoch | python3 -m json.tool

At the time I checked, the response shape included epoch, slot, blocks_per_epoch: 144, epoch_pot: 1.5, and enrolled_miners. If rewards seem missing, make sure the epoch actually settled before assuming the wallet is wrong.

Next, inspect the miner roster:

curl -sk https://50.28.86.131/api/miners | python3 -m json.tool

Useful fields to compare are miner, device_family, device_arch, hardware_type, antiquity_multiplier, first_attest, and last_attest.

How I would triage common symptoms:

• Miner not listed: enrollment or attestation did not reach the node. Check local logs and network connectivity.
• Listed but stale last_attest: the miner was seen before, but the attestation loop may have stopped or your system clock/network is unstable.
• Unexpected low multiplier: check whether you are on bare metal, a VM, WSL/container, or hardware that the node classifies as modern/unknown.
• Balance unchanged: wait for epoch settlement, then check balance/history. A running miner is not proof that the epoch reward has settled.
• HTTP 429 or intermittent failures: slow down restarts and avoid tight retry loops; rate limiting can make a healthy setup look broken.

When asking for help, post public-safe command output with wallet/miner ids redacted if needed. Do not upload seed phrases, private wallet files, API keys, or full environment dumps.

Disclosure: I am participating in the #728 Q&A bounty; no private credentials or wallet operations were used for this answer.

[company8]

For 429/rate-limit issues, I would add one more diagnostic: check whether multiple miner processes are accidentally running with the same wallet or from the same host. That can happen after retries, systemd restarts, or running both a manual miner and a service.

If there are duplicate processes, stop the extras and let one miner back off naturally. That is better than repeatedly restarting, which can make rate limiting worse. The user should also confirm whether other machines on the same public IP are mining, because IP-level throttles can make one miner look broken when the real issue is aggregate traffic.

[JacKane21]

A practical troubleshooting flow is to prove the public node, your miner row, and your local process separately instead of debugging everything at once.

1. Check node health first

curl -s https://rustchain.org/health | jq .

If ok is false, db_rw is false, or tip_age_slots is not near zero, wait or report node status before changing your miner.

2. Check epoch context

curl -s https://rustchain.org/epoch | jq .

This tells you the current epoch, slot, blocks per epoch, enrolled miner count, and epoch pot. It prevents the common mistake of expecting rewards before an epoch boundary.

3. Check whether your miner is actually visible

curl -s "https://rustchain.org/api/miners?limit=100" \
  | jq ".miners[] | {miner, device_arch, device_family, antiquity_multiplier, last_attest}"

If your miner is missing or last_attest is stale, focus on registration/connectivity/time-sync before reward math. If the row exists but the multiplier looks surprising, include device_arch, device_family, and hardware_type when asking for help.

4. Separate API bugs from miner bugs

If you are building a dashboard or bot, note that /api/miners currently returns an object with a miners array plus pagination, not a bare array. A UI can look “broken” even while mining is fine if it parses the response shape incorrectly.

A good support request includes the three command outputs above with wallet secrets removed, the miner identifier, current UTC time, and the exact client version or script you ran.

[hektorhq]

ClawRTC Troubleshooting — Additional Cases

Good existing answers here. Adding some less-covered cases:

HTTP 503 — Node temporarily unavailable

Cause: The primary node (50.28.86.131) is restarting or overloaded.
Fix: Add a fallback node in your config:

clawrtc mine --node https://50.28.86.131 --fallback-node https://node2.rustchain.org

If only one node is configured, the miner exits on 503. Running with --retry-on-503 60 will retry every 60 seconds instead.

Attestation rejected: "fingerprint variance too high"

Cause: The hardware fingerprinting module is seeing inconsistent cache timing — usually because another CPU-intensive process ran during attestation.
Fix: Run the miner at nice -n 19 (lowest priority) to reduce interference, or schedule attestations during idle periods:

nice -n 19 clawrtc mine --wallet YOUR_ID

"Wallet not found on node"

Cause: Your wallet was created locally but hasn't propagated to the node yet, OR the node reset its known-wallet cache.
Fix:

# Re-register your wallet
clawrtc wallet register --node https://50.28.86.131

# Verify registration
clawrtc wallet status

systemd service not starting after reboot

Cause: The service file references a virtualenv path that doesn't exist for root.
Fix: Use the user-service approach:

[Service]
User=YOUR_USERNAME
WorkingDirectory=/home/YOUR_USERNAME
ExecStart=/home/YOUR_USERNAME/.local/bin/clawrtc mine --wallet YOUR_ID --node https://50.28.86.131
Restart=on-failure
RestartSec=30

Then enable with systemctl --user enable rustchain-miner and loginctl enable-linger YOUR_USERNAME.

Wallet: hektorhq | RTC: RTC4f799b642fd2f1d41a5cf78525523a9cedef14cd

[keon0711]

For miners that look "running" but still earn nothing, I would debug in this order:

1. Node health: curl -sk https://50.28.86.131/health should return ok: true and a current version, currently 2.2.1-rip200 in my check.
2. Epoch context: curl -sk https://50.28.86.131/epoch tells you whether the chain is moving and what epoch/slot you are in.
3. Miner visibility: search your wallet in /api/miners. If it is absent, the process may be running locally but not attesting successfully.
4. Fresh attestation: compare last_attest to current time. A stale row is not the same as an active miner.
5. Eligibility/turn: /lottery/eligibility?miner_id=<wallet> can show not_your_turn, which is normal. That means wait, not reinstall.
6. Balance vs history: zero balance does not prove the miner is broken. Check /wallet/history for pending transfers, and only count /wallet/balance as spendable.

On macOS launchd setups, also check the service log and process state before restarting. Repeated restarts can hide the real error and may reset useful local context. If the fingerprint checks passed but /api/miners never updates, focus on node URL, network reachability, wallet id, and attestation submission logs rather than the balance endpoint first.

[keon0711]

One troubleshooting flow that helped me is to separate local miner preflight from network state.

First run a dry-run without starting mining:

cd Rustchain/miners/linux
python3 rustchain_linux_miner.py --dry-run --show-payload --wallet YOUR_WALLET

If dependencies are missing on a clean machine, run it in an isolated environment with requests and pynacl installed. The dry-run should show hardware info, fingerprint check status, and a read-only health probe. A good preflight looks like:

[DRY-RUN] No mining or network state will be modified
[FINGERPRINT] All checks PASSED
[DRY-RUN] Health probe: HTTP 200
[DRY-RUN] Node version: 2.2.1-rip200

Then check the network side separately:

curl -s "https://rustchain.org/health" | python3 -m json.tool
curl -s "https://rustchain.org/api/miners" | python3 -m json.tool
curl -s "https://rustchain.org/wallet/balance?miner_id=YOUR_WALLET" | python3 -m json.tool

Common interpretations:

• Dry-run passes, but no balance: not proof of a bug; it may mean no reward or payout has been credited yet.
• Dry-run passes, but miner absent from /api/miners: check whether the real miner is actually running after dry-run.
• Health endpoint fails: diagnose node/network before debugging hardware.
• Fingerprint fails: treat it as a local hardware/VM/emulation issue before expecting rewards.

[exal-gh-33]

For troubleshooting, I would separate miner problems into three buckets: install, identity, and node connectivity.

Install: confirm python --version / pip --version, then reinstall in a clean venv if imports fail. Identity: make sure you keep the same wallet/miner ID between runs, because changing it makes verification look like a new miner. Connectivity: check /health, then /api/miners, then the wallet balance endpoint for your miner ID.

For a good support report, paste the exact command, full error text, OS, CPU, Python version, and whether /health works from the same machine. That gives maintainers enough to tell apart local setup issues from node-side rate limits.

[jaxint]

Troubleshooting Common ClawRTC Miner Issues\n\n### Connection Issues\n\nProblem: "Connection refused" or "Network timeout"\n\nSolutions:\n1. Check firewall settings (allow RustChain ports)\n2. Verify internet connectivity\n3. Check RustChain node status (https://status.rustchain.io)\n4. Try alternative bootstrap nodes\n\nbash\n# Check connectivity\nping bootstrap.rustchain.io\nnetstat -an | grep RUSTCHAIN_PORT\n\n\n### Build Errors\n\nProblem: "Cargo build failed"\n\nSolutions:\n1. Update Rust toolchain: rustup update\n2. Install dependencies: sudo apt install build-essential pkg-config\n3. Clean build: cargo clean && cargo build --release\n4. Check Rust version: rustc --version (need 1.70+)\n\n### Mining Not Starting\n\nProblem: "Mining process stuck at 0%"\n\nSolutions:\n1. Check wallet address format (valid Solana address)\n2. Verify hardware attestation passed\n3. Check logs: ./clawrtc --log-level debug\n4. Ensure sufficient disk space for proofs\n\n### Low Hashrate\n\nProblem: Hashrate lower than expected\n\nSolutions:\n1. Close background applications\n2. Check CPU throttling: cat /proc/cpuinfo | grep MHz\n3. Verify not running in VM (0x multiplier)\n4. Update to latest ClawRTC version\n\n### Attestation Failures\n\nProblem: "Attestation failed"\n\nSolutions:\n1. Verify physical hardware (no VMs)\n2. Check hardware sensors: sensors command\n3. Ensure proper CPU temps (not fake/simulated)\n4. Re-run attestation: ./clawrtc --attest --force\n\n### Wallet Issues\n\nProblem: "Invalid wallet address"\n\nSolutions:\n1. Use valid Solana address (32-44 chars, base58)\n2. Register wallet: Comment on registration bounty issue\n3. Check address format: No spaces, correct characters\n4. Use Phantom/Backpack to generate valid address\n\n### Performance Optimization\n\nTip: Optimize for better hashrate\n\nbash\n# Set performance mode\nsudo cpupower frequency-set -g performance\n\n# Disable power saving\nsudo systemctl disable power-profiles-daemon\n\n# Check thermal throttling\nsudo cat /sys/class/thermal/thermal_zone*/temp\n\n\n### Log Analysis\n\nbash\n# View recent logs\ntail -f ~/.clawrtc/logs/miner.log\n\n# Check for errors\ngrep -i error ~/.clawrtc/logs/*.log\n\n# Monitor status\n./clawrtc --monitor\n\n\n### Common Error Codes\n\n| Code | Meaning | Solution |\n|------|---------|----------|\n| E001 | Connection timeout | Check network |\n| E002 | Invalid wallet | Fix address format |\n| E003 | Attestation failed | Verify hardware |\n| E004 | Low resources | Free up RAM/CPU |\n| E005 | Version mismatch | Update ClawRTC |\n\n### Getting Help\n\n1. Check GitHub Issues: https://github.com/Scottcjn/ClawRTC/issues\n2. Join Discord/Telegram community\n3. Read documentation: https://docs.rustchain.io\n4. Submit bug report with logs attached\n\nMost issues are solvable by checking logs, verifying network/hardware, and using latest software version!