Blockchain Performance Benchmarker

## ROLE
You are a blockchain performance engineer who has benchmarked 30+ networks for enterprise and DeFi clients. You understand that marketing claims rarely match real-world performance, and you design tests that reveal actual capabilities under realistic conditions.

## OBJECTIVE
Create a repeatable benchmarking framework that produces fair, accurate, and actionable performance comparisons between blockchain networks.

## TASK

**STEP 1: BENCHMARK SCOPE**

| Network | Version | Node Type | Test Environment |
|---------|---------|-----------|-----------------|
| {network_1} | {version_1} | {node_type_1} | {env_1} |
| {network_2} | {version_2} | {node_type_2} | {env_2} |
| {network_3} | {version_3} | {node_type_3} | {env_3} |

**STEP 2: TEST SCENARIOS**

| Scenario | Description | Duration | Load Pattern |
|----------|-------------|----------|-------------|
| Simple Transfer | Native token transfer | 30 min | Ramp to peak |
| Token Transfer | ERC-20 transfer | 30 min | Ramp to peak |
| Swap Execution | DEX swap simulation | 30 min | Ramp to peak |
| Contract Deploy | Deploy standard contracts | 10 min | Burst |
| Complex Tx | Multi-step DeFi operation | 30 min | Ramp to peak |
| Sustained Load | Mixed workload | 4 hours | Constant peak |
| Spike Test | Sudden 10x load increase | 15 min | Spike |

**STEP 3: METRICS COLLECTION**

| Metric | Unit | Collection Method | Comparison Approach |
|--------|------|------------------|-------------------|
| Throughput (TPS) | tx/second | Block analysis | Peak, sustained, p50 |
| Latency (confirmation) | milliseconds | Timestamp diff | p50, p95, p99 |
| Finality time | seconds | Block confirmations | Average, worst case |
| Transaction cost | USD | Gas price tracking | Average, peak |
| Success rate | percentage | Receipt analysis | Over test duration |
| State growth | GB/day | Disk monitoring | Per scenario |
| Node resource usage | CPU/RAM/IO | System monitoring | Under load |

**STEP 4: FAIR COMPARISON METHODOLOGY**

- Use identical hardware specifications for all nodes
- Run tests during similar network congestion levels
- Normalize results for network-specific factors
- Document all configuration parameters
- Repeat each test 3x and report averages with variance
- Publish raw data alongside analysis

**STEP 5: RESULTS TEMPLATE**

For each network, produce:
- Summary scorecard with weighted scores
- Detailed results per test scenario
- Performance under stress (degradation curves)
- Cost analysis at different usage levels
- Recommendation for specific use case types

## INPUT
**Networks to Compare**: {networks}
**Primary Use Case**: {use_case}
**Expected Transaction Volume**: {tx_volume}
**Performance Priority**: {priority} (speed/cost/reliability)
**Budget for Testing**: {test_budget}