/vVv

Primary LanguageSolidity

vVv Vesting & Staking contest details

Q&A

Q: On what chains are the smart contracts going to be deployed?

Mainnet, possibly Avalanche C-Chain for the staking contract.

Q: Which ERC20 tokens do you expect will interact with the smart contracts?

$VVV

Q: Which ERC721 tokens do you expect will interact with the smart contracts?

none

Q: Do you plan to support ERC1155?

no

Q: Which ERC777 tokens do you expect will interact with the smart contracts?

none

Q: Are there any FEE-ON-TRANSFER tokens interacting with the smart contracts?

no

Q: Are there any REBASING tokens interacting with the smart contracts?

no

Q: Are the admins of the protocols your contracts integrate with (if any) TRUSTED or RESTRICTED?

TRUSTED -- if AuthorizationRegistry is considered a protocol in this case

Q: Is the admin/owner of the protocol/contracts TRUSTED or RESTRICTED?

TRUSTED

Q: Are there any additional protocol roles? If yes, please explain in detail:

  1. DefaultAdmin, any arbitrary role
  2. actions: a. Create role b. Remove role c. Set permission d. Call function
  3. expected outcomes:
    • DefaultAdmin must be allowed to take all these actions (d. only if setPermission was used to give it permission`).
    • Any arbitrary role should only be allowed to take action d. if (and only if) given permission through setPermission
  4. prohibited:
    • Any arbitrary role must not be allowed to take action a - c
    • No role may be able to take action d without having the role assigned through setPermission

Q: 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?

no

Q: Please list any known issues/acceptable risks that should not result in a valid finding.

We accept a loss of precision of 0.000000000001% on the vested amount calculation.

Q: Please provide links to previous audits (if any).

none

Q: Are there any off-chain mechanisms or off-chain procedures for the protocol (keeper bots, input validation expectations, etc)?

no

Q: 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.

no

Q: Do you expect to use any of the following tokens with non-standard behaviour with the smart contracts?

no

Q: Add links to relevant protocol resources

https://hackmd.io/@vvv-knowledge/Syme5HlRT

Audit scope

vvv-platform-smart-contracts @ 7008f399a58c05832ef361dc5c54bd091d723f84