Clean rate limits for hotkey/coldkey swaps#2727
Conversation
🛡️ AI Review — Skeptic (security review)VERDICT: SAFE BASELINE scrutiny: established write-permission contributor, no Gittensor allowlist hit found, branch chore/clean-rate-limits -> devnet-ready. Static analysis only. Reviewed the full 4-file diff: it removes generic FindingsNo findings. ConclusionNo malicious code or security vulnerability found in the changed lines. The removed generic limiter appears scoped to the intended swap cleanup while existing ownership checks, swap costs, and subnet-specific swap interval checks remain in place. 🔍 AI Review — Auditor (domain review)VERDICT: 👍 Established write-permission contributor; no Gittensor allowlist hit found, treated as UNKNOWN for incentive calibration. The Auditor proposed a replacement PR description, but the current body is non-trivial; not overwriting. Maintainers: ask the Auditor to regenerate if you want it. Reviewed the 4-file runtime pallet diff. The change removes the generic No auto-fixes were applied. The PR touches FindingsNo findings. ConclusionThe implementation matches the stated cleanup: removed generic rate-limit reads/writes are no longer referenced by live swap gates, ownership/cost checks remain intact, and the updated tests cover the intended same-block hotkey swap behavior. I found no blocking domain issues. |
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
Description
This PR cleans rate limits for:
Related Issue(s)
Type of Change
Breaking Change
If this PR introduces a breaking change, please provide a detailed description of the impact and the migration path for existing applications.
Checklist
./scripts/fix_rust.shto ensure my code is formatted and linted correctlyScreenshots (if applicable)
Please include any relevant screenshots or GIFs that demonstrate the changes made.
Additional Notes
Please provide any additional information or context that may be helpful for reviewers.