Comment on page
This page intends to create a wiki with most common sources of Troubleshooting, check it first if you experience a problem with Tortle Ninja
This feature is only available on a Combo Trigger related to a Perpetual Dex position. The feature allows us to execute a secondary Combo trigger that will close the position automatically when the risk of liquidation is high, and send it to the next node.
To do this, we use a formula that take as reference the entry price and the liquidation price provided by GMX.
For Long Positions:
liquidationPrice + ((entryPriceUSD - liquidationPrice) * PERCENTAGE_THRESHOLD)
For Short Positions:
liquidationPrice - ((liquidationPrice - entryPriceUSD) *PERCENTAGE_THRESHOLD)
In general, this feature works extremely well and recovers an important part of your principal. In our internal tests, it has been successful more than 9 out of 10 times. However, it doesn't always work. Our system relies on Chainlink price feeds, and our oracle is not easy to manipulate. However, price action often moves faster than the oracle. If there is a sudden market movement that surpasses the liquidation price before the Chainlink oracle gives us our exit price, the operation will be liquidated by GMX and the position will be automatically closed.
You can create an additional trigger that will close the position based on a condition using our Price Feeds Combo trigger. This will allow you to exit the position when the oracle dictates a certain asset price. You can adjust the level of risk you want to assume manually, creating another layer of protection in addition to what we already provide.
To create another layer of protection just setup the Close position Trigger manually, at the price you prefer.
Tortle Ninja developers frequently change the UX, sometimes multiple times per week. This can result in certain components being stored on your computer's local storage. To clear this, press F12 on your computer, then navigate to Application > Local Storage, then clear it. This will remove all old data.
Tortle sometimes bundles over 100 transactions into one, creating a large transaction that may not fit in the first blocks that the blockchain is mining. As a result, transactions may sometimes take a few extra seconds to process. However, Tortle users save a significant amount of gas fees in return.
That error is related to some RPCs on Fantom. Tortle uses data to calculate its KPIs, but there are some RPCs that don't provide the necessary information. In that case, we suggest changing to another RPC provider.
I encountered an error while trying to connect my wallet "Login Error: Timestamp is too old", What should I do?
To troubleshoot this issue, it's important to ensure that your device's time is accurate, and don't forget to clear your cache and reload your page too. Even a minor deviation of a few minutes from the correct time can result in this problem.
It seems like you've encountered an error when gas estimation fails. Don't worry, this happens when gas estimation is not successful before executing a transaction. Sometimes, network congestion can cause this problem. If you're experiencing this issue, just wait a few minutes and try again when the network conditions are better.