Fix root basket claim weight accounting

[UnArbosFive]

Summary

• bound root basket claims to 256 staking hotkeys and 256 raw basket-position rows before mutation
• benchmark the full Root Reborn claim path with a single work parameter
• use the canonical claim weight for both worst-case admission and post-dispatch refund
• keep the claim within the production normal-extrinsic limit, including transaction extensions

Verification

• 43 focused root-claim tests
• parameterized claim_root benchmark test
• production-runtime admission test including transaction extensions
• diff and formatting audit

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
subtensor	Ready	Preview, Comment	Jul 29, 2026 11:20am

[github-actions]

🛡️ AI Review — Skeptic (security review)

VERDICT: SAFE

HIGH contributor-risk signal from a 25-day-old account with no public repos, mitigated by admin permission and substantial merged repository work; no Gittensor association; release-v438 is an active integration branch.

Static analysis found the claim workload bounds, benchmark parameterization, declared admission weight, and post-dispatch refund internally consistent. The diff does not modify trusted AI-review or Copilot instruction files.

Findings

No findings.

Conclusion

No malicious behavior or security vulnerability was found. The change bounds both storage-scan dimensions before mutation and charges a conservative benchmark-derived weight.

---

🔍 AI Review — Auditor (domain review)

VERDICT: 👍

Gittensor association UNKNOWN; author is an established repository administrator with substantial recent contributions.

The implementation consistently bounds both hotkey and raw holding-row traversal, uses the benchmark-derived weight for admission and refund, and adds focused boundary and production-runtime admission coverage. The overlapping open PRs are broad integration/runtime changes rather than competing implementations. No auto-fixes were required.

Findings

No findings.

Conclusion

The accounting change is conservative, internally consistent, and adequately tested. No blocking domain issues were found.

[github-actions]

🔄 AI review updated — Skeptic: SAFE Auditor: 👍