While each vault run under the same parameters, the results could be different depending on the initial conditions of the vault. Let me give you an example.
It could be the case that Vault#1 receives a new investment (deposit) into the vault that causes its debt ratio to get back closer to the ideal target. So then after the same price price movement, vault#2 gets rebalanced while vault#1 didn’t get triggered. If price then reverted back, it could cause out performance on the vault#1.
You can see that the 2nd vault has poorer performance due to the higher number of rebalances.
The good news is that our repurchase pilot is going well and so far showing good results. These issues will go away as we will no longer require rebalance and the vaults performance should be more inline with one another.
Vault rebalances if one of the position’s debt ratio is beyond the threshold set. However, when a user deposits, the new assets are added into the existing positions such that the overall debt ratio get closer to the ideal value. Hence, less likely for it to get rebalance on the same price move vs. another vault that didn’t receive the deposit.
It’s not a mistake. The 2nd vault was created because we must cap the size of each vault. Otherwise, we would incur a large price impact when making a swap when rebalancing.
We launched the PCS2 pool after L3x-BUSDBTCB-PCS1 was full at the time.