Cross-Chain
MORE Vaults can be deployed on any chain. Any MORE Vault can be extended to other chains, offering strategists the ability to transfer assets across chains securely within the same vault ecosystem or mesh.
Hub & Spoke
Each MORE Mesh operate as a hub and spoke model. Vault creators must first choose the chain on which they prefer to keep their hub. Once the hub chain is chosen, it cannot be changed.
Accounting is aggregated on the hub vault from all spoke vaults within a mesh in order to ensure a reliable and resilient NAV calculation. As a result, deposits and withdrawals are also handled by the hub vault. Such a configuration requires strategists to liberate liquidity and propagate it back to the hub to fulfill redemption requests.
Once the hub vault is created, a second MORE Vault can be deployed on any other EVM. The deploy step of the second vault must be executed by the same Vault Owner, set the same Vault Owner and provide a SALT, a unique identifier that makes Vault Factories on other chains aware of the relationship between the vaults. The registration is propagated to other chains via LayerZero. Only after confirmation is the hub-spoke relationship considered valid.
Spoke vaults have no share accounting. Instead, their value is tracked via assets under management through totalAssets(). The spoke vault may hold yield-generating positions, but its P&L is reflected in the total asset value reported to the hub.
Omni-chain Fungible Tokens
MORE Vault ERC-20s are natively omni-chain. MORE has partnered with a major cross-chain message provider to enable vault receipt tokens that can be held on or bridged to any EVM chain. This means that liquidity providers can supply assets from any chain, and in exchange, receive their receipt token on the chain of their choice, in a single transaction.
Because withdrawals on MORE Vaults may be asynchronous, for now, withdrawals must take place on the hub vault's chain. This means that if you hold your deposit token on Flow, but the hub vault is on Ethereum, you will need to bridge your token to Ethereum in order to withdraw.
Asynchronous atomic cross-chain withdrawals will be available by mid-Q4 2025. When this feature is deployed, vault token holders will never need to manually bridge in order to withdraw.
Cross-Chain Transfers
Vaults within the same mesh may send and receive assets between each other. Spokes may send assets directly to other spokes without first passing through the hub vault.
The MORE Vaults Core includes a generic Bridge facet. This contract first references Vault Factory in order to verify the sending and receiving vaults exist in the same mesh. The Curator can query the Vault Registry to surface all the paths for the selected asset to the destination chain and provide the required parameters to submitActions(). Because facet selectors are not mapped directly to the functions on a specific bridge, the Bridge facet can be made fully interoperable with any whitelisted cross-chain messaging protocol.
Cross-Chain Accounting
Accounting from spokes is composed on the hub vault. MORE does not support off-chain or self-reported accounting practices and favors trust-minimized methods. Vault Owners must choose between oracle accounting or cross-chain message accounting for each spoke vault in their mesh.
Oracle Accounting
Oracles call totalAssets() to updates the oracle value. The hub vault integrates the oracle's value and consolidates the mesh's NAV and receipt token share price in near real-time.
Cross-Chain Message Accounting
When cross-chain message accounting is activated, the Vault Owner can determine the frequency at which totalAsset() accounting is sent to the hub. By default, when cross-chain message accounting is activated, a message is sent at each executeActions() call.
Last updated