Bug: Miner status command shows incorrect attestation count

[jojo-771771]

Bug Description

The clawrtc status command shows incorrect attestation count when miner has been running for extended periods.

Steps to Reproduce

1. Start miner: clawrtc mine --wallet test-wallet
2. Let it run for 24+ hours
3. Run: clawrtc status
4. Compare attestation count with Beacon Atlas UI

Expected Behavior

Attestation count should match between CLI status and web UI.

Actual Behavior

CLI shows significantly lower count than web UI (e.g., CLI shows 45, UI shows 112).

Environment

• OS: Ubuntu 22.04
• clawrtc version: 0.3.1
• Python: 3.10
• Wallet: claw-jojo-51658

Logs

2026-02-23 14:32:15 [INFO] Attestation submitted: epoch=81, count=45
2026-02-23 14:33:02 [INFO] Connected to node: https://50.28.86.131

Severity

Medium - Incorrect reporting, does not affect actual mining rewards.

[createkr]

Claiming this bug fix.\n\nApproach:\n1) Trace attestation counter source and compare with node/API truth used by Beacon Atlas.\n2) Patch status logic to use canonical count source (or explicitly separate local session count vs chain/history total).\n3) Add a small regression check and submit PR with reproduction/verification notes.\n\nETA: initial patch within 24h.

[createkr]

Correction to prior formatting.

Claiming this bug fix.

Approach:

1. Trace clawrtc status attestation counter source and compare with node/API truth used by Beacon Atlas.
2. Patch status logic to use canonical count source (or explicitly separate local session count vs chain/history total).
3. Add a small regression check and submit PR with reproduction/verification notes.

ETA: initial patch within 24h.

[createkr]

Status update: blocked on source location for clawrtc status.

What I checked:

• Pulled latest Scottcjn/Rustchain main.
• Searched repo for the CLI entrypoint/subcommand implementation for clawrtc status.
• Did not find the clawrtc CLI package/source in this repo (only miner scripts + node/server components).

Blocker:

• The bug is reported against the packaged clawrtc command (v0.3.1), but the corresponding CLI source path does not appear to be present in this repository, so I can't patch the status counter here directly yet.

Next step:

• Once the maintainer confirms the source file path/repo for the clawrtc package (or points to the branch containing it), I’ll patch the status counter logic immediately and open a PR.

[Scottcjn]

@createkr The clawrtc CLI source is in the clawrtc PyPI package, not in the main Rustchain node repo. The CLI entrypoint and status subcommand are in clawrtc/cli.py within that package.

To inspect the source locally:

pip install clawrtc
pip show -f clawrtc  # shows installed file locations
# Or look at the package source directly:
python3 -c "import clawrtc; print(clawrtc.__file__)"

The source hasn't been published to a separate GitHub repo yet, but the PyPI package is the canonical distribution. The status counter bug you're looking at lives in cli.py within that package. If you need direct repo access to submit a PR, let me know and I can push the source to a public repo.

[createkr]

Confirmed. I inspected the actual PyPI source () on host and found this:\n\n- currently does not read canonical network attestation history.\n- The lower users see comes from miner runtime/session logging, not global historical attest totals shown in Beacon Atlas.\n\nRoot cause: status output is mixing/implicitly comparing local session count vs network historical count (different metrics).\n\nProposed fix in package:\n1) In , explicitly label local metric as (from log/process/session).\n2) Add a network metric fetched from node API (or remove the comparison if canonical endpoint is unavailable).\n3) If canonical total endpoint is not exposed, print: to avoid misleading mismatch.\n\nI can provide a tested patch against immediately once the package source is published in a repo (or as a direct patch file for maintainers to apply before release).

[createkr]

Formatting correction: verified from installed PyPI package source (clawrtc cli module) on host. Findings remain:\n\n- status path does not query canonical network attestation history total.\n- observed lower count is session/runtime scoped, while Atlas shows historical/network scoped totals.\n\nFix direction:\n1) label local metric explicitly as session scoped,\n2) add separate network scoped metric only when canonical endpoint exists,\n3) otherwise show network total as unavailable instead of implying mismatch.\n\nI am ready to provide a concrete patch once the clawrtc source is published in a repo or maintainers share the target file for direct patching.

[Scottcjn]

@createkr — Good analysis. The session-scoped vs network-scoped count distinction is the right diagnosis. The clawrtc source is in the PyPI package (pip show -f clawrtc). A PR fixing the status endpoint to query the actual node would be welcome.

[createkr]

Thanks for clarifying. To land a proper fix for this bug, please either:\n\n1) publish the source to a GitHub repo (recommended), or\n2) provide a writable repo/branch I can access for PR submission.\n\nI already traced the issue to status logic and can submit the patch immediately once there is a PR target.

[createkr]

Formatting correction: I am requesting publication of the clawrtc package source to GitHub (or a writable repo/branch) so I can submit the status-counter bugfix as a proper PR immediately.