๐งโ๐พSilos
Reference material for Aloe Blend silos
Last updated
Reference material for Aloe Blend silos
Last updated
The information provided by Aloe Labs, Inc. (โwe,โ โusโ or โourโ) on docs.aloe.capital (the โSiteโ) is for general informational purposes only. All information on the Site is provided in good faith, however we make no representation or warranty of any kind, express or implied, regarding the accuracy, adequacy, validity, reliability, availability or completeness of any information on the Site.
Under no circumstance shall we have any liability to you for any loss or damage of any kind incurred as a result of the use of the site or reliance on any information provided on the site. Your use of the site and your reliance on any information on the site is solely at your own risk.
Aloe Blend uses silos to take advantage of external yield opportunities and keep users' funds productive. This is possible because most Uniswap liquidity sits idle, far from the current trading range. Instead of leaving it there, Blend deposits it to silos. If the price does shift, Blend can recenter its Uniswap V3 position without locking in impermanent loss ๏ผ it just pulls the requisite funds from silos. Alternatively, if the price stays the same but volatility increases, Blend pulls from both silos in order to widen its Uniswap position. Finally, if volatility decreases, Blend narrows its Uniswap position and places excess liquidity in silos. At any given time, silos manage between 45% and 94% of pool liquidity (because 1%๏ผ50% is in Uniswap and 5% is held as float).
Each silo contains just enough logic to move funds from Blend to another protocol and back again. Since Blend vaults delegatecall
to their silos, a single silo can be reused by multiple Blend vaults.
Supplies funds to the lending market. Logic compatible with any cToken (not cETH). Specify cToken address in silo constructor. poke()
accrues interest on the cToken.
Supplies WETH to the lending market. Unwraps WETH to ETH when depositing and rewraps it when withdrawing. Specify cETH address in silo constructor. poke()
accrues interest on cETH.
Supplies funds to . Logic compatible with any fToken (not fETH). Specify fToken address in silo constructor. Note that fTokens are pool specific, e.g. fDAI 8 is not the same as fDAI 18. poke()
accrues interest on the fToken.
Supplies WETH to . Unwraps WETH to ETH when depositing and rewraps it when withdrawing. Specofy fETH address in silo constructor. Note that fETH tokens are pool specific, e.g. fETH 8 is not the same as fETH 18. poke()
accrues interest on fETH.
Supplies funds to pools that have in-kind token rewards, e.g. fTRIBE when TRIBE is being distributed as an incentive. poke()
searches for these in-kind rewards and claims them. Otherwise same as a standard fToken Silo.
Supplies funds to any yield opportunity that conforms to the standard.
Deposits assets to a vault. Behavior would be sub-optimal (but non-breaking) in cases where atomic withdrawal limit is less than balance, as only Yearn keepers have permission to replenish withdrawal queue strategies. In practice this hasn't been an issue.
Doesn't do anything. Useful in cases where one asset of the pair has great potential, but the other isn't supported by existing silos.