Contact person: Ethereum Presale Claim Bot Development

Phone:Show

Email:Show

Location: London, United Kingdom

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Objectives
1. Deliver a secure Ethereum presale claim bot that continuously monitors claim status and executes the moment claim functions open
2. Prevent front running and sweeper bots by bundling claim and transfer transactions together in the same private Flashbots submission
3. Support both LilPepe and BTC Hyper within a single configuration
4. Ensure the bot runs continuously until both claims are completed with reliability and clear logs
Scope of Work
1. The bot will be configurable for both LilPepe and BTC Hyper
2. When both tokens are claimable it will send a single private Flashbots bundle that chains claim LilPepe then transfer full LilPepe balance to safe wallet then claim BTC Hyper then transfer full BTC Hyper balance to safe wallet
3. If only one token is open the bot will execute that claim and transfer while continuing to monitor the other
4. Detection will be by contract events state flags or callStatic probes with safe polling intervals
5. Transactions will only be sent through private Flashbots relays with automatic resubmission each block until successful inclusion
6. Dry run simulation will be performed before every submission and aborted if simulation fails
7. Gas management will support EIP 1559 with runtime configurable maxFeePerGas and maxPriorityFeePerGas including multipliers and caps
8. The process must run continuously under PM2 or systemd with failover to secondary RPC and relay if primary fails
9. Logs will be written to console and rotating files with transaction hashes bundle hashes and inclusion blocks
10. Alerts may be sent by Telegram or email when claims are detected bundles sent and when transactions succeed or fail
11. Private key remains on client machine at all times
Deliverables
1. Private GitHub repository with full Node.js and [login to view URL] codebase
2. Configuration files including [login to view URL] and .env template for secrets
3. README with setup instructions configuration guide and run commands
4. PM2 ecosystem file or systemd unit file for continuous running
5. Sepolia proof with verifiable private bundle transaction hash and logs
6. Mainnet dry run simulation logs for both LilPepe and BTC Hyper
7. Final handover of all code and documentation
Acceptance Criteria
1. Bot runs for forty eight hours on Sepolia without crashing
2. Bot detects claimable state and submits private bundle that confirms within one or two blocks
3. Dual token orchestration works both open leads to chained bundle with correct order one open executes that path while monitoring the other
4. Tokens arrive in safe wallet either through direct claimTo or through transfer within the same bundle
5. Logs clearly show detection submission transaction hashes and results
6. Failover tested so if primary RPC or relay is unavailable the bot switches to backup and continues
7. Client can configure gas and relays without editing source code
Milestones and Payment Terms
Total budget 500 USD fixed
Payment split 20 percent 30 percent 50 percent
Milestone 1 20 percent Sepolia proof by Day 2
• Repo skeleton delivered with configuration system
• Detection engine for LilPepe and BTC Hyper in place
• Flashbots submission wired and functioning
• Verifiable Sepolia private bundle submitted with transaction hash provided
Milestone 2 30 percent Dual token orchestration and monitoring by Day 4
• Full LilPepe and BTC Hyper orchestration implemented
• Claim and transfer bundled together to safe wallet in same private submission
• Skip logic in place so if one token is not open the other still executes
• Bot runs continuously with monitoring and demonstrates forty eight hours uptime on Sepolia
• Structured logs produced with transaction hashes and inclusion blocks
Milestone 3 50 percent Mainnet readiness and final handover by Day 6
• Mainnet dry run simulations for both tokens showing claim and transfer chain
• Full repository delivered with README configuration templates and instructions
• Bot proven to run continuously from start until both claims complete
• Final confirmation by client that all essentials are working
• Ownership of source code transferred to client
Timeline and Payment Condition
• Project timeline is six calendar days total from project start
• If the project runs over this timeline without client approval no further payment will be released until final handover is complete
• If the developer delivers completed and functional code after the deadline payment will only be made on final acceptance and the final milestone will be reduced by twenty percent
• Support will continue until the claim has been successfully executed on mainnet in case of programme malfunction
Also, what is actually involved technically:
Config system trivial, a JSON loader with dotenv 0.5 day
Detection engine listen for events, poll state flags, callStatic probe 1 day
Flashbots integration boilerplate, plenty of open code examples 1 day
Bundle builder chain claim and transfer calls, manage nonces 1 day
Skip logic simple conditionals 0.5 day
Continuous runner wrap in PM2 or systemd, restart on crash 0.5 day
Logging structured console and rotating file logs 0.5 day
Testing Sepolia proof with verifiable transaction, then dry run on mainnet 1 to 2 days
Docs and repo handover README and templates 0.5 day
This is about five to six days of actual work for one person. If you are experienced in Flashbots and [login to view URL], it could realistically be done in three to five focused days." (client-provided description)