💸Compensation and Cases
AKBot is a bot focused on trading on the Solana blockchain. To ensure the policy is clear and transparent, the scope of compensation, compensation limits, and special cases are explained below.
I.Cases Eligible for Compensation
1
Token migrated to Raydium Liquidity Pool V4
Compensation
After the token migrates to Raydium Liquidity Pool V4, selling in this pool is currently not supported. Such cases can be compensated according to the rules.
2
Sell failure
Compensation
In some scenarios, multiple sell conditions may be triggered at the same time. Since the actual remaining amount is already less than the planned sell amount, the subsequent sell will fail because the sell amount exceeds the remaining amount.
3
Sell not triggered
Compensation
Because the user had just created a Nonce account, the system had not yet read the user’s configuration.
II.Cases Not Eligible for Compensation
1
Creator change
No compensation
If the creator change is completed within 1 slot, the bot cannot guarantee that the sell order will also be completed within that same 1 slot. This type of situation is an execution deviation caused by extremely short on-chain changes.
2
Incorrect lightning sell time setting
No compensation
If the user sets the lightning sell time to 600ms, the bot usually cannot complete the sell within 1 slot. This is due to the time setting itself not matching the actual slot rhythm on-chain, and is not an abnormal situation. (1 second = 1000ms, and on the Solana chain, 1 second is approximately equal to 2 ~ 2.5 slots.)
4
Configuration update synchronization delay
No compensation
Because the server needs time to synchronize configurations, all configuration changes made by the user to the Bot usually have a synchronization delay of 10 to 30 seconds. This delay is normal.
5
Block fork
No compensation
Due to changes in the current market environment, the staking status of some validator nodes has changed. As a result, some individual validator nodes may sometimes filter certain transaction requests, causing the user’s transaction to fail to be included in the expected block and only be confirmed in a later block.
This type of situation is an objective issue caused by on-chain infrastructure and network conditions, not a bot issue.
6
Lower-than-expected profit
No compensation
Profits lower than expected or missing a better selling point are not within the scope of compensation.
7
Losing trade
No compensation
If the trade itself is already in a loss state, compensation cannot be provided due to a sell failure.
8
No drawdown and stop-loss set
No compensation
Drawdown and stop-loss are important risk control measures. If the user has not enabled these functions, any profit retracement or expanded loss caused by market fluctuations is a trading risk borne by the user and is not within the scope of compensation.
9
Timeout setting too long
No compensation
If the timeout setting is too long, 100% effectiveness cannot be guaranteed.
10
High gas fee
No compensation
Large Gas fees are bidding costs paid by the user on-chain and are subject to external competition, so they are not included in the scope of compensation.
11
Transactions involving USDC on Pump.fun AMM will be filtered.
No compensation
Transactions on Pump.fun AMM that include USDC will be filtered, because arbitrageurs commonly use USDC for trading. Therefore, sell functions that would otherwise be triggered by such transactions — including follow sell, take profit, stop loss, and similar features — will not take effect.
Case
Creator change
The token underwent a creator change at block 402452993. If the sell transaction occurs in the same block as the creator change or within the next few adjacent blocks, the sell may fail.
Block fork
The user had already submitted the on-chain request at block 403278209, and the timing of the request was very close to that of the smart wallet; however, the transaction was ultimately not included on-chain until block 403278212.。
III.Additional Compensation Notes
1.Compensation amount cannot exceed the fees already provided by the user
The compensation amount will be calculated based on the user’s historical fees that have already been incurred and provided. If the compensation amount is greater than the fees already incurred, then: the difference will first be recorded; compensation will be paid only after the user’s subsequent accumulated fees reach that difference.
2.Compensation cap
For losses caused by non-principle issues and non-force-majeure factors, the compensation cap is 5 SOL.
Last updated