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.
Managing Multiple Bots
Access Your Bots:
- Send
/startto @MobotsBuyBot - Click "π€ My Buy Bots"
- See all your bots listed
- Shows usage: "You have 2/2 bots"
Select Bot to Manage:
- Click group name from list
- Access that bot's settings
- Make changes independently
- Other bots unaffected
Bot Capacity Management
When at maximum capacity (2/2):
β οΈ Must delete a bot to create new one:
- Choose bot to remove
- Click "β Delete Bot"
- Confirm deletion
- Space freed for new bot
- 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:
- Buy detected on pool address
- Bot queries all DEX factory contracts
- Matches pool to factory
- Identifies DEX name
- Displays in notification
- 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
- Bot Setup - Your Telegram user ID recorded as creator
- Access Attempt - Anyone tries to manage bot
- Verification - Bot checks if user ID matches creator
- Authorization - Only creator can proceed
- 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:
- Temporarily disable it during bot creation
- Bot needs to identify you as creator
- Re-enable after setup complete
- 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
- Open your Telegram group
- Tap group name β Administrators
- Click "Add Admin"
- Select @MobotsBuyBot
- Enable: "Post Messages"
- Disable: All other permissions (optional)
- Save changes
Permission Troubleshooting
If notifications not sending:
- Verify bot is admin
- Check "Post Messages" is enabled
- Ensure bot wasn't removed
- 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
Transferevents - 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
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 movementsFactory Contract Queries:
getPair(tokenA, tokenB) β Find pool address
allPairs(index) β Enumerate all poolsPool Contract Analysis:
token0() / token1() β Identify pool tokens
getReserves() β Check liquidity depthDexscreener 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
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.