Group Notification System
Advanced Features

Advanced Features

Explore the advanced capabilities of MoBots Buy Bot. Learn about multi-bot management, dynamic DEX identification, creator permissions, and technical features that power the system.


Multi-Bot Management

Bot Limits

Free Tier: 2 bots maximum per user

  • βœ… One bot per Telegram group
  • βœ… Different tokens for different groups
  • βœ… Independent settings for each
  • βœ… Manage all from unified interface

Use Cases

Multiple Token Projects

Bot 1: Main token in community group

Bot 2: Governance token in DAO group

Track different tokens for different communities under one account.

Segmented Communities

Bot 1: Same token in public group

Bot 2: Same token in VIP/holder group

Different minimum amounts for different audiences.

Testing & Production

Bot 1: Live token in main community

Bot 2: Test token in development group

Safely test configuration changes.

Managing Multiple Bots

Access Your Bots:

  1. Send /start to @MobotsBuyBot
  2. Click "πŸ€– My Buy Bots"
  3. See all your bots listed
  4. Shows usage: "You have 2/2 bots"

Select Bot to Manage:

  1. Click group name from list
  2. Access that bot's settings
  3. Make changes independently
  4. Other bots unaffected

Bot Capacity Management

When at maximum capacity (2/2):

⚠️ Must delete a bot to create new one:

  1. Choose bot to remove
  2. Click "❌ Delete Bot"
  3. Confirm deletion
  4. Space freed for new bot
  5. Create new configuration

Remember: Deletion is permanent. All settings lost.


Dynamic DEX Identification

The bot automatically identifies which DEX each buy came from using sophisticated smart contract queries.

How It Works

Detection Process:

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

Supported DEXes

Uniswap V2

Factory queries for pool matching

PancakeSwap V2

Factory queries for pool matching

OctoSwap V2

Factory queries for pool matching

TayaSwap V2

Factory queries for pool matching

Purps Exchange V2

Factory queries for pool matching

Madness Finance V2

Factory queries for pool matching

Benefits

  • βœ… Accurate - Always shows correct DEX
  • βœ… Automatic - No manual configuration
  • βœ… Real-time - Identifies on each buy
  • βœ… Reliable - Backed by smart contracts
  • βœ… Transparent - Verifiable on-chain

Legacy Support

For bots created before DEX identification feature:

  • Old notifications may show "Unknown"
  • Reconfigure bot to enable DEX identification
  • New buys will show correct DEX name
  • No data loss during reconfiguration

Creator-Only Management

Security feature ensuring only the bot creator can modify settings.

Permission System

Creator Can:

  • βœ… Change token/pools
  • βœ… Update notification image
  • βœ… Set minimum amount
  • βœ… Add/remove social links
  • βœ… Activate/deactivate bot
  • βœ… Delete bot

Other Admins Cannot:

  • ❌ Access bot settings
  • ❌ Modify configuration
  • ❌ Delete or deactivate
  • ❌ Change any settings

How It Works

  1. Bot Setup - Your Telegram user ID recorded as creator
  2. Access Attempt - Anyone tries to manage bot
  3. Verification - Bot checks if user ID matches creator
  4. Authorization - Only creator can proceed
  5. Others Blocked - Non-creators see access denied

Benefits

  • πŸ”’ Security - Prevents unauthorized changes
  • πŸ”’ Control - Creator maintains full authority
  • πŸ”’ Trust - Community can't accidentally break config
  • πŸ”’ Accountability - Clear ownership
  • πŸ”’ Protection - Settings safe from tampering

Anonymous Admin Mode

⚠️ Important for Setup:

If you have "Remain Anonymous" enabled in group admin settings:

  1. Temporarily disable it during bot creation
  2. Bot needs to identify you as creator
  3. Re-enable after setup complete
  4. Subsequent management works normally

Why: Anonymous mode hides your user ID, preventing creator registration.


Group Admin Permissions

Required Permissions

For bot to function, it needs:

Essential:

  • βœ… Post Messages - Send buy notifications

Not Required:

  • ❌ Delete messages
  • ❌ Ban users
  • ❌ Pin messages
  • ❌ Manage video chats
  • ❌ Any other admin permissions

Granting Permissions

  1. Open your Telegram group
  2. Tap group name β†’ Administrators
  3. Click "Add Admin"
  4. Select @MobotsBuyBot
  5. Enable: "Post Messages"
  6. Disable: All other permissions (optional)
  7. Save changes

Permission Troubleshooting

If notifications not sending:

  1. Verify bot is admin
  2. Check "Post Messages" is enabled
  3. Ensure bot wasn't removed
  4. Verify group privacy settings allow bots

