fix: updated xvs max limit and setPrime permissions

VenusProtocol · Sep 13, 2023 · 860c959 · 860c959
1 parent 8af2567
commit 860c959
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 4 deletions.
diff --git a/contracts/Tokens/Prime/PrimeStorage.sol b/contracts/Tokens/Prime/PrimeStorage.sol
@@ -28,7 +28,7 @@ contract PrimeStorageV1 {
     uint256 public constant MINIMUM_STAKED_XVS = 1000 * EXP_SCALE;
 
     /// @notice maximum XVS taken in account when calculating user score
-    uint256 public constant MAXIMUM_XVS_CAP = 10000 * EXP_SCALE;
+    uint256 public constant MAXIMUM_XVS_CAP = 100000 * EXP_SCALE;
 
     /// @notice number of days user need to stake to claim prime token
     uint256 internal constant STAKING_PERIOD = 90 * 24 * 60 * 60;

diff --git a/contracts/XVSVault/XVSVault.sol b/contracts/XVSVault/XVSVault.sol
@@ -870,9 +870,7 @@ contract XVSVault is XVSVaultStorage, ECDSA, AccessControlledV5 {
      * @param _primeRewardToken address of reward token
      * @param _primePoolId pool id for reward
      */
-    function setPrimeToken(IPrime _primeToken, address _primeRewardToken, uint256 _primePoolId) external {
-        _checkAccessAllowed("setPrimeToken(address,address,uint256)");
-
+    function setPrimeToken(IPrime _primeToken, address _primeRewardToken, uint256 _primePoolId) external onlyAdmin {
         require(address(_primeToken) != address(0), "prime token cannot be zero address");
         require(_primeRewardToken != address(0), "reward cannot be zero address");