I'm focusing on the "breakeven line" idea and its ability to accurately express when a position is compounded (yield is withdrawn, and redeposited.) Instead of graphing it as a ray (a line with one "extended" point) we can instead graph it as a line segment (no extended points) from the position deposit time, to when a position's size is modified.

If we add to the position size, then the breakeven line should be steeper (more fees should be accrued due to a larger position size.) I made a quick mockup using TradingView to illustrate this idea.

Dynamic Data Input on TradingView Indicator

The first major engineering challenge in order for this to be useful in realtime decision making is to allow for the script to have the capability to dynamically read position data from external data sources. I did quite a bit of research on this, and it appears that TradingView's PineScript does not currently have this capability.

Currently the variables must be manually input on the indicator. This can be done by double clicking the indicator on TradingView.

Those variables are manually imported off of the data presented by Revert's UI

https://revert.finance/#/uniswap-position/mainnet/312741

The founder of Revert passed me along this draft documentation of their private API. This was current as of 12 July 2022, as such there may have been some changes introduced since. This will allow you to access the information in JSON format.

apidocs.md

---

Research

I would encourage you to explore workarounds.

Workaround Strategy A - API Reverse Engineering

I would highly recommend API reverse engineering so that there is FAR LESS infrastructure to support for this capability. Then we could have a super simple node program that simply pings Revert (GET) and TradingView (POST) APIs every minute or so.

Workaround Strategy B - Scraper

Have a remote invoked scraper to manually log in to your TradingView account, and

1. pass in the updated parameters using the settings panel (this might be possible by directly making the API request to update the user's settings vs having to navigate through the UI) or
2. to hardcode the parameters and update the PineScript code.