Add getStakeInfoForColdkeyAndNetuid and getStakeOperationThreshold views to StakingPrecompileV2#2899
Open
pawel-gebal-reef wants to merge 1 commit into
Conversation
…ews to StakingPrecompileV2
|
@pawel-gebal-reef is attempting to deploy a commit to the RaoFoundation Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds two read-only view functions to the V2 staking precompile:
getStakeInfoForColdkeyAndNetuid(coldkey, netuid)— returns every hotkey a coldkey stakes to on a given subnet, each with its stake amount. Contracts built on top of staking currently have no way of tracking the hotkeys they stake under, especially in the case of hotkey swaps.getStakeOperationThreshold()— returns the minimum stake amount the chain will accept for a stake operation. Contracts integrating with the staking precompile currently have no on-chain way to read this limit, even though operations below it revert (AmountTooLow); they are forced to hardcode the value and break silently if it changes.Both functions are read-only and charge gas per storage read, so they can't be used to force unbounded work.
Related Issue(s)
Type of Change
Breaking Change
None. Both are additive, read-only view functions — no storage, extrinsic, or existing-selector changes.
Checklist
./scripts/fix_rust.shto ensure my code is formatted and linted correctlyAdditional Notes
getStakeOperationThresholdrather than the storage item's literal name (DefaultMinStake) so integrators understand what the value does without reading pallet internals.