Make setting ck take extrinsics payable#2750
Conversation
🛡️ AI Review — Skeptic (security review)VERDICT: SAFE BASELINE scrutiny: established contributor with repo write permission, substantial prior subtensor activity, no Gittensor allowlist match found; branch feat/ck-take-settings-pays-yes -> devnet-ready. Static-only review found no FindingsNo findings. Prior-comment reconciliation
ConclusionNo malicious pattern or security vulnerability was found in the current diff. The prior weight-accounting concern remains addressed. 🔍 AI Review — Auditor (domain review)VERDICT: 👍 Gittensor UNKNOWN by allowlists; author has repo write permission and substantial recent subtensor contribution history, so calibrated as established. Description discrepancies: the PR body is substantive but stale. It says Overlapping PRs share broad runtime/test/generated files, but I did not identify a duplicate candidate for this exact delegate-take fee metadata change. No auto-fixes were applied, and I did not run tests because the reviewed behavior is covered statically by the dispatch metadata assertions and no finding required runtime confirmation. FindingsNo findings. ConclusionApproving: the intended |
|
🔄 AI review updated — Skeptic: VULNERABLE |
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👎 |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
🔄 AI review updated — Skeptic: VULNERABLE |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👎 |
…r/subtensor into feat/ck-take-settings-pays-yes
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
Motivation
increase_takeanddecrease_takewere marked asPays::No, which means these state-mutating delegate take changes did not pay normal transaction fees. These calls should be payable like other user-submitted staking operations.What Changed
decrease_takedispatch metadata fromPays::NotoPays::Yes.increase_takedispatch metadata fromPays::NotoPays::Yes.DispatchClass::Normaland now reportPays::Yes.spec_versionfrom417to418.Behavioral Impact
Delegate take increase/decrease transactions now participate in normal fee payment. The existing origin checks, take bounds, ownership checks, rate limiting, and underlying staking logic are otherwise unchanged.
Migration / Spec Version
No storage migration is required. This is a runtime-affecting metadata change and includes the required
spec_versionbump.Testing
test_delegate_take_dispatch_info_pays_feefor the affected dispatch metadata../scripts/fix_rust.shand unit tests were run locally.