Files
mev-beta/.env.production
Krypto Kajun 850223a953 fix(multicall): resolve critical multicall parsing corruption issues
- Added comprehensive bounds checking to prevent buffer overruns in multicall parsing
- Implemented graduated validation system (Strict/Moderate/Permissive) to reduce false positives
- Added LRU caching system for address validation with 10-minute TTL
- Enhanced ABI decoder with missing Universal Router and Arbitrum-specific DEX signatures
- Fixed duplicate function declarations and import conflicts across multiple files
- Added error recovery mechanisms with multiple fallback strategies
- Updated tests to handle new validation behavior for suspicious addresses
- Fixed parser test expectations for improved validation system
- Applied gofmt formatting fixes to ensure code style compliance
- Fixed mutex copying issues in monitoring package by introducing MetricsSnapshot
- Resolved critical security vulnerabilities in heuristic address extraction
- Progress: Updated TODO audit from 10% to 35% complete

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-17 00:12:55 -05:00

143 lines
5.3 KiB
Plaintext

# Production Environment Configuration for MEV Bot
# WARNING: This file contains sensitive information - NEVER commit to version control!
# =============================================================================
# ARBITRUM NETWORK CONFIGURATION
# =============================================================================
# Primary RPC endpoint - Use your premium provider
ARBITRUM_RPC_ENDPOINT=https://arbitrum-mainnet.core.chainstack.com/53c30e7a941160679fdcc396c894fc57
# WebSocket endpoint for real-time events
ARBITRUM_WS_ENDPOINT=wss://arbitrum-mainnet.core.chainstack.com/53c30e7a941160679fdcc396c894fc57
# Fallback RPC endpoints (comma-separated)
ARBITRUM_FALLBACK_ENDPOINTS=wss://arbitrum-mainnet.core.chainstack.com/53c30e7a941160679fdcc396c894fc57,https://arb1.arbitrum.io/rpc,https://arbitrum.llamarpc.com,https://arbitrum-one.publicnode.com,https://arbitrum-one.public.blastapi.io
# Rate limiting
RPC_REQUESTS_PER_SECOND=100
RPC_MAX_CONCURRENT=10
# =============================================================================
# BOT CONFIGURATION
# =============================================================================
# Performance settings
BOT_MAX_WORKERS=5
BOT_CHANNEL_BUFFER_SIZE=1000
# =============================================================================
# ETHEREUM ACCOUNT CONFIGURATION
# =============================================================================
# CRITICAL: Your trading account private key (64 hex characters without 0x)
# Generate a new key specifically for the bot and fund it appropriately
ETHEREUM_PRIVATE_KEY=your_64_character_private_key_here
# Account address (derived from private key)
ETHEREUM_ACCOUNT_ADDRESS=0x5a588c7ff76a827c1b67adcafe2226918b60a19d8dba25f2d1cfad80399ace9a
# Gas price multiplier for competitive transactions
ETHEREUM_GAS_PRICE_MULTIPLIER=1.5
# =============================================================================
# REAL DEPLOYED CONTRACT ADDRESSES ON ARBITRUM MAINNET
# =============================================================================
# PRODUCTION READY - ArbitrageExecutor contract (VERIFIED)
CONTRACT_ARBITRAGE_EXECUTOR=0xec2a16d5f8ac850d08c4c7f67efd50051e7cfc0b
# PRODUCTION READY - UniswapV3FlashSwapper contract (VERIFIED)
CONTRACT_FLASH_SWAPPER=0x5801ee5c2f6069e0f11cce7c0f27c2ef88e79a95
# Additional deployed contracts
CONTRACT_UNISWAP_V2_FLASH_SWAPPER=0xc0b8c3e9a976ec67d182d7cb0283fb4496692593
CONTRACT_DATA_FETCHER=0x3c2c9c86f081b9dac1f0bf97981cfbe96436b89d
# =============================================================================
# SECURITY CONFIGURATION
# =============================================================================
# Encryption key for secure storage (generate with: openssl rand -base64 32)
MEV_BOT_ENCRYPTION_KEY="tVoxTugRw7lk7q/GC8yXd0wg3vLy8m6GtrvCqj/5q48="
# Keystore and audit locations
MEV_BOT_KEYSTORE_PATH=keystore/production
MEV_BOT_AUDIT_LOG=logs/production_audit.log
MEV_BOT_BACKUP_PATH=backups/production
# =============================================================================
# DATABASE CONFIGURATION
# =============================================================================
# PostgreSQL configuration
POSTGRES_DB=mevbot
POSTGRES_USER=mevbot
POSTGRES_PASSWORD=your_secure_database_password
# =============================================================================
# MONITORING CONFIGURATION
# =============================================================================
# Metrics and logging
METRICS_ENABLED=true
METRICS_PORT=9090
HEALTH_PORT=8080
LOG_LEVEL=info
LOG_FORMAT=json
# Grafana credentials
GRAFANA_USER=admin
GRAFANA_PASSWORD=your_secure_grafana_password
# Prometheus port
PROMETHEUS_PORT=9091
GRAFANA_PORT=3000
# =============================================================================
# PRODUCTION SETTINGS
# =============================================================================
# Environment
GO_ENV=production
DEBUG=false
# Resource limits and timeouts
MAX_MEMORY=1024m
MAX_CPU=2000m
# =============================================================================
# EXAMPLE PREMIUM RPC PROVIDERS
# =============================================================================
# Chainstack (Recommended for production)
# ARBITRUM_RPC_ENDPOINT=wss://arbitrum-mainnet.core.chainstack.com/YOUR_API_KEY
# Alchemy
# ARBITRUM_RPC_ENDPOINT=wss://arb-mainnet.g.alchemy.com/v2/YOUR_API_KEY
# Infura
# ARBITRUM_RPC_ENDPOINT=wss://arbitrum-mainnet.infura.io/ws/v3/YOUR_PROJECT_ID
# QuickNode
# ARBITRUM_RPC_ENDPOINT=wss://YOUR_ENDPOINT.arbitrum-mainnet.quiknode.pro/YOUR_TOKEN/
# =============================================================================
# SECURITY BEST PRACTICES
# =============================================================================
# 1. Use a dedicated server/VPS for production deployment
# 2. Enable firewall and limit access to necessary ports only
# 3. Use premium RPC providers for better reliability and speed
# 4. Monitor all transactions and profits closely
# 5. Start with small position sizes to test everything works
# 6. Set up alerts for unusual activity or losses
# 7. Keep private keys encrypted and backed up securely
# 8. Use separate accounts for testing and production
# 9. Regularly update and patch the system
# 10. Monitor gas prices and adjust strategies accordingly
ARBISCAN_API_KEY=H8PEIY79385F4UKYU7MRV5IAT1BI1WYIVY