Multi-Chain MEV Transaction Execution Framework Asynchronous engine for scanning mempools, analyzing on-chain & market data, and dispatching profitable MEV trades across any EVM chain – complete with safety-nets, RL-powered strategy selection, and an interactive terminal experience.
The easiest way to enter ON1Builder Framework is through our interactive ignition system:
- Clone and enter the ignition system
git clone https://github.com/john0n1/ON1Builder.git
cd ON1Builder
python ignition.py- Follow the prompts
- Select "Install and set up dependencies"
- If you prefer the traditional approach:
./setup_dev.sh- Run directly:
on1builder run --env .env --dry-run| Feature | Description |
|---|---|
| Auto-Setup | One-click dependency installation, virtual environment setup, and configuration |
| Multi-Chain | MultiChainCore spawns workers per chain with shared safety & metrics |
| MEV Strategies | Front-run, back-run, sandwich (+ flash-loan variants) with RL-powered auto-selection |
| Robust Safety | SafetyNet with balance, gas, slippage checks + circuit-breaker alerts |
| Real-time Monitoring | Mempool & market monitors feeding live data to RL agents |
| Nonce-safe | Thread-safe nonce management under high concurrency |
| Dynamic ABIs | Hot-loadable JSON ABIs with automatic validation |
| Full Persistence | Async SQLAlchemy recording every transaction for analytics |
The ignition system automatically:
- Checks for required packages
- Installs missing dependencies
- Sets up Python virtual environments
- Configures development environment
- Provides fallback systems for missing packages
Navigate through terminal menus:
- Install and set up dependencies - One-click setup
- Launch ON1Builder - Start the MEV engine
- Configure Settings - Interactive configuration
- View System Status - Health checks and diagnostics
- Manage Configuration Files - Edit and create configs
- View Logs - Real-time log monitoring
- Help & Documentation - Built-in help system
Configuration is handled through:
- YAML files in
configs/chains/ - Environment variables in
.env(for secrets) - Interactive setup via ignition.py
on1builder config init > my_chain.yaml
# Validate configurationon1builder config validate my_chain.yaml- Or use the interactive system
python ignition.py
# → Select "Manage Configuration Files"- Python ≥ 3.12
- Poetry (optional, for advanced dependency management)
- Git
poetry install --with dev
pre-commit install
pytest -q- Pre-configured settings in
.vscode/ - Automatic Python environment detection
- Integrated debugging and testing
- Start full stack (Grafana + Prometheus + Node)
docker compose up -d- Access Grafana dashboard → http://localhost:3000
- Production keys: Always use
.envfiles; never commit secrets - Bug reports: Create GitHub issues or email
john@on1.no - Security issues: Use GPG key in SECURITY.md
We welcome contributions!
- Fork the repository
- Use 'setup_dev.sh' to set up your development environment
- Create a feature branch
- Make your changes
- Run tests via ignition system
- Submit a pull request
MIT © 2025 John0n1/ON1Builder
See LICENSE for full terms