This section outlines the main features of the Aggregator protocol at various stages of its development.
- Connect wallet.
- Pick a rebalancer strategy from the Aggregator screen.
- Deposit a pair of tokens into a rebalancer strategy / withdraw constituents of the LP from it, as available (both tokens or one token if the rebalancer range order is out of range for some reason).
- Send CLP (Cargo Liquidity Provider tokens) to another wallet on deposit, Be able to withdraw to a different wallet, specified by the user.
- Can see the CLP in the portfolio screen, which represents the tokens they supplied to the rebalancer of their choice.
- 2 rebalancers integrated.
- All of the above.
- Single-sided deposits.
- LP deposits, V2 and V3 style.
- Cross-rebalancer integration (easily move between different rebalancers).
- 5 rebalancers integrated.
- Public launch as is to mainnet.
- All live rebalancers integrated.
- Portfolio screen does have historical data (graphs).
- Fee management.
- DAO transition begins here.
- Mobile friendly.
- Other ancillary products, e.g. hedging, insurance, rebalancer squared etc. as prioritised.
- Ongoing maintenance (adding new rebalanceres, refactoring and so on).
Providers of active LP Management strategies / rebalancers we plan to integrate with
|Arrakis (G-UNI, Sorbet)||https://www.arrakis.finance/ / https://www.sorbet.finance/#/pools/|
|Gamma Strategies (ex-Visor Finance)||https://vault.visor.finance/dashboard/|
|Charm Alpha Vaults||https://alpha.charm.fi/|
Elements to be included in the roadmap
Here we collect some of the potential building blocks to be added to the V2/V3 releases.
Items that can be worked on without integrating any additional DeFi products.
|Multichain||A number of relevant protocols that we want to highlight in the Aggregator are going live on various L2 Ethereum scaling solutions. These will need to be factored into the Aggregator as well. The list below is constantly being updated:|
|Creating new pools||Where a rebalancer allows its users to create new pools, they should be able to initiate it from the Cargo interface as well.|
|Compound farming rewards||When a rebalancer allocates some of its native tokens to the user that supplies liquidity, allow them to feed those back into their rebalancer position, at a set frequency.|
|Withdraw LP as a single token||User should be able to define a single token to which their LP should be automatically converted when withdrawing from an LP Management strategy.|
|Backtesting||Check declared rebalancer performance and compare versus actual performance of the pool. Highlight outperformers, underperformers.|
|Blended return tokens||Provide users with an option to deposit their tokens into a diversified pool, which allocates them across rebalancers and respective strategies in a pre-defined fashion. Blended returns are accrued to the receipt token, averaging out high-low, risky-conservative strategy yields as well as counterparty risks associated with supplying to different LP Management services.|
|Boosted spots in search results||Burn cargo tokens in exchange for top spots in the ranking/search results for a given token pair. E.g. could be used by the rebalancers to boost awareness of their new strategies or increased limits.|
|Algorithmic redistribution, a.k.a. rebalancer^2||Dynamically shift allocation of user's tokens between different rebalancer strategies based on defined risk profile, market data and specified triggers. From stables to majors to degen pairs, upon determined price levels being hit and so on.|
|Analytical rebalancer market dashboard V2||Take V1 dashboard and turbo-charge it. Review all available liquidity pools on Uni V3 / Trident, across chains, overlay existing rebalancer strategies on top of that data to identify gaps in coverage or overmanaged pairs. Plot highest and lowest APRs along with limits available to show the allocation opportunities, then direct the user to the corresponding pool via the cargo UI.|
|Smart filters and ratings||Every rebalancer / LP Management strategy should receive a designated rating according to set criteria. This classification will help the users to navigate the landscape of such strategies, distinguishing between aggressive and more conservative ones. A set of filters could then be applied to a given wallet by default, so that whenever the user logs in, they see the desired set of items to deploy their tokens into from the start.|
Items that involve integrating other DeFi building blocks.
|Insurance add-on||When depositing tokens into a particular rebalancer strategy, a user should have an option of paying a proportion of performance towards an insurance contract to mitigate operational risks associated with smart contracts (hacks, critical bugs etc.). E.g. Unslashed, Nexus Mutual, InsureDAO, ArmorFi etc.|
|Lending / leverage integration||A number of prominent protocols are working on leverage DeFi solutions and we started to compile a short list for the integration queue: Gearbox, Wild Credit, Aave. Offer users a choice of whitelisted contracts to automatically deposit their LP receipt tokens into for the purpose of receiving additional yield income.|
|Hedge package||User should be able to append a hedge component to their position, to reduce the risks of supplying liquidity into a DEX. Inspired by the following articles: Impermanent Loss Series: Liquidity Provision as a Short Gamma Option Position and Hedging Uniswap v3 with SQUEETH|
|Ethereum Push Notification Service||Introduce notifications for new pools available as well as pools closing so users know when they need to withdraw or transfer their tokens elsewhere.|
|Automatic allocation of continuous streams||Integration with continuous payment streams like Superfluid or mean.finance enabling users to allocate part of their token flows to particular strategies at a pre-defined periodic frequency.|
|DAO coordination tools||Once DAO transition kicks off, there will be a few tools that would need to be employed. E.g. Coordinape, Colony, Utopia, Juicebox.|
|Decentralised UI||It's no secret that the front end is one of the points of contention in the current DeFi application stack. And while there are lots of performant solutions reliant on centralised infrastructure, there are obvious downsides to such an approach, especially if you subscribe to the trustless ethos of the industry. Hence we are definitely researching the possibility of migrating to a solution that could help propagating application's UI in a decentralised fashion e.g. Arweave|