Analyze your blockchain application scalability bottlenecks and design solutions using sharding, rollups, state channels, and other scaling techniques.
## ROLE
You are a blockchain scalability engineer who has worked on scaling solutions for applications handling 10M+ daily transactions. You understand both theoretical limits and practical engineering constraints of blockchain scaling.
## OBJECTIVE
Identify scalability bottlenecks in your current or planned blockchain application and design a concrete scaling strategy.
## TASK
**STEP 1: CURRENT PERFORMANCE BASELINE**
| Metric | Current | Required | Gap |
|--------|---------|----------|-----|
| Transactions per second | {current_tps} | {required_tps} | |
| Block time | {block_time} | {target_block_time} | |
| State size | {state_size} | {max_state} | |
| Cost per transaction | {current_cost} | {target_cost} | |
| Time to finality | {current_finality} | {target_finality} | |
**STEP 2: BOTTLENECK IDENTIFICATION**
Analyze where the system hits limits:
- **Execution**: Contract computation limits per block
- **Data Availability**: Cost and speed of publishing transaction data
- **State Growth**: Database size growth rate and access patterns
- **Network**: P2P message propagation delays
- **Consensus**: Validator communication overhead
**STEP 3: SCALING SOLUTIONS COMPARISON**
| Solution | TPS Gain | Cost Reduction | Complexity | Maturity |
|----------|----------|---------------|------------|----------|
| Optimistic Rollups | 10-100x | 10-50x | Medium | Production |
| ZK Rollups | 10-100x | 10-100x | High | Early Production |
| State Channels | 1000x+ | Near-zero | Medium | Production |
| Sidechains | 10-50x | 10-50x | Low | Production |
| Sharding | 10-100x | 10-100x | Very High | Development |
| Validium | 10-100x | 100x+ | High | Early Production |
| Data Compression | 2-5x | 2-5x | Low | Production |
**STEP 4: IMPLEMENTATION ROADMAP**
For the recommended solution:
- Phase 1: Quick wins (compression, batching, caching)
- Phase 2: Medium-term scaling (rollup deployment or sidechain)
- Phase 3: Long-term architecture (sharding, cross-shard communication)
- Timeline and resource estimates per phase
- Risk factors and rollback plans
## INPUT
**Application Type**: {app_type}
**Current Chain**: {current_chain}
**Peak Load (TPS)**: {peak_tps}
**Budget for Scaling**: {scaling_budget}
**Team Size**: {team_size}Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
{current_tps}{required_tps}{block_time}{target_block_time}{state_size}{max_state}{current_cost}{target_cost}{current_finality}{target_finality}{app_type}{current_chain}{peak_tps}{scaling_budget}{team_size}