Next generation Governance Black Hole. Boosting yields across DeFi, starting with the CurveFinance ecosystem.
Scope
Contest Results
On what chains are the smart contracts going to be deployed?
The Convergence protocol will be deployed on the Ethereum Mainnet.
Which ERC20 tokens do you expect will interact with the smart contracts?
Lock the CVG in the LockingPositionService
Receives and acculate the following rewards :
Receives rewards from the treasury. The list of ERC20 can vary.
Convert & Stake assets in Staking contracts
Which ERC721 tokens do you expect will interact with the smart contracts?
Only NFT that we made :
LockingPositionManager
SdtStakingPositionManager
BondPositionManager
Do you plan to support ERC1155?
None
Which ERC777 tokens do you expect will interact with the smart contracts?
None
Are there any FEE-ON-TRANSFER tokens interacting with the smart contracts?
We have some interaction with USDC and potentially USDT.
We understand that USDT and USDC may introduce fees in the future, but those tokens should be assumed not to do that.
Are there any REBASING tokens interacting with the smart contracts?
None
Are the admins of the protocols your contracts integrate with (if any) TRUSTED or RESTRICTED?
TRUSTED
Is the admin/owner of the protocol/contracts TRUSTED or RESTRICTED?
TRUSTED
Are there any additional protocol roles? If yes, please explain in detail:
Multisig executing the action voted by the DAO.
Multisig receiving SDT from CvgSDT staking. Lock this SDT in veSDT.
A bond contract can mint CVG.
A staking contract can mint CVG
Only a Staking contract can be a gauge
A SDT staking contract that can withdraw a gauge token from the SdtBlackHole
Is the code/contract expected to comply with any EIPs? Are there specific assumptions around adhering to those EIPs that Watsons should be aware of?
None
Please list any known issues/acceptable risks that should not result in a valid finding.
None
Please provide links to previous audits (if any).
Halborn ( on the old Tokemak integration ) : https://ipfs.io/ipfs/QmPyZZoeNJqt44GiFRoc8E9JctCyp5DYxkW254hhfkeUui
Hats ( on the Bond mechanism & Oracle price fetching ) : https://app.hats.finance/audit-competitions/convergence-finance-ibo-0x0e410e7af8e70fc5bffcdbfbdf1673ee7b3d0777/leaderboard
Are there any off-chain mechanisms or off-chain procedures for the protocol (keeper bots, input validation expectations, etc)?
None
In case of external protocol integrations, are the risks of external contracts pausing or executing an emergency withdrawal acceptable? If not, Watsons will submit issues related to these situations that can harm your protocol's functionality.
We are interacting with StakeDao on the integration of their Gauge contract through our Staking architecture.
We are for instance :
We are aware of this kind of issues, we so separated the Convergence rewards from the rewards coming from StakeDao, in order not to break the full protocol.
Do you expect to use any of the following tokens with non-standard behaviour with the smart contracts?
USDC & USDT
Add links to relevant protocol resources
Technical documentation is to find through natspec in contracts & under technical documentation folder: https://github.com/sherlock-audit/2023-11-convergence/tree/main/sherlock-cvg/technical-docs
Total Rewards
Contest Pool
Lead Senior Watson
Judging Pool
Lead Judge
29,500 USDC
16,000 USDC
2,000 USDC
2,500 USDC
Status
Scope
Start Time
End Time
Finished
2,591 nSLOC
Nov 15, 2023, 3:00 PM
Nov 29, 2023, 3:00 PM