Movement network · Move · DeFi
A yield-aggregation protocol. Vaults take a single deposit and route it across lending venues through composable strategy packages.
The stack
Every package below is live on Movement mainnet and was published with its source attached. Select a component to see what it does, its address, and the modules that implement it — each one linking to its verified source on the explorer.
Deposit path
Value crossing a package boundary is wrapped in a type the language will not let a contract store, copy, or discard — so an intermediate step physically cannot retain funds. It must pass them on, and the compiler rejects any path that doesn't.
Vault accounting
A vault values itself as idle balance plus deployed debt, rather than by reading its own token balance. Assets sent directly to a vault therefore do not move the share price; only accounted inflows do. Resyncing the two is a privileged operation.
Harvested profit is released on a linear schedule instead of landing in one step, so a deposit arriving immediately after a harvest cannot capture yield it wasn't present for. Withdrawals draw from idle funds first and touch a venue only for the shortfall.
Security review
Reviewed continuously from first deployment through the rewards system, with core accounting audited twice and the cross-chain campaign reviewed independently by two firms.