Add additional project structure, config, Docker support, and more prompt files
This commit is contained in:
24
@prompts/database.md
Normal file
24
@prompts/database.md
Normal file
@@ -0,0 +1,24 @@
|
||||
You are an expert in Go database integration and data persistence. I'm building an MEV bot in Go that needs to store and query historical data for analysis and strategy optimization.
|
||||
|
||||
I need help with:
|
||||
|
||||
1. Setting up a database for storing transaction data
|
||||
2. Designing efficient database schemas for MEV data
|
||||
3. Implementing efficient data access patterns
|
||||
4. Handling database migrations
|
||||
5. Optimizing queries for performance
|
||||
6. Implementing data retention policies
|
||||
|
||||
Please provide production-ready Go code that:
|
||||
- Uses an embedded database like SQLite or BadgerDB
|
||||
- Implements efficient data access patterns
|
||||
- Handles database connections properly
|
||||
- Follows Go best practices
|
||||
- Includes comprehensive comments
|
||||
|
||||
The code should:
|
||||
- Store transaction and swap data efficiently
|
||||
- Support fast querying of historical data
|
||||
- Implement proper indexing for performance
|
||||
- Handle concurrent access safely
|
||||
- Include backup and recovery mechanisms
|
||||
26
@prompts/performance-optimization.md
Normal file
26
@prompts/performance-optimization.md
Normal file
@@ -0,0 +1,26 @@
|
||||
You are an expert in Go performance optimization and high-frequency trading systems. I'm building an MEV bot in Go that needs to process thousands of transactions per second with minimal latency.
|
||||
|
||||
I need help with:
|
||||
|
||||
1. Optimizing data structures for high-frequency access
|
||||
2. Minimizing memory allocations and garbage collection
|
||||
3. Implementing efficient caching strategies
|
||||
4. Optimizing network I/O for RPC calls
|
||||
5. Parallel processing of transactions
|
||||
6. Profiling and benchmarking techniques
|
||||
|
||||
Please provide production-ready Go code that:
|
||||
- Implements lock-free or low-lock data structures where appropriate
|
||||
- Minimizes memory allocations through object pooling
|
||||
- Uses efficient algorithms for data processing
|
||||
- Implements caching for frequently accessed data
|
||||
- Handles concurrency properly
|
||||
- Follows Go best practices
|
||||
- Includes comprehensive comments
|
||||
|
||||
The code should:
|
||||
- Process transactions with minimal latency
|
||||
- Scale efficiently across multiple CPU cores
|
||||
- Handle backpressure gracefully
|
||||
- Provide metrics for performance monitoring
|
||||
- Include benchmarks for critical functions
|
||||
24
@prompts/security.md
Normal file
24
@prompts/security.md
Normal file
@@ -0,0 +1,24 @@
|
||||
You are an expert in blockchain security and MEV bot development. I'm building an MEV bot in Go that needs to be secure against various attack vectors.
|
||||
|
||||
I need help with:
|
||||
|
||||
1. Protecting private keys and signing credentials
|
||||
2. Preventing frontrunning by other bots
|
||||
3. Securing RPC endpoint connections
|
||||
4. Handling MEV submission securely
|
||||
5. Preventing sandwich attacks
|
||||
6. Implementing secure configuration management
|
||||
|
||||
Please provide production-ready Go code that:
|
||||
- Implements secure key management practices
|
||||
- Protects against common MEV bot vulnerabilities
|
||||
- Handles sensitive data securely
|
||||
- Follows security best practices
|
||||
- Includes comprehensive comments
|
||||
|
||||
The code should:
|
||||
- Store private keys securely using hardware wallets or secure enclaves
|
||||
- Use encrypted connections for RPC endpoints
|
||||
- Implement proper access controls
|
||||
- Handle errors without exposing sensitive information
|
||||
- Include security checks and validations
|
||||
25
@prompts/smart-contract-interaction.md
Normal file
25
@prompts/smart-contract-interaction.md
Normal file
@@ -0,0 +1,25 @@
|
||||
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
|
||||
26
@prompts/testing-simulation.md
Normal file
26
@prompts/testing-simulation.md
Normal file
@@ -0,0 +1,26 @@
|
||||
You are an expert in Go testing and blockchain simulation. I'm building an MEV bot in Go that needs comprehensive testing to ensure reliability and profitability.
|
||||
|
||||
I need help with:
|
||||
|
||||
1. Creating realistic test scenarios for MEV detection
|
||||
2. Simulating Arbitrum network conditions
|
||||
3. Testing pricing calculations with real-world data
|
||||
4. Implementing integration tests with mock contracts
|
||||
5. Creating benchmarks for performance testing
|
||||
6. Implementing property-based testing for mathematical functions
|
||||
|
||||
Please provide production-ready Go test code that:
|
||||
- Uses the standard testing package and testify for assertions
|
||||
- Implements realistic test scenarios
|
||||
- Creates mock data for testing
|
||||
- Includes benchmarks for performance-critical functions
|
||||
- Follows Go testing best practices
|
||||
- Provides comprehensive coverage
|
||||
|
||||
The test code should:
|
||||
- Test edge cases and boundary conditions
|
||||
- Validate mathematical accuracy of pricing functions
|
||||
- Simulate network errors and timeouts
|
||||
- Test various swap scenarios and arbitrage opportunities
|
||||
- Benchmark performance of critical algorithms
|
||||
- Provide meaningful test output
|
||||
Reference in New Issue
Block a user