Custom Settings

How to interact with the Titan platform with your own custom settings

Extra User Parameters

In the settings button at the top right of the swap box, users can configure their transactions and routes in a variety of ways including:

• Max Slippage

• Transaction Fee Methods

• AMM Exclusion

Max Slippage

Slippage is the amount that your final trade differs by from your quoted price when executing a trade. This could be due to several reasons, but the most common is that someone has already traded ahead of you. This setting exists so that if the slippage exceeds your max tolerance, the trade is reverted even though the transaction fee is still taken by the blockchain.

There are 2 slippage settings that the user can modify:

• Base Tokens: Any token pair that is not a stablecoin to stablecoin pair or SOL/LST or LST/SOL pair.

• Stable/LST: Any token pair that is a stablecoin to stablecoin pair or SOL/LST or LST/SOL pair

These 2 different settings are used to reflect that some tokens are very closely related in value and therefore have far less slippage involved.

For Titan quotes, the transaction is simulated to see what the user would get at that point in time when the swap button is pressed. If this would result in a revert due to slippage tolerances being exceeded, the attempted swap would result in an error message.

Transaction Fee Methods

Titan currently supports three types of broadcast mode fees in order to process transactions with plans to add more soon. These currently are:

• Priority Fees (https://solana.com/developers/guides/advanced/how-to-use-priority-fees)

• Jito Fees (https://docs.jito.wtf/)

• Nozomi (https://use.temporal.xyz/)

All broadcast modes have the same options included.

With Auto fee mode, Titan determines the appropriate fee level to be paid leveraging 3rd party services such as Helius, Triton, and Jito depending on how fast the user wishes to process the transaction. A max cap on the fee is also set here in case the suggested fee goes above what the user is comfortable paying.

With Custom fee mode, the user sets the exact fee they wish to pay.

Some wallets may enforce a minimum priority fee to be paid per transaction for Jupiter transactions. We are currently working on finding a better solution.

AMM Exclusion

Users also have the option to exclude various AMMs from the chosen routes for whatever reason.

The selected AMMs will then be excluded from generated routes. AMMs have been normalized across DEX Aggregators so that the user does not need to know how each DEX Aggregator handles the naming and identification of various DEXes.