Group Notification System
Pool Selection

Pool Selection & Monitoring

Understanding how to select and monitor liquidity pools is crucial for comprehensive buy tracking. This guide explains pools, monitoring options, and how to make the best choices for your project.

Understanding Liquidity Pools

What is a Liquidity Pool?

A liquidity pool is a smart contract that holds two tokens (a trading pair) and enables decentralized trading. For buy tracking, you need pools where your token is paired with MON (or wrapped MON).

Pool Structure

TOKEN / MON Liquidity Pool
├── Contains: Your TOKEN
├── Contains: MON (or WMON)
├── Located on: Specific DEX
└── Address: 0x...

Why Pools Matter

  • 📊 Each DEX has its own separate pool
  • 📊 Buys can happen on any DEX where liquidity exists
  • 📊 Different pools = different trade volumes
  • 📊 Bot must monitor all pools to catch every buy

Pool Discovery

When you configure your bot, it automatically searches for all liquidity pools.

Discovery Process

  1. You enter token address
  2. Bot queries all DEX factory contracts
  3. Searches for TOKEN/MON pairs
  4. Returns all pools found
  5. Displays them for selection

Example Discovery Result

✅ Found 4 pool(s) for TOKEN

[🌐 Monitor All Pools]

[🔄 Uniswap V2]      [🔄 PancakeSwap V2]
[🔄 OctoSwap V2]     [🔄 TayaSwap V2]

Each button represents a pool on a specific DEX.

Pool Selection Options

You have two main strategies for monitoring:

Option 1: Monitor All Pools

Recommended for most projects

✅ Tracks buys across every DEX

✅ Comprehensive coverage

✅ No manual management

✅ Catch every purchase

✅ Set and forget

Option 2: Specific Pools

For targeted tracking

✅ Focus on primary DEX

✅ Test before full rollout

✅ Promote specific exchange

✅ Control which DEXes shown

✅ Flexible selection

Monitor All Pools (Recommended)

How It Works

Click "🌐 Monitor All Pools" during setup to automatically track every discovered pool.

Benefits

📊 Complete Coverage

No missed buys regardless of DEX. Captures 100% of buying activity.

⚡ Simplicity

One click setup. No need to know which DEXes matter.

🔍 Market Insights

See which DEXes get the most volume. Learn where your community trades.

⏱️ Time Saving

No manual pool management. Bot handles everything automatically.

Best For

  • ✅ New token launches
  • ✅ Multi-DEX presence
  • ✅ Maximum visibility
  • ✅ Comprehensive tracking
  • ✅ Projects with growing liquidity

Setup Steps

  1. Enter your token address
  2. Bot discovers all pools
  3. Click "🌐 Monitor All Pools"
  4. ✅ All pools are now monitored
  5. Start receiving notifications from all DEXes

💡 Pro Tip: "Monitor All Pools" only monitors currently existing pools. If you add liquidity to a new DEX later, you'll need to reconfigure the bot to include it.

Monitor Specific Pools

How It Works

Click individual DEX buttons to select specific pools you want to monitor.

When to Use

🎯 Focused Tracking

Your main liquidity is on one DEX. You want to highlight that specific exchange.

Example: Only monitor Uniswap V2 where you have the deepest liquidity.

🧪 Testing Phase

Testing the bot before full deployment. Start with one pool, expand later.

Example: Monitor OctoSwap first, add others after verifying it works.

🤝 Partnership Promotion

Promoting a specific DEX partnership. Want to highlight buys on that DEX.

Example: Exclusive partnership with PancakeSwap, only track that DEX.

📊 Volume Control

High volume on one DEX causes spam. Monitor smaller DEXes only.

Example: Exclude main DEX to reduce notifications, keep smaller ones.

Setup Steps

  1. Enter your token address
  2. Bot discovers all pools
  3. Click individual DEX buttons (e.g., "🔄 Uniswap V2")
  4. Select as many as you want
  5. ✅ Only selected pools are monitored

Multiple Pool Selection

You can select multiple specific pools:

Selected:
✅ Uniswap V2
✅ PancakeSwap V2

Not Selected:
❌ OctoSwap V2
❌ TayaSwap V2

Bot will only monitor Uniswap V2 and PancakeSwap V2 in this example.

Multi-Pool Monitoring

How It Works

The bot can monitor multiple pools simultaneously, each independently tracked.

Technical Details

  • ✅ Each pool monitored separately
  • ✅ Transfer events tracked per pool
  • ✅ DEX automatically identified
  • ✅ No performance impact
  • ✅ No limit on pool count

