[Proposal] Track Impermanent Loss + Fees Collected for Data Pools

Ocean DAO Proposal

  • Name of project: APY.vision

  • Team Website (if applicable): https://apy.vision

  • Proposal Wallet Address: 0x891181a601412593d686439116b32a468441757f

  • The proposal in one sentence: We want to add visbility for tracking impermanent losses and fees collected for datatoken liquidity providers.

  • Which category best describes your project? Pick one or more.

    • [x] Build / improve applications or integrations to Ocean
    • [ ] Outreach / community (grants don’t need to be technical in nature)
    • [ ] Unleash data
    • [ ] Build / improve core Ocean software

Project Overview

  • Description of the project:
    The team at APY.vision is focused on bringing analytics to Liquidity Providers, a profession that did not exist even just 12 months ago. We are a tool that tracks fees collected and impermanent losses (IL) from providing liquidity to a pool. We want to empower liquidity providers by giving them the tools to analyse their performance by providing liquidity.

  • What problem is your project solving?
    It is very difficult for liquidity providers to accurately track their profit and loss of liquidity providing positions using the available tools. APY.Vision offers enhanced visibility in terms of tracking fees and impermanent loss that allows users to feel more comfortable and confident entering and exiting liquidity providing positions.

  • What is the final product (e.g. App, URL, Medium, etc)?

  • How does this project drive value to the Ocean ecosystem?
    This product will drive value to the Ocean ecosystem by providing tools for liquidity providers that will give them more accurate information and in turn give them confidence in their positions and encourage them to provide more liquidity to the Ocean liquidity pools.

  • Expected ROI
    In traditional finance the large brokers offer data and analytics alongside their trading services to increase their assets under management as a value-added service. We believe this principle holds true in the crypto industry. To increase the assets under management by Ocean we believe that increasing the number of data and analytical services will provide the same type of value addition to attract capital that traditional finance organizations have been using for decades.

  • Metric to optimize: “Total Value Locked”.
    Project length: 4 weeks
    We estimate Ocean can get at least 20% increase in TVL from more liquidity providers if they believe they are making the correct choice in providing liquidity.

  • Calculations for ROI
    TVL: 1,146,296.844 OCEAN
    20% of TVL = (1,146,296.844 * .2) = 229,259.3688 OCEAN
    Bang = ~229K OCEAN
    Grant size = buck = 10K OCEAN
    So ROI = bang / buck = 229K OCEAN / 10K OCEAN = 22.9
    Proposer’s estimate of % chance of success = 75%
    Final: expected ROI = .75 * 22.9 = 17.175

Project Deliverables - Roadmap

  • Any prior work completed thus far?
    Yes we have launched the tool to support Uniswap, Balancer, and Sushiswap swap thus far.

  • What is the project roadmap? That is: what are key milestones, and the target date for each milestone.
    Because Ocean uses Balancer’s Smart Pools and currently a subgraph doesn’t exist yet, we wil first need to create or modify the exist one that we have. Afterwards we will add in the calculation on the backend to support fetching the P+L for the token gains. Finally we need to look at fetching the prices for each data token to reflect the gains / losses on the UI. Project timeline is about 4 weeks from the start of work.

  • Please include the milestone: publish an article/tutorial explaining your project as part of the grant (eg medium, etc).
    – Add in Ocean as a data provider to APY.vision
    – Add in a blog to explain how it works

Project Details

Here are some of the mock ups for the current product and what we want to accomplish by adding OCEAN data tokens:

Team members

For each team member, give their name, role and background such as the following.

Tom C

  • Background/Experience:
    • Web3 Developer, BUIDLER
    • Github: https://github.com/tomafc330
    • Arctic Code Vault Contributor, Sushiswap Dev Contributor, Swerve Dev Contributor, Scaffold-ETH Contributor

Aaron B

  • Role/Background
    • MBA graduate handling outreach, education and evangelism for DeFi and Liquidity Providing
    • Non-technical contributor to INDEX/DPI community

Additional Information


Hi. Check out Ocean Core’s released Subgraph repo. https://github.com/oceanprotocol/ocean-subgraph#-get-started. One of your deliverables mentions crating / modifying a Subgraph. Ensuring your contributions on the Subgraph front are different from or leverage what has already been built might help in saving time not re-creating any of the same things.

Also Ocean graph repo is new. If you see any limitations, please feel free to comment and improve.

1 Like

Hi Alex, thanks for that! I read through the subgraph a bit, I raised a ticket with regards to an issue that I saw: https://github.com/oceanprotocol/ocean-subgraph/issues/3

1 Like