Skip to main content
A vault is what almost every partner buys, and the only product you need to offer a balance that earns. Your users deposit into it, it puts that money to work, and your app reads back one balance and one APY.

​
Several sources, one balance

A vault can use several yield sources at once, and adding a new one does not disturb the vaults already running, because each source sits behind its own strategy. See Strategies for the ones running today. Which sources your vault may use is decided when it is created. No vault function adds or swaps one afterwards, and the only thing that can change the list is replacing the vault’s code, which is a decision you make when you create it: a vault can be deployed upgradable or permanent.

​
What you control

You choose which assets the vault accepts, which sources it may use, and the fee it charges on the yield. The fee you can change whenever you want. See Fees and revenue. Money that has not been put to work yet sits in the vault itself, and a user can withdraw it like any other balance. Keeping some there is deliberate: it makes small deposits cheaper to handle, and it is where funds land if we ever need to pull them out of a protocol in a hurry.

​
What protects the money

  • A vault can only ever invest in the sources chosen when it was created.
  • Nothing can be sent to an outside address. Money moves between the vault and its own strategies, and out only to the user who owns it.
  • If a protocol underneath turns risky, one call pulls everything back into the vault.
  • A source can be closed to new money while withdrawals stay open.
  • No lock-up. A user withdraws whenever they want, with no minimum holding period and no notice, and nobody can freeze it.
  • Fees only accrue on gains.
None of that is policy. It is what the contracts do, and they are public in defindex-io/stellar-contracts. The audit reports are on Risks and Audits.