Notification Behavior

Each buy generates ONE notification showing:

  • Which pool (DEX) it came from
  • All standard buy information
  • Separate notifications for each buy

Example:

  • Buy on Uniswap → 1 notification (shows "Uniswap V2")
  • Buy on PancakeSwap → 1 notification (shows "PancakeSwap V2")
  • Both happen → 2 notifications (one for each)

Changing Pool Selection

You can change which pools you're monitoring at any time.

How to Change

  1. Go to bot management
  2. Click "🔄 Change Token/Pool"
  3. Enter same token address (or new one)
  4. Select different pools
  5. ✅ Monitoring updates immediately

What Happens

  • ❌ Old pool monitors stop
  • ✅ New pool monitors start
  • 📊 No data loss
  • ⚡ Instant switch
  • 🔄 All other settings preserved

Example Scenarios

Scenario 1: Add New DEX

You added liquidity to TayaSwap. Want to include it.

Old: Monitoring Uniswap V2 only
Action: Change Token/Pool → Select All Pools
New: Monitoring Uniswap V2 + TayaSwap V2

Scenario 2: Remove Spammy DEX

One DEX has too much volume, causing spam.

Old: Monitoring All Pools
Action: Change Token/Pool → Select Specific (exclude spammy one)
New: Monitoring 3 of 4 DEXes

Scenario 3: Switch to New Token

Launching new token, want to monitor that instead.

Old: Monitoring TOKEN_A
Action: Change Token/Pool → Enter TOKEN_B address
New: Monitoring TOKEN_B on all its pools

Pool-Related Considerations

New Liquidity Pools

⚠️ Important: If you add liquidity to a new DEX after initial setup, the bot will NOT automatically detect it. You must reconfigure to include the new pool.

How to add new pools:

  1. Add liquidity to new DEX
  2. Go to "🔄 Change Token/Pool"
  3. Re-enter token address
  4. Select all pools (including new one)
  5. ✅ New pool now monitored

Removed Liquidity

If you remove liquidity from a DEX:

  • Bot continues monitoring that pool
  • No notifications (no buys happening)
  • No harm in keeping it monitored
  • Can remove via reconfiguration

Multiple Pools Same DEX

If you have multiple pools on the same DEX (rare):

  • Bot identifies them separately
  • Both monitored if using "Monitor All"
  • Notifications show the same DEX name
  • Technically separate pool addresses

DEX Identification

How It Works

For each buy, the bot automatically determines which DEX was used.

Identification Process

  1. Buy detected on pool address
  2. Bot queries all factory contracts
  3. Matches pool to specific factory
  4. Identifies DEX name
  5. Displays in notification

Supported DEX Names

The bot can identify these DEXes:

✅ Uniswap V2

✅ PancakeSwap V2

✅ OctoSwap V2

✅ TayaSwap V2

✅ Purps Exchange V2

✅ Madness Finance V2

Unknown DEXes

If a DEX isn't recognized:

  • Shows as "Unknown"
  • Still tracks the buy
  • Contact support to add DEX support

Best Practices

✅ Do

  • Monitor all pools for comprehensive tracking
  • Reconfigure when adding new liquidity
  • Test with small buy after setup
  • Check which DEXes get most volume
  • Keep pool selection updated
  • Use insights to guide liquidity strategy

❌ Don't

  • Assume new pools auto-detect
  • Monitor wrong token address
  • Forget to verify pool selection
  • Ignore DEX distribution insights
  • Skip reconfiguration after liquidity changes
  • Monitor too few pools

Pool Monitoring Strategies

Strategy 1: Full Coverage (Recommended)

Setup:

  • Monitor all pools
  • Set moderate minimum amount
  • Track DEX distribution
  • Adjust based on volume

Best for: Most projects, comprehensive tracking

Strategy 2: Primary DEX Focus

Setup:

  • Monitor only main DEX
  • Lower minimum (catch more buys)
  • Promote specific DEX
  • Test before expanding

Best for: Single DEX partnerships, focused campaigns

Strategy 3: Volume-Based Selection

Setup:

  • Monitor high-volume DEXes only
  • Higher minimum on main DEX
  • Lower minimum on smaller DEXes
  • Balance notification frequency

Best for: High-volume tokens, spam control

Next Steps

💡 Best Practices

Learn optimization strategies for community engagement.

🔧 Advanced Features

Explore advanced bot features and management.

🛠️ Troubleshooting

Fix common pool-related issues.

NotificationsBest Practices