Completed clean root directory structure: - Root now contains only: .git, .env, docs/, orig/ - Moved all remaining files and directories to orig/: - Config files (.claude, .dockerignore, .drone.yml, etc.) - All .env variants (except active .env) - Git config (.gitconfig, .github, .gitignore, etc.) - Tool configs (.golangci.yml, .revive.toml, etc.) - Documentation (*.md files, @prompts) - Build files (Dockerfiles, Makefile, go.mod, go.sum) - Docker compose files - All source directories (scripts, tests, tools, etc.) - Runtime directories (logs, monitoring, reports) - Dependency files (node_modules, lib, cache) - Special files (--delete) - Removed empty runtime directories (bin/, data/) V2 structure is now clean: - docs/planning/ - V2 planning documents - orig/ - Complete V1 codebase preserved - .env - Active environment config (not in git) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
26 lines
1.1 KiB
Markdown
26 lines
1.1 KiB
Markdown
You are an expert in Ethereum gas optimization and MEV strategies. I'm building an MEV bot in Go that needs to optimize transaction submission for maximum profitability.
|
|
|
|
I need help with:
|
|
|
|
1. Estimating optimal gas prices for arbitrage transactions
|
|
2. Implementing transaction bundling strategies
|
|
3. Working with flashbots or similar MEV protection services
|
|
4. Optimizing transaction ordering within bundles
|
|
5. Handling frontrunning and backrunning strategies
|
|
6. Managing gas refunds and stipends
|
|
|
|
Please provide production-ready Go code that:
|
|
- Integrates with flashbots or similar MEV protection services
|
|
- Calculates optimal gas prices based on network conditions
|
|
- Implements transaction bundling for atomic execution
|
|
- Handles errors and edge cases properly
|
|
- Follows Go best practices
|
|
- Is optimized for performance
|
|
- Includes comprehensive comments
|
|
|
|
The code should:
|
|
- Connect to flashbots relay or similar service
|
|
- Calculate optimal gas prices based on base fee and priority fees
|
|
- Bundle transactions for atomic execution
|
|
- Handle failed transactions gracefully
|
|
- Implement retry logic with exponential backoff |