Skip to main content
YieldPoint is a hub-and-spoke protocol. Base is the hub: all vault state — shares, withdrawal requests, bonding timers, exchange rates — lives there. Avalanche and Katana are spokes. On spokes you interact with 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?

​
Contract surface per chain

Deployed addresses for every contract above are on the Contracts page. Don’t hard-code addresses — link to that page and read from it.

​
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.
Planning a gauge or multi-chain aggregator? If you intend to aggregate redemptions across multiple spoke chains for the same controller address, read Gotchas and known limits before designing your controller model. Concurrent pending withdrawal requests across multiple spokes for one controller is not supported and produces failure modes the guide does not work around.