A detailed description of the function in the documentation does not necessarily mean that it can already be used.
In TermMax, I would be especially checking this right now using the example of Smart Unwind.
The mechanism itself is described quite specifically: the user sets a condition for an early exit from a position at a target rate or price.
Because of this level of detail, it’s easy to conclude that the function is already available in V2.
But the current TermMax website still places Smart Unwind in the "What's Next" section, and the Leverager documentation explicitly states that the function has not been launched yet.
And for me, this is a much more useful check than simply reading a list of the protocol’s possible capabilities.
Before building a strategy around a new function, I would verify its status separately:
it is already working,
it is only planned,
or for now it’s only described in the documentation.
In DeFi, the difference between "the mechanics are already described" and "the function is already available" can be more important than it seems.
@TermMax #TermMax
In TermMax, I would be especially checking this right now using the example of Smart Unwind.
The mechanism itself is described quite specifically: the user sets a condition for an early exit from a position at a target rate or price.
Because of this level of detail, it’s easy to conclude that the function is already available in V2.
But the current TermMax website still places Smart Unwind in the "What's Next" section, and the Leverager documentation explicitly states that the function has not been launched yet.
And for me, this is a much more useful check than simply reading a list of the protocol’s possible capabilities.
Before building a strategy around a new function, I would verify its status separately:
it is already working,
it is only planned,
or for now it’s only described in the documentation.
In DeFi, the difference between "the mechanics are already described" and "the function is already available" can be more important than it seems.
@TermMax #TermMax
