c54c569f30
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>
25 lines
998 B
Markdown
25 lines
998 B
Markdown
You are an expert in Ethereum smart contract interaction and Web3 development. I'm building an MEV bot in Go that needs to interact with Uniswap V3 smart contracts.
|
|
|
|
I need help with:
|
|
|
|
1. Interacting with Uniswap V3 factory contract to get pool addresses
|
|
2. Querying pool contracts for liquidity and price information
|
|
3. Simulating swap transactions to estimate outputs
|
|
4. Building and signing transactions for submission
|
|
5. Working with contract ABIs and function selectors
|
|
6. Handling contract events and logs
|
|
|
|
Please provide production-ready Go code that:
|
|
- Uses the go-ethereum library for contract interaction
|
|
- Implements efficient contract querying
|
|
- Handles errors gracefully
|
|
- Follows Go best practices
|
|
- Is optimized for performance
|
|
- Includes comprehensive comments
|
|
|
|
The code should:
|
|
- Connect to Ethereum contracts using ABI bindings
|
|
- Query pool state efficiently
|
|
- Simulate transactions before execution
|
|
- Handle contract events and logs
|
|
- Work with both RPC and WebSocket connections |