1. What does Decimals mean?

Computers cannot precisely store floating-point numbers, so all numerical values on the blockchain need to be converted to integers for storage. When developers initially design a token, they need to determine its precision (decimals), which can be understood as the number of decimal places.

When configuring ChainBot monitoring, all numerical comparisons need to be done in the original format on the blockchain. For example, 100 ETH should be written as 100e18 because the decimals for ETH is 18.

2. What does 1e18, 1e6 mean?

These expressions are scientific notation for numbers; 1e18 means 1 multiplied by 10 to the 18th power, and 1e6 means 1 multiplied by 10 to the 6th power.

To facilitate entering integers, you can prioritize using scientific notation to specify accurate numbers.

3. How do I confirm a token's decimals?

You can check on the token page at https://etherscan.io/.

4. Is there an API available for direct integration?

Public API is under active preparation, stay tuned~

5. How do I determine which type of Bot to use when creating a new Bot?

Please read



6. How do I determine which Symbol to choose in Bot monitoring configuration?

Condition(s) Description

7. What is the difference between Bot and List?

A Bot is individual, while a List contains a group of Bots.

You can add multiple related Bots to a List for easier management, for example, Bots related to a specific project.

Both Bots and Lists can be shared, allowing other users to quickly subscribe to the quality Bots/Lists you create or discover.

8. How to handle reaching the limit of free alerts?

Currently, the number of free alerts is 500, which typically suffices for most needs. When the alert limit is reached, the ChainBot platform will send a notification to your configured Channel. If you still hit the alert limit, please contact the administrator via a private message on Discord.

9. What is the methodId of a transaction? How do I find the methodId of a target transaction?

In the EVM system, each method defined by a contract generates a corresponding methodId as an identifier. The methodId is fixed at 4 bytes, for example: 0x38926b6d

In a blockchain explorer, select the corresponding transaction and scroll to the bottom where you can see the methodId. For instance:

Example of a transaction in Uniswap v2:

Example of a transaction in Seaport 1.1:

Last updated