A powerful Ethereum transaction generator for testnets π
Spamoor is a robust transaction spamming tool designed for stress testing, network validation, and continuous transaction testing on Ethereum testnets. With 13+ different transaction scenarios and a powerful web-based daemon mode, it's the ultimate tool for Ethereum network testing.
# π³ Using Docker
docker run ethpandaops/spamoor
# π§ Building from source
git clone https://github.com/ethpandaops/spamoor.git
cd spamoor
make
./bin/spamoor
# Run a single scenario
spamoor <scenario> [flags]
# Run multiple scenarios from YAML configuration
spamoor run <yaml-file> [flags]
Parameter | Description |
---|---|
--privkey |
Private key for the root wallet (funds child wallets) |
--rpchost |
RPC endpoint(s) to send transactions to |
# Basic usage
spamoor eoatx --privkey="0x..." --rpchost="http://localhost:8545"
# Multiple RPC endpoints
spamoor eoatx --privkey="0x..." \
--rpchost="http://node1:8545" \
--rpchost="http://node2:8545"
# With authentication
spamoor eoatx --privkey="0x..." \
--rpchost="headers(Authorization:Bearer token)http://node:8545"
π‘ See the App User Guide for advanced RPC configuration options
Spamoor provides a comprehensive suite of transaction scenarios for different testing needs:
Scenario | Description |
---|---|
eoatx |
EOA Transactions - Send standard ETH transfers with configurable amounts |
erctx |
ERC20 Transactions - Deploy ERC20 tokens and perform transfers |
calltx |
Contract Calls - Deploy contracts and repeatedly call functions |
deploytx |
Contract Deployments - Deploy contracts with custom bytecode |
deploy-destruct |
Self-Destruct Deployments - Deploy self-destructing contracts |
setcodetx |
Set Code Transactions - EIP-7702 setcode transactions |
uniswap-swaps |
Uniswap Swaps - Deploy and test Uniswap V2 token swaps |
blobs |
Blob Transactions - Send blob transactions with random data |
blob-replacements |
Blob Replacements - Test blob transaction replacement |
blob-conflicting |
Conflicting Blobs - Test conflicting blob/normal transactions |
blob-combined |
Combined Blob Testing - Randomized blob scenario combinations |
gasburnertx |
Gas Burner - Burn specific amounts of gas |
storagespam |
Storage Spam - Stress test EVM storage |
geastx |
Geas Transactions - Execute custom geas bytecode |
xentoken |
XEN Sybil Attack - Simulate XEN token sybil attacks |
taskrunner |
Task Runner - Execute configurable task sequences with init and execution phases |
The spamoor run
command allows you to execute multiple scenarios concurrently from a YAML configuration file, without needing the full daemon infrastructure.
spamoor run <yaml-file> [flags]
Flag | Short | Description |
---|---|---|
--spammers |
-s |
Indexes of spammers to run (e.g., -s 0,2 ). If not specified, runs all |
--privkey |
-p |
Private key for the root wallet |
--rpchost |
-h |
RPC endpoints (multiple allowed) |
--rpchost-file |
- | File containing RPC endpoints |
--verbose |
-v |
Enable verbose logging |
--trace |
- | Enable trace logging |
# example-run-config.yaml
- scenario: eoatx
name: "High Volume ETH Transfers"
description: "Basic ETH transfers with 400 tx/slot throughput"
config:
seed: eoatx-demo
refill_amount: 1000000000000000000 # 1 ETH in wei
refill_balance: 500000000000000000 # 0.5 ETH in wei
refill_interval: 600 # 10 minutes
throughput: 400
max_pending: 800
max_wallets: 200
base_fee: 20 # gwei
tip_fee: 2 # gwei
amount: 100 # 100 wei per transfer
random_amount: true
random_target: true
- scenario: erctx
name: "ERC20 Token Spammer"
description: "Deploy and transfer ERC20 tokens"
config:
seed: erctx-demo
refill_amount: 2000000000000000000 # 2 ETH
refill_balance: 1000000000000000000 # 1 ETH
throughput: 100
max_pending: 200
max_wallets: 100
amount: 50
random_amount: true
# Include other configuration files
- include: ./high-load-configs.yaml
# Run all spammers from configuration
spamoor run config.yaml -h http://localhost:8545 -p 0x...
# Run only specific spammers (0-based indexes)
spamoor run config.yaml -h http://localhost:8545 -p 0x... -s 0,2
# With multiple RPC endpoints
spamoor run config.yaml -p 0x... \
-h http://node1:8545 \
-h http://node2:8545
Run Spamoor as a daemon with a powerful web interface for managing multiple concurrent spammers.
spamoor-daemon [flags]
Flag | Short | Description | Default |
---|---|---|---|
--db |
-d |
Database file location | spamoor.db |
--rpchost |
-h |
RPC endpoints (multiple allowed) | - |
--rpchost-file |
- | File containing RPC endpoints | - |
--privkey |
-p |
Root wallet private key | - |
--port |
-P |
Web UI port | 8080 |
--startup-spammer |
- | YAML file or URL with startup spammers | - |
--fulu-activation |
- | Unix timestamp of Fulu activation | 0 |
--without-batcher |
- | Disable transaction batching | false |
--disable-tx-metrics |
- | Disable transaction metrics collection | false |
--verbose |
-v |
Enable verbose logging | false |
--debug |
- | Enable debug mode | false |
--trace |
- | Enable trace logging | false |
Access the web UI at http://localhost:8080
for:
- View all spammers at a glance with their status, scenario type, and actions
- Mass actions for bulk operations on multiple spammers
- Quick access to start, stop, edit, and delete spammers
- Expandable live logs for each spammer
- Monitor wallet balances and transaction counts
- Track child wallets spawned from the root wallet
- Real-time balance updates
- View and manage RPC client connections
- Group clients for load balancing
- Enable/disable clients dynamically
- Monitor client status and block height
- Visual monitoring of transaction throughput
- Success/failure rates per spammer
- Network performance metrics
The daemon exposes a comprehensive REST API for automation:
-
π‘ Client Management
GET /api/clients
- List all RPC clientsPUT /api/client/{index}/groups
- Update client groupsPUT /api/client/{index}/name
- Set custom display name
-
π€ Spammer Control
GET /api/spammers
- List all spammersPOST /api/spammer
- Create new spammerPUT /api/spammer/{id}/start
- Start spammerPUT /api/spammer/{id}/pause
- Pause spammer
-
πΎ Import/Export
GET /api/export
- Export configurationsPOST /api/import
- Import configurations
π Full API documentation available at /docs
when daemon is running
- Select from 13+ pre-configured scenarios
- Customize configuration with YAML editor
- Real-time YAML validation
- Access to pre-built configuration library
# Export all spammers to YAML
curl http://localhost:8080/api/export > my-spammers.yaml
Import dialog showing YAML validation and configuration options
Pre-built configuration library for common test scenarios
# Import on startup
spamoor-daemon --startup-spammer="spammer-configs.yaml"
# Import via API
curl -X POST http://localhost:8080/api/import \
-H "Content-Type: application/yaml" \
--data-binary @spammer-configs.yaml
# Direct spammer definition
- scenario: "eoatx"
name: "Basic ETH Transfers"
config:
wallet_count: 10
transaction_count: 1000
# Include other files
- include: "common-spammers.yaml"
- include: "https://example.com/stress-tests.yaml"
Access metrics at /metrics
for monitoring with Prometheus/Grafana:
- π’ Transaction Metrics: Success rates, gas usage, confirmation times
- π Performance Metrics: TPS, latency, queue sizes
- π― Scenario Metrics: Custom metrics per scenario type
Comprehensive documentation is available for different user types:
π App User Guide
Complete guide for CLI usage, daemon mode, configuration, and troubleshooting. Covers:
- Installation and setup options
- Detailed CLI usage with examples
- Web interface walkthrough
- Configuration management
- Troubleshooting common issues
π API Consumer Guide
REST API documentation with bash/curl examples for all endpoints. Includes:
- Complete API reference with examples
- Spammer management endpoints
- Client configuration and monitoring
- Real-time data streaming
- Import/export functionality
π οΈ Scenario Developer Guide
Comprehensive guide for implementing custom transaction scenarios. Covers:
- Scenario architecture and lifecycle
- Critical development rules and best practices
- Wallet management and transaction building
- Contract interaction patterns
- Testing and debugging scenarios
- π― 13+ Transaction Scenarios: From basic EOA transfers to complex DeFi interactions
- π₯οΈ Web-Based Daemon Mode: Manage multiple spammers through an intuitive UI
- π REST API: Full programmatic control for automation
- π Prometheus Metrics: Built-in monitoring and observability
- π³ Docker Support: Easy deployment with official images
- π§ Highly Configurable: YAML configs, CLI flags, and runtime adjustments
- π High Performance: Optimized for maximum transaction throughput
- π‘οΈ Production Ready: Battle-tested on Ethereum testnets
- Go 1.24+
- CGO enabled (required for SQLite and cryptographic operations)
- Build tags:
with_blob_v1,ckzg
for blob transaction support
# Clone the repository
git clone https://github.com/ethpandaops/spamoor.git
cd spamoor
# Run tests
make test
# Build binaries
make build
# Run development environment with local testnet
make devnet-run
spamoor/
βββ .cursor/rules/ # Development standards and guidelines
βββ cmd/ # CLI applications (spamoor & spamoor-daemon)
βββ daemon/ # Daemon implementation
βββ docs/ # User documentation
βββ scenario/ # Core scenario framework
βββ scenarios/ # Transaction scenario implementations
βββ scripts/ # Build and utility scripts
βββ spammer-configs/ # Pre-built spammer configuration library
βββ spamoor/ # Core spamoor logic
βββ txbuilder/ # Transaction building utilities
βββ utils/ # Shared utilities
βββ webui/ # Web interface frontend
We welcome contributions! Here's how you can help:
- π Report Issues: Found a bug? Open an issue
- π‘ Suggest Features: Have an idea? Share it in the discussions
- π Improve Documentation: Help us make the docs better
- π§βπ» Submit Code: Check our development guidelines
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature
) - Commit your changes (
git commit -m 'Add amazing feature'
) - Push to the branch (
git push origin feature/amazing-feature
) - Open a Pull Request
- Follow the code standards
- Add tests for new features
- Update documentation as needed
- Ensure all tests pass
This project is licensed under the MIT License - see the LICENSE file for details.
Built with β€οΈ by the Ethpandaops team.
Special thanks to all contributors who have helped make Spamoor better!