# Key Behavior Highlights

**General**

* When sending any ERC20 token, an allowance would be automatically provided by the airdrop for successful transactions.
* When execution is in progress for any wallet, it will not be shown in the drop-down list when creating a new task.
* Default values when the user provides invalid input for each field:
* Balance to use: 25%
* Time delay: 300-600 seconds
* Number of transactions: 1

**Swap**

* Swaps currently supported by Airdrop are ETH->USDC and USDC->ETH
* When the user selects 100% of wallet balance for swaps then the amount percentage considered would be 95% when sending ETH as some ETH has to be kept for gas for future transactions.
* Swap pairs would be randomly picked based on the amounts present for the tokens.
* Pairs for which swap has to be done would be picked randomly, so it is recommended to always choose at max 75% of the total balance percentage to be used else there might be scenarios where swaps might fail due to less ETH balance for gas or users might end up with very less ETH liquidity.
* When 100% is selected in UI for swaps then 90% is considered to not use up all the ETH liquidity.

**Liquidity**

* Airbot currently supports add/remove liquidity for ETH<->USDC pool.
* When adding liquidity, if the user selects 50% then firstly 25% of the ETH balance would be swapped to USDC after which USDC & ETH pair liquidity would be added to the pool.
* When 100% is selected in UI for adding liquidity then 90% is considered so ETH liquidity is not consumed fully.
* If liquidity is present for more then one platform then liquidity would be removed from one random platform.<br>

**Mint**

* Currently Tevaera mint is supported by Airbot which supports minting of only 1 NFT, if users try to mint more NFT transactions would auto fail.

**Bridge**

* Bridging takes approximately 15-30 minutes from ethereum mainnet to zkSync mainnet.
* Bridging will always be done with ETH.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://airbotfarm.gitbook.io/airbot/general/key-behavior-highlights.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.