is_active
get-method on it.
If it is not, please contact us via Telegram @swap.coffee DEV Chat.
Our recommendation for gas is 0.05 TON
. Excesses won’t be returned.
0.1 TON
for each message. Excesses will be returned.
If you’re using notifications, more gas may be needed.
0.1 TON
for each message. Excesses will be returned.
If you’re using notifications, more gas may be needed.
custom_payload
on burn so that users may specify withdrawal liquidity parameters
to secure the operation. You can read more about it in TL-B schemes section.
0.1 TON
for the transaction itself plus 0.05 TON
for every additional swap step after the first one.
So, for example, if you’re performing a direct swap, our recommendation is 0.1 TON
,
but if your swap route consists of 3 steps (A -> B -> C -> D), then our recommendation is 0.1 + 0.05 * 2 = 0.2 TON
.
Actual usage should be much lower and all the excesses will be returned.
If you’re using notifications, more gas may be needed.