yearn-vaults-v3 icon indicating copy to clipboard operation
yearn-vaults-v3 copied to clipboard

Published 20 hours ago • verified publisher icon jmonteer

Registry

Open pandadefi opened this issue 2 years ago • 0 comments

v1

Our legacy registry is a single contract that allows to create and endorse a new vault cloning a specific vault version. It holds a registry of vaults version and a registry of token<>vault.

Only governance can endorse vault owned by governance. You can only have one vault per token<>version

v2

The second version of the registry I have recently deployed is two contracts a VaultRegistry and a ReleaseRegistry.

  • VaultRegistry: token<>Vault
  • ReleaseRegistry: version<>Vault implementation.

This new version of the registry comes with more flexibility, it is possible to have more than one address in charge of endorsing vaults and vault can be owned by different whitelisted addresses.

The vaults are typed and we can have more than one vault for a token<>version pair.

v3

V3 will have to have a different ReleaseRegistry from v2 since we won't be cloning but using a vyper factory.

pandadefi avatar Jun 30 '22 08:06 pandadefi