🎉ChainBot Introduction

https://chainbot.io

ChainBot is a powerful real-time data monitoring and alerting platform. It can be customized and automated to monitor data on-chain or from third-party platforms based on your needs, and provide real-time feedback and alerts through channels you set up, allowing you to stay on top of project progress.

ChainBot currently supports the following main categories of monitoring:

1. On-chain Event Bot Monitoring

2. On-chain DEX Bot Monitoring

3. On-chain Transaction Bot Monitoring

4. On-chain Value Bot Monitoring

5. NFT Bot Monitoring

6. Third-party Snapshot Bot Monitoring

7. On-chain Block Bot Monitoring

8. On-chain Arweave Bot Monitoring

What Key Problems Does ChainBot Solve?

ChainBot platform is designed to be more flexible and general at the underlying level. The following scenarios are just high-frequency examples. For more features, please refer to the "Monitoring/Bot" section.

1. When a whale withdraws a large amount of liquidity from a pool, you need to receive the message promptly and make your next plan.

2. Real-time price change alerts in DEX, for example, if a new shitcoin is listed in the DEX, you need to keep an eye on its price.

3. Monitoring when the NFT floor price falls below the issuance price.

4. Monitoring alerts for high-quality articles on mirror, so you can be the first to learn new content.

5. Monitoring hacker address behavior, for example, when funds are transferred in or out of an FTX hacker address, you need to receive alert notifications immediately.

6. Sending alert notifications when the project team you are following operates a relevant proposal on snapshot, instead of refreshing the official UI from time to time.

Terminology

1. Bot

   A set of rules and alert templates for continuous monitoring of different types of data, referred to as a Bot. Bots can be private or public, and any user can subscribe to public Bots. When a Bot meets the configured conditions, it will send alert notifications to all Subscriptions that subscribed to the Bot according to the alert Channel set by the user.

2. Condition(s)

   Conditions for Bot to trigger alerts;

   Condition(s) support comparison of multiple fields. When multiple fields are filled in, the logical relationship for triggering alerts is “AND”, meaning an alert will only be triggered when both Condition A and Condition B are met;

3. Subscription

   Users need to set the sending method and frequency of Bot alerts through Subscription. A Subscription can only belong to one Bot, but a Bot can be subscribed multiple times by different users;

4. List

   A collection of multiple Bots. Users can set different types of Bots into different Lists according to their needs for easy management.

5. Fork

   Completely copies all data of the original Bot.

6. Contract

   Smart contracts deployed on the blockchain.

7. Notify Channel

   The alert channel and configuration for receiving messages, such as Slack/Pushover;

8. Notify Template

   Template content for subscription alerts. When configuring a Bot, the platform will automatically generate a default alert template, and users can change the alert content according to their needs.

9. DataSources

   Data sources supported by the ChainBot platform architecture.