feat: add config checker for staking roles#102
Merged
Seth-Schmidt merged 4 commits intomainfrom Apr 20, 2026
Merged
Conversation
Seth-Schmidt
changed the title
jatZama
reviewed
Apr 20, 2026
jatZama
approved these changes
Apr 20, 2026
- Introduced a new script `get-staking-roles` to report roles of ProtocolStaking contracts and their beneficiaries. - Updated `package.json` to include the new script in the npm tasks. - Enhanced the README to document the usage of the new script and added it to the list of available scripts. - Created a new `staking-addresses.json` file to store addresses for ProtocolStaking and OperatorStaking contracts.
…ation updates - Added support for the Sepolia testnet in the chains-config-checker, including new RPC endpoint in `.env.example`. - Updated `staking-addresses.json` to include separate configurations for mainnet and testnet, with deployment blocks for each contract. - Enhanced the `README.md` to clarify the usage of the `get-staking-roles` script across both mainnet and testnet, including details on deployment blocks. - Modified the `get-staking-roles.js` script to handle network-specific configurations and improve error handling for missing RPC URLs. chore: streamline staking address configurations and enhance script functionality - Removed the RPC_SEPOLIA variable from `.env.example` as it is no longer needed. - Updated `README.md` to clarify the usage of the `get-staking-roles` script, emphasizing the separation of mainnet and testnet configurations. - Introduced a new `staking-addresses-testnet.json` file for testnet-specific staking addresses. - Refactored `get-staking-roles.js` to utilize network-specific configuration files, improving clarity and maintainability.
Seth-Schmidt
force-pushed
the
feature/pro-304-config-checker-for-staking-roles
branch
from
5918c0c to
56e38d2
Compare
…script - Added a new section for the `getStakingRoles` script, outlining its functionality to report roles of ProtocolStaking contracts and beneficiaries of OperatorStaking contracts. - Clarified the usage instructions for mainnet and testnet configurations, including command examples and environment variable requirements. - Enhanced documentation to improve clarity and usability for developers working with staking roles.
jatZama
approved these changes
Apr 20, 2026
Seth-Schmidt
deleted the
feature/pro-304-config-checker-for-staking-roles
branch
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
2 participants
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.
Summary
Adds a
get-staking-rolesscript tochains-config-checkerthat reports role holders on theProtocolStakingcontracts (KMS + Coprocessor) and the beneficiary of every
OperatorStakingcontract.Contract addresses live in a new
staking-addresses.json, organized asprotocolStaking.{kms,coprocessor}andoperatorStaking.{kms,coprocessor}.<OperatorName>, so the ~20 operator addresses stay out of.envand can bemaintained in one place.