In the configuration file for Jupiter perps alarms, we need an extension of the target column.
Normally we can use a target price, for example '123.23'. This needs to be extended to support a simple calculation.
So we could have this '100.0+10%' - this should result in the same behaviour as if I just had written '110'. Or '200-25%' would be the same as if I had written '150'.
This makes it easier to update the price if the liquidation price is know. Now you will not need to do a manual calculation on each price trigger update.
In the configuration file for Jupiter perps alarms, we need an extension of the target column.
Normally we can use a target price, for example '123.23'. This needs to be extended to support a simple calculation.
So we could have this '100.0+10%' - this should result in the same behaviour as if I just had written '110'. Or '200-25%' would be the same as if I had written '150'.
This makes it easier to update the price if the liquidation price is know. Now you will not need to do a manual calculation on each price trigger update.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In the configuration file for Jupiter perps alarms, we need an extension of the target column.
Normally we can use a target price, for example '123.23'. This needs to be extended to support a simple calculation.
So we could have this '100.0+10%' - this should result in the same behaviour as if I just had written '110'. Or '200-25%' would be the same as if I had written '150'.
This makes it easier to update the price if the liquidation price is know. Now you will not need to do a manual calculation on each price trigger update.
'Advanced' Jupiter perps alarm price triggerto 'Advanced' Jupiter perps alarm price target'Advanced' Jupiter perps alarm price targetto Support percentage expressions in alarm targets