Event Bot Monitoring

What is Event Bot Monitoring?

Event refers to the event in a smart contract. When a transaction occurs, it triggers the corresponding event, allowing users to trace the transaction by listening to the event.

Event monitoring achieves the purpose of monitoring specific behaviors on-chain by listening for events generated by smart contracts.

Typical Scenarios for Event Bot Monitoring

  1. DeFi Liquidity Event Monitoring

    1. DeFi liquidity exceeds the set threshold

    2. DeFi liquidity falls below the set threshold

  2. NFT Mint Event Monitoring

    1. An NFT starts minting

  3. Token Mint Event Monitoring

    1. Large token unlocks monitoring

  4. Others, etc.

Supported Data Sources

Data SourceTypeStability

Ethereum

on chain

Very high

BSC

on chain

High

Avalanche

on chain

High

Polygon Pos

on chain

High

Arbitrum

on chain

High

Optimism

on chain

High

Polygon zkEVM

on chain

High

ZkSync Era

on chain

High

Base

on chain

High

Scroll

on chain

High

Manta

on chain

High

ZKFair

on chain

High

Blast

on chain

High

Linea

on chain

High

B2

on chain

High

Merlin

on chain

High

How to Configure Event Bot Monitoring?

After logging into the ChainBot platform, click "Create Bot" in the upper right corner -> "Event Monitor".

⚠️ Note

When you select a specific Event, Conditions will automatically parse the fields contained within that Event, and they can only be fields from that specific Event. Therefore, Event and Conditions are corresponding relationships.

Info Description

Field NameDescriptionRequired

Name

Monitor Bot name

Yes

Chain

User-selected chain

Yes

Contract

User-selected contract

Yes

Event

User-selected event

Yes

Tags

Bot monitoring tags, useful for search

Yes

Conditions Description

Conditions in event monitoring dynamically change based on the selected Event.

For example, when monitoring the Approval event in the USDT contract, since the Event Approval(owner: address, spender: address, value: uint256) has three parameters, the fields available in conditions are also three: owner, spender, and value. Configure your parameters based on your conditions to achieve your goals.

Template Variable Description

VariableDescriptionExample

$block.time

Block where the event was generated

16073651

$tx.hash

Transaction hash that generated the event

transaction hash

$event.contract

Contract address that generated the event

16073651

$event.params.{abc}

Key fields parsed from the event

$event.params.tokens

$chain.explore

Prefix of the current chain's explorer

$subscription.id

Subscription alert ID

306310837801629120

$subscription.name

Subscription alert name

USDC New Mint

Default Notification Template

[ {$subscription.name} ]
  Contract: {$event.contract}
  Time: {$block.time}
  Explore: {$chain.explore}/tx/{$tx.hash}
  Created By ChainBot.io

Learn about alert notification templates?

Notification Message Example

[ CRV Liquidation Call Monitor ] Contract: 0x7d2768dE32b0b80b7a3454c06BdAc94A69DDc7A9 Amount: 187743.2161384799 CRV Time: 2022-11-23T02:09:23+08:00 Explore: https://etherscan.io/tx/0x47ffc7939cf8deed6a28357934f98402892b370ac2d3be0c6576f733f6d97b1e Created By ChainBot.io

Event Bot Monitoring Cases

Event Bot Case Study

Last updated