You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Subject: Extending the Staking Module in Cosmos SDK
Hello Cosmos team,
I have a requirement to modify the existing staking module by:
1- Adding a new field to the Validator protobuf definition in staking module.
2- Implementing logic in the staking keeper to check this new field.
However, I want to extend the existing staking keeper rather than creating a separate custom module. Given that our chain references the staking module externally (without having its code locally), is this possible? If so, what would be the best approach to achieve this?
Is there a samle project OR code to direct me?
Looking forward to your guidance.
Best regards,
The text was updated successfully, but these errors were encountered:
the design of the staking module is quite tied to the current design, it would be recommended to fork or write your own implementation for staking if it is time sensitive
the design of the staking module is quite tied to the current design, it would be recommended to fork or write your own implementation for staking if it is time sensitive
I already have forked it. Just can't understand how I can extend it to handle ERC1155 staking.
Subject: Extending the Staking Module in Cosmos SDK
Hello Cosmos team,
I have a requirement to modify the existing staking module by:
1- Adding a new field to the Validator protobuf definition in staking module.
2- Implementing logic in the staking keeper to check this new field.
However, I want to extend the existing staking keeper rather than creating a separate custom module. Given that our chain references the staking module externally (without having its code locally), is this possible? If so, what would be the best approach to achieve this?
Is there a samle project OR code to direct me?
Looking forward to your guidance.
Best regards,
The text was updated successfully, but these errors were encountered: