|
Description: |
Expected duration: Ongoing
I run a web2 agency but am looking to partner with a developer or team experienced in the web3 space to create a crypto Telegram bot.
The bot needs to operate similarly to 'Oomer Bots' BUMPBUY feature and include all necessary functions for comprehensive operation: https://docs.oomerbot.xyz/telegram-bots-info/volume-bot/bumpbuy-microbuy. The primary goal is to help tokens appear on trending sections of token trackers like Dexscreener.
I’ve developed a partial script that includes basic functions like wallet creation and fund disbursement, but it has issues executing token purchases successfully and needs further development. I am seeking someone to either develop the bot from scratch or use an existing codebase if it reduces cost and development time.
Telegram Bot Development: Scope of Work
Objective
Implement bumpbuy functionality and related features, enabling users to execute volume transactions on the Base network via Uniswap while managing subscriptions, fees, and operational logic.
Core Features
1. Bumpbuy Functionality
Automate token purchases on the Base network's Uniswap (V2/V3).
Commands:
/bumpbuy [token_address] [speed: slow|medium|fast]
Example: /bumpbuy 0xTokenAddress medium
Speeds:
Slow: 3 wallets, transactions every 15 seconds.
Medium (default): 10 wallets, every 8–10 seconds.
Fast: 25 wallets, every 4–6 seconds.
Wallet Management:
Generate 10 persistent wallets per user using secure HD Wallet logic. ETH is dispersed proportionally based on the speed chosen.
Lifecycle:
Runs until canceled with /cancelbumpbuy. Supports tokens with Uniswap liquidity pools.
2. Subscription Model
Users must subscribe to access bumpbuy.
Fee: $RKT equivalent to $5/week (calculated dynamically).
Example: If $RKT = $1, the fee is 5 $RKT; if $RKT = $2.5, the fee is 2 $RKT.
Burn Mechanism:
$RKT is sent to a predefined burn wallet upon validation via Base blockchain smart contracts.
3. Premium Fee Collection
Fees deducted based on user input:
Standard Fee: 1% of bumpbuy amount.
Discounted Fee: 0.5% for tokens deployed by Clanker contract addresses (to be provided).
Fees are deducted pre-operation and sent to the operator’s wallet.
4. Minimum ETH Requirement
Ensure sufficient funds for gas and operations.
Threshold: 0.05 ETH minimum balance.
Logic:
If balance < 0.05 ETH: Reject with an error message.
If balance ≥ 0.05 ETH: Deduct fees and proceed.
5. User Feedback & Reporting
Provide feedback and summaries:
Pre-Operation:
ETH balance.
Fee amount.
Remaining ETH for bumpbuy.
Post-Operation Summary:
Total ETH used.
Number of wallets.
Remaining balance.
6. Core Bot Commands
User-friendly TG commands:
/start: Introductory bot info.
/help: List of commands and examples.
/bumpbuy [token_address] [speed]: Start bumpbuy.
/cancelbumpbuy: Cancel bumpbuy.
/balance: Show ETH/token balances.
/withdraw: Withdraw funds.
/subscribe: Start subscription process.
Phased Implementation
Bumpbuy: Wallet generation, ETH dispersal, Uniswap integration, speed options, cancellation commands.
Subscription: Validate weekly $RKT payments, automate burn wallet transactions.
Premium Fee Collection: Deduct fees pre-operation.
User Feedback: Pre-checks and post-operation summaries.
Documentation Requirements
Thorough documentation for:
Usage: Commands, fees, subscriptions, wallet management.
Logic: Wallet generation, transaction flow, fee deductions.
Technical: Supported networks/tokens, error handling.
Align documentation with Oomer Docs.
Additional Notes
Ensure compatibility with Base network and Uniswap (V2/V3).
Securely handle fees and collected amounts.
Implement robust error handling and logging.
I’m open to ongoing support post-project, either ad-hoc or via retainer with agreed service levels. Please clarify any uncertainties. If it's clear you haven't read this, I will decline your proposal. Provide a timeframe and price; do not ask for my budget unless offering options with prices.
Thank you! |
