Executed

{"version":"v2","title":"VIP-77 Upgrade comptroller and set supply caps","description":"VIP-77 releases the changes implemented in [PR 164](https://github.com/VenusProtocol/venus-protocol/pull/164).


ID 167

ID 167

Proposed on: Oct 27th, 2022

Proposed on: Oct 27th, 2022

Result details
Final Votes

Quorum

305.48K of 0

Majority support

Yes

For

305.48K

Against

0

Abstain

0

Actions

Type

Address

Details

Custom

0x94d1...b77D

_setPendingImplementation(..)

Custom

Account

0x94d1...b77D

Method

_setPendingImplementation(..)

Custom

0x8D8f...2705

_become(..)

Custom

Account

0x8D8f...2705

Method

_become(..)

Proposal

The changes to the Comptroller contract allow for faster and more fine-grained reaction to changing market conditions:

  • Supply cap is introduced to prevent market manipulation attacks.
  • Risk parameters (collateral factor, supply cap, borrow cap) can now be configured with a risk manager multisig.
  • Certain actions can now be paused and unpaused on a per-market basis without a VIP with a pause guardian multisig.

Access control for risk parameters and pausing is now moved to a separate Access Control Manager contract. Governance owns the access control contract, so the roles can be asigned and unassigned by governance only.

The supply cap is set to "unlimited" on all markets except for:

  • SXP – 52.5M SXP
  • LUNA – 0 LUNA
  • UST – 0 UST

The supply cap of 0 means that no further supply is allowed (so nothing changes for LUNA and UST). The supply caps are subject for further adjustment. ","forDescription":"I agree that Venus Protocol should upgrade the Comptroller contract and set the supply caps","againstDescription":"I do not think that Venus Protocol should upgrade the Comptroller contract and set the supply caps","abstainDescription":"I am indifferent to whether Venus Protocol upgrades the Comptroller contract and sets the supply caps"}

Final Votes

Quorum

305.48K of 0

Majority support

Yes

For

305.48K

Against

0

Abstain

0

Final Votes
Status

Thu Oct 27, 11:52 am

Published onchain

Fri May 6, 06:07 am

Voting period started

Fri May 6, 06:20 am

Voting period ended

Thu Oct 27, 12:16 pm

Proposal queued

Thu Oct 27, 12:30 pm

Proposal executed