VIP-210 Venus Prime: deployment stage 5/5



If passed, this VIP will resume Prime contract, allowing Prime holders to claim their rewards. It will also upgrade the Prime contract, to improve the traceability of interactions with the contract, emitting more events.


This VIP is the fifth (and last) one on the deployment plan of Venus Prime. Check the updated Venus public documentation to review the details of the deployed Venus Prime program. This VIP is part of the proposal Venus Tokenomics Upgrade v3.0 Proposal, published in the Venus community forum. The Venus Prime finally released has several differences with the original program proposed.

The full deployment of Venus Prime needs 5 VIP’s. These are the details of the full deployment plan:

  • Enable Prime token, and allow users to claim them (VIP-201)
  • Set the rest of the timestamps when users staked more than 1,000 XVS on the XVSVault (VIP-202 and VIP-203)
  • Configure the PrimeLiquidityProvider contract, starting accruing rewards for Prime holders (VIP-206)
  • Resume Prime (this VIP)

Specifically, in this VIP the following actions will be performed:

After this VIP, Prime holders will be able to claim their Prime rewards.

Security and additional considerations

We applied the following security procedures for this VIP:

  • Venus Prime configuration post upgrade: in a simulation environment, validating the behavior of the Venus Prime tokens is the expected one after the VIP
  • Deployment on testnet: the same contracts were deployed and configured to testnet, and used in the Venus Protocol testnet deployment
  • Audit: OpenZeppelin, Certik, Peckshield and Fairyproof have audited the deployed code
  • Contest: Code4rena performed a contest on the Prime codebase

Audit reports

Deployed contracts on mainnet


Voting options

  • For – Execute this proposal
  • Against – Do not execute this proposal
  • Abstain – Indifferent to execution


0x6beb6D2695B67FEb73ad4f172E8E2975497187e4.upgrade(“0xBbCD063efE506c3D42a0Fa2dB5C08430288C71FC”, “0x371c0355CC22Ea13404F2fEAc989435DAD9b9d03”)



Related Tags: