Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[VEN-3018]: configure RiskStewardReceiver and MarketCapsRiskSteward #463

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

coreyar
Copy link
Contributor

@coreyar coreyar commented Jan 20, 2025

Description

Resolves VEN

@coreyar coreyar force-pushed the configure-risk-steward branch from df3efce to a3ed6e9 Compare January 20, 2025 16:16
@chechu chechu changed the title feat: configure RiskStewardReceiver and MarketCapsRiskSteward [VEN-3018]: configure RiskStewardReceiver and MarketCapsRiskSteward Jan 20, 2025
@coreyar coreyar force-pushed the configure-risk-steward branch from a3ed6e9 to 9cfc49c Compare January 21, 2025 14:03
@coreyar coreyar force-pushed the configure-risk-steward branch from 5fcb751 to 9f693c5 Compare January 21, 2025 15:22
Comment on lines 101 to 110
...IL_COMPTROLLERS.map((comptroller) => ({
target: ACM,
signature: "giveCallPermission(address,string,address)",
params: [comptroller, "setMarketSupplyCaps(address[],uint256[])", MARKET_CAPS_RISK_STEWARD],
})),
...IL_COMPTROLLERS.map((comptroller) => ({
target: ACM,
signature: "giveCallPermission(address,string,address)",
params: [comptroller, "setMarketBorrowCaps(address[],uint256[])", MARKET_CAPS_RISK_STEWARD],
})),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would make sense to use the wildcard 0x0 in this case, allowing the risk steward contracts to invoke the mentioned functions on any contract. This way, we won't have to update the permissions if a new pool is added in the future

export const LIQUID_STAKING_ETH_COMPTROLLER = "0xC7859B809Ed5A2e98659ab5427D5B69e706aE26b";
export const MEME_COMPTROLLER = "0x92e8E3C202093A495e98C10f9fcaa5Abe288F74A";
export const ACM = "0x45f8a08F534f34A97187626E05d4b6648Eeaa9AA";
export const RISK_STEWARD_RECEIVER = "0x34e4505f92C8499B07eeb7Aa72404A490D152Ab3";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see this contract deployed at VenusProtocol/governance-contracts#115

Copy link
Contributor Author

@coreyar coreyar Jan 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't pushed the deployments. (Updated and pushing)

Comment on lines 61 to 80
{
target: ACM,
signature: "giveCallPermission(address,string,address)",
params: [RISK_STEWARD_RECEIVER, "setRiskParameterConfig(string,address,uint256)", NORMAL_TIMELOCK],
},
{
target: ACM,
signature: "giveCallPermission(address,string,address)",
params: [RISK_STEWARD_RECEIVER, "toggleConfigActive(string)", NORMAL_TIMELOCK],
},
{
target: ACM,
signature: "giveCallPermission(address,string,address)",
params: [RISK_STEWARD_RECEIVER, "pause()", NORMAL_TIMELOCK],
},
{
target: ACM,
signature: "giveCallPermission(address,string,address)",
params: [RISK_STEWARD_RECEIVER, "unpause()", NORMAL_TIMELOCK],
},
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think Fast-track and Critical timelocks should also be authorized to call these functions

Comment on lines +86 to +90
{
target: ACM,
signature: "giveCallPermission(address,string,address)",
params: [MARKET_CAPS_RISK_STEWARD, "setMaxIncreaseBps(uint256)", NORMAL_TIMELOCK],
},
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would also authorize Fast-track and Critical timelocks

@coreyar coreyar force-pushed the configure-risk-steward branch 3 times, most recently from a4b87c8 to 9c63bb2 Compare January 23, 2025 13:36
@coreyar coreyar force-pushed the configure-risk-steward branch from 9c63bb2 to 55928da Compare January 27, 2025 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants