VaultInterface, a smart contract that implements the ERC-7540 vault signatures and routes deposit and redeem calls cross-chain to the hub on Base via LayerZero.
Where do I go?
| You want to… | Read… |
|---|---|
| Deposit USDC for UTY, or UTY for yUTY, from Base | Base operations |
| Integrate a gauge, wrapper, or aggregator on a spoke chain | Spoke chain operations |
| Verify the DVN configuration, understand the cross-chain trust model, or bridge tokens between chains | Bridge operations |
| Debug a revert, trace an error, or check a known limitation | Gotchas and known limits |
Contract surface per chain
| Chain | Role | What lives here |
|---|---|---|
| Base | Hub | UTY vault, yUTY vault, hub UTYVaultComposer, ShareOFTAdapter lockboxes for UTY and yUTY |
| Avalanche, Katana | Spoke | UTY OFT, yUTY OFT, UTYVaultInterface (one per spoke, distinct addresses) |
Why the spoke interface looks standard
The spoke
VaultInterface matches the ERC-7540 function signatures exactly. deposit(assets, receiver, controller) and requestRedeem(shares, controller, owner) on a spoke have the same shape as on the hub vault, so partner integrations that target ERC-7540 compile against the spoke without cross-chain-specific code paths. The protocol sponsors return-hop LayerZero fees from gas tanks on the spoke VaultInterface and the hub UTYVaultComposer — users pay only the first-hop native fee. See Bridge operations for the gas sponsorship model.