Cross-chain Deployments

What are Cross Chain Deployments?

Cross-chain deployments allow one Aera vault to access assets on other chains by leveraging other Aera vaults on those chains. Cross-chain deployments mean that each chain has an independent Aera vault with its own guardians and assets. However, the vaults on chains other than the parent vault are just BaseVault contracts since they don't need to collect fees separately or even support withdrawals/deposits.

Why They Matter

Cross-chain access is crucial for incorporating unique assets, finding liquidity for long-tail assets and tapping into the best yields.

How to do a Cross Chain Deployment

Cross-chain deployments should be planned carefully taking into account the behavior of assets on every chain involved but here is a list of concerns to think about:

  • Which chains will be used and whether to use BaseVault or another type of vault on those chains?

  • Is there a risk of assets becoming irretrievable?

  • What address will be the vault owner and guardian on non-parent chains?

  • How will the account take into account the value on other chains and value that is moving across the bridge?

Caveats

Cross-chain deployments can be very risky depending on the specific bridge used. Cross-chain deployments to non-EVM chains are not currently supported.

Last updated