feat: add disassociate_hotkey

[Rapiiidooo]

Description

Adds disassociate_hotkey(hotkey, max_items) so a coldkey can release an idle hotkey and allow another coldkey to associate it. The call checks ownership, registrations, stake, collateral, reward entitlements and active or pending relationships before clearing ownership and inactive autostake references. Cooldowns, swap lineage and EVM associations are preserved.

Includes pallet and E2E tests, a benchmark and proxy restrictions. Regression coverage includes inbound pending child links and work limits across multiple parents on the same subnet.

Ownership changes and user-visible consequences

Beyond retiring unused or compromised hotkeys, this change enables an individual hotkey to be released and associated with a different coldkey, without transferring the original owner’s other hotkeys. This could facilitate transferring or selling individual hotkeys once they are idle.

A familiar hotkey address could therefore represent a different operator after deregistration and reassociation. Someone staking again based on that address’s previous reputation could end up supporting an operator they did not intend to support.

The current owning coldkey must sign the release. The hotkey must have no subnet registrations, collateral, outstanding reward entitlements, or active or pending relationships.

Deregistration does not remove delegators’ stake. If any stake remains on the hotkey, including third-party stake on any subnet, disassociate_hotkey fails with HotkeyHasOutstandingStake and leaves ownership unchanged. This extrinsic does not unstake, refund, or detach those positions. They must already have been withdrawn or moved through the existing staking mechanisms before release can succeed. Residual zero-valued stake entries also block release until they have been cleaned up.

Validation

• Passed: cargo fmt --check --all, pnpm run fmt in ts-tests, and git diff --check.
• Functional tests and reference benchmarks are left to CI, per repository guidance.

Before merge

• Bound storage reads on rejected calls and replace the fallback with measured weights. Existing vectors are still read in full before an insufficient max_items is rejected. The current storage layout does not provide an independently readable size bound.
• Run functional CI and satisfy the runtime version gate; the branch and mainnet both report spec_version = 455.

[vercel]

@Rapiiidooo is attempting to deploy a commit to the RaoFoundation Team on Vercel.

A member of the Team first needs to authorize it.