Martin Green

After receiving some community feedback, we've decided to do some changes to the logic of liquidities which outlast the foreseen locked time. So, if a project lasts longer than what was agreed (agreement which is kept on a contract, immutable) in the borrowing transaction, this means that the user of such project will be forced to either: a) Keep paying for its borrowed amount. b) Buyout the liquidity. a) is pretty simple. Just pay the same monthly fee. However, most of the devs whom have a project last longer than a few months, will surely be able to afford a buyout, so let's focus on that. b) Buying out the liquidity is a process which will be defined the following way: Initial_liq+monthly+0.1% of volume. So, for b), let's say a token started with borrowing 1ETH(initial_liq), and had 1M volume. In this case, the buyout charge will stand at 1+0.1(monthly)+$1000(0.1% of 1M). It's important to note that, according to UNISWAP V2, Liquidity owner gets 0.25% of volume accrued, meaning that $LP would be taking $1000 out of $2500, thus leaving a profit on both the dev's end, and the protocol's. For coins which want to burn their liquidity once it unlocks, we'll take Initial_liq + monthly price, so it'd be 1.1ETH for the aforementioned scenario. In this case, there won't be a profit for the dev when it unlocks, so it'd be unfair to charge them for the accrued value of a burned liquidity. There are further specifications about how to define whether a coin will be taken in for buyout or not, which will be detailed in the whitepaper. Speaking of which, our whitepaper will have an update including these topics: — Revenue (Threshold, differences between managed funds and profits) — Buyouts (Requirements and set targets) — Pre-agreement of borrowing discounts. The whitepaper will be updated following those bullet points.