Python Telegram Bot and Node.js Optimization
Краткое
Freelancer Client is hiring: Python Telegram Bot and Node.js Optimization.
Location: Remote
Compensation: $70 USD (fixed)
Telegram Bot Developer (Python / Aiogram) + Minor Node.js Fixes (PumpPortal Integration)
What you'll do:
• 5% supply → developer
Requirements:
• Python / Aiogram
• Aiogram (latest version)
• Async handlers
• Clean callback structure
• Good UI/UX sense
• Experience with multi‑step flows
• Express
• Basic debugging
Nice to have:
• Experience with JITO bundles
• This is a small job — mostly UI cleanup and integration.
• Estimated delivery time
• Confirmation you can work for $70
Skills: JavaScript, Python, User Interface / IA, Software Architecture, Node.js, Backend Development, API Development, User Experience Research
Source: Freelancer Client via Remote / Online. Apply on the source website.
Оригинал
Telegram Bot Developer (Python / Aiogram) + Minor Node.js Fixes (PumpPortal Integration)
I already have a working system:
• A Node.js backend (index.js) that handles PumpPortal token creation, buys, sells, bundlers, auto‑dump, etc.
• A Python Telegram bot (bot.py) built with Aiogram that controls the whole launch flow.
I don’t need blockchain development.
I don’t need a new backend.
I don’t need a full rebuild.
I need someone who can read the existing code, understand how the bot and backend work together, and then clean it up, fix the integration, and upgrade the UI.
What needs to be done:
Rename “helpers” to “bundlers”
The system currently uses the word “helper” everywhere.
I want everything renamed to “bundler”, including variables, functions, database fields, logs, routes, and UI text.
Important:
Do NOT delete the helper logic.
Only delete the old “ helper strength” and “helper mode” options.
The bundler system stays exactly the same, just renamed.
Remove old helper UI options
The bot currently asks for helper mode and helper strength.
These must be removed completely from the bot UI.
Hardcode supply split
Every launch must automatically use:
• 5% supply → developer
• 95% supply → bundlers
This should not be shown to the user and should not be configurable.
Metadata handling
The user uploads a real photo in Telegram.
The bot must download the image bytes and send them directly to the backend using multipart/form-data.
The backend will upload the image to Pinata, build the metadata JSON, and upload the metadata JSON to IPFS.
The bot must collect:
• name
• symbol
• description
• image bytes
• optional social links (Twitter @, Telegram link, Website domain, Instagram @)
The bot sends these fields to the backend.
The backend handles all IPFS uploads.
Remove the metadata URI option.
The bot must not allow users to paste a metadata URI anymore.
Use JITO for everything except withdrawals
The backend must use JITO bundles for:
• dev buy
• bundler buys
• auto‑dump
• manual dump
• multi‑pool sells
• any PumpPortal buy/sell transaction
Do NOT use JITO for withdrawals.
Withdrawals should stay normal.
Improve bundler timing (profit optimization for users)
Bundlers should be updated to improve user profit.
This includes:
• Front‑loaded buys in the first 3–5 seconds
• Human‑like micro‑delays (200–600ms with randomness)
• Wave‑based buy patterns (60% → 30% → 10%)
• Whale‑style early buys (20–30% of SOL)
• Dynamic timing adjustments based on early volume
This makes the chart look more natural, attracts snipers, and increases the user’s exit price.
Fix the Telegram bot flow
The bot must follow this exact 9‑step flow:
Token name
Token symbol
Description
Upload photo
SOL amount to bundle (show the recommendations)
Bundler count (1–25)
Auto‑dump threshold
Social media link (Twitter / Telegram / Website / Instagram / Skip)
Confirmation step
The confirmation step must show the image and all details before launching.
Fix session handling
The bot currently gets stuck if the user sends unexpected input.
Fix stuck sessions, restarts, back buttons, and invalid input handling.
Fix backend routes
Some backend routes return inconsistent responses or missing errors.
Fix the launch route, add an image upload route, add a metadata builder route, clean up error handling, and update the payload format to match the new bot.
Tech Requirements:
Python / Aiogram
• Aiogram (latest version)
• Async handlers
• Clean callback structure
• Good UI/UX sense
• Experience with multi‑step flows
Node.js
• Express
• Basic debugging
• Understanding of PumpPortal API (bonus)
• Experience with JITO bundles
Budget: $70 USD (fixed)
This is a small job — mostly UI cleanup and integration.
To Apply:
Send:
• Examples of Telegram bots you’ve built
• Your Aiogram experience
• Your Node.js experience
• PumpPortal experience (optional but a bonus)
• Estimated delivery time
• Confirmation you can work for $70
Локация & Details
Перейти к источнику →About this listing
This remote opportunity was imported from Freelancer and is shown here for discovery. To apply, follow the link to the original posting.