Event Monitoring System

Technical details of how the bot monitors blockchain events.

Monitoring Architecture

Block Processing:

  • Checks new blocks every 2 seconds
  • Concurrent event handling
  • Multiple monitors run independently
  • Thread pool: 32 workers

Event Detection:

  • Monitors Transfer events
  • Filters transfers FROM pool (buys)
  • Ignores transfers TO pool (sells)
  • Applies minimum amount filter

Transaction Analysis:

  • Reads transaction receipt
  • Calculates token amounts
  • Identifies MON spent
  • Determines buyer address
  • Matches DEX via factory

Performance Optimizations

Transaction Caching

Cache processed transaction IDs

  • Prevents duplicate notifications
  • 100-block sliding window
  • Automatic cleanup
  • Memory efficient

Async Processing

Non-blocking operations

  • Async blockchain queries
  • Concurrent event handling
  • Queued message delivery
  • High throughput

DEX Caching

Cache factory query results

  • Faster DEX identification
  • Reduced RPC calls
  • Session-level cache
  • Improves response time

Reliability Features

  • βœ… Retry logic - Failed notifications retried
  • βœ… Error handling - Graceful degradation
  • βœ… Queue system - Messages never lost
  • βœ… Fallback modes - Text-only if image fails
  • βœ… State persistence - Survives restarts

Data Storage & Privacy

What's Stored

Per Bot Configuration:

  • Group chat ID (public)
  • Group chat title (public)
  • Creator Telegram user ID
  • Token contract address (public)
  • Pool addresses (public)
  • DEX names
  • Notification image URL
  • Minimum buy amount
  • Social media links (public)
  • Active/inactive status

What's NOT Stored

  • ❌ Private keys or wallet data
  • ❌ Personal information
  • ❌ Chat messages
  • ❌ User data beyond creator ID
  • ❌ Transaction private details
  • ❌ Sensitive business info

Privacy Guarantees

πŸ”’ All displayed data is publicly available on-chain

  • Token addresses: Public blockchain data
  • Transaction hashes: Publicly verifiable
  • Buyer addresses: Public wallet addresses
  • Pool information: Public smart contracts
  • DEX details: Public protocol data

No private or sensitive information is collected or displayed.


Integration with Monad Blockchain

Network Details

Blockchain: Monad

Chain ID: 143

Native Token: MON

Block Time: ~1 second

Explorer: https://monadvision.com/ (opens in a new tab)

RPC Endpoint: (configured internally)

Smart Contract Interactions

Token Contract Queries:

decimals() β†’ Get token decimal places
symbol() β†’ Get token symbol name
Transfer event β†’ Monitor token movements

Factory Contract Queries:

getPair(tokenA, tokenB) β†’ Find pool address
allPairs(index) β†’ Enumerate all pools

Pool Contract Analysis:

token0() / token1() β†’ Identify pool tokens
getReserves() β†’ Check liquidity depth

Dexscreener Integration

Notifications link to Dexscreener for:

  • Real-time price charts
  • Trading volume data
  • Liquidity information
  • Pool statistics
  • Historical price data

Scalability

How the Bot Scales

Per-Bot Scalability

  • βœ… Handles high-volume tokens
  • βœ… Multiple pools simultaneously
  • βœ… Thousands of transactions/day
  • βœ… No performance degradation

Multi-Bot Scalability

  • βœ… Independent monitoring per bot
  • βœ… Separate event loops
  • βœ… No resource contention
  • βœ… Efficient thread pooling

Network Scalability

  • βœ… Optimized RPC usage
  • βœ… Caching strategies
  • βœ… Batch processing where possible
  • βœ… Rate limiting compliance

Future Features

Planned enhancements for MoBots Buy Bot:

Coming Soon:

  • πŸ”„ Automatic new pool detection
  • πŸ“Š Analytics dashboard
  • 🎨 Customizable notification templates
  • πŸ’° USD value display option
  • πŸ”” Custom alert thresholds
  • πŸ“ˆ Volume tracking features
  • 🎯 Buyer address whitelisting
  • 🌐 Multi-chain support

API & Webhook Integration

Currently in development:

Potential Features:

  • Webhook notifications to external services
  • REST API for buy data
  • Custom notification endpoints
  • Integration with Discord, Twitter auto-posting
  • Programmatic bot management

πŸ’‘ Interested in API access? Contact the MoBots team to discuss enterprise features.


Next Steps

πŸ”§ Technical Details

Deep dive into smart contract interactions and blockchain monitoring.

❓ FAQ

Frequently asked questions and quick answers.

πŸ’Ό Use Cases

Real-world implementation examples and strategies.