State Channel Network Design

## ROLE
You are a state channel protocol designer who has built payment channel networks and generalized state channel frameworks. You understand the Lightning Network, Raiden, and Nitro Protocol architectures deeply.

## OBJECTIVE
Design a state channel network for [PROJECT NAME] to enable [USE CASE: payments/gaming/trading] with [TARGET LATENCY] latency and [TARGET THROUGHPUT] throughput between participants.

## TASK

### Channel Architecture
- Two-party channels: direct bilateral state management
- Multi-party channels: N participants sharing a channel (virtual channels)
- Hub-and-spoke topology: central routing nodes for network connectivity
- Channel factories: batch-open multiple channels from a single on-chain transaction
- Virtual channels: route payments through intermediaries without on-chain setup

### State Transition Protocol
- State format: define the state object structure (balances, game state, positions)
- Update mechanism: signed state updates exchanged off-chain
- Turn-based vs concurrent: who can propose state updates and when
- Conflict resolution: what happens when parties disagree on state
- State hashing: efficient hashing for compact state commitments

### Dispute Resolution
- Challenge period: window for submitting the latest state on-chain
- Adjudicator contract: on-chain logic for resolving disputes
- Forceclose flow: unilateral channel closure with challenge period
- Happy path: cooperative close with final signed state
- Appeal mechanism: respond to outdated state submissions with newer state
- Punishment: slash bonds for submitting known-outdated states

### Payment Routing (for payment channels)
- Pathfinding: find route through network from sender to receiver
- HTLC (Hash Time-Lock Contracts): atomic multi-hop payments
- Routing fees: incentive structure for intermediary nodes
- Channel capacity management: rebalancing, liquidity allocation
- Multi-path payments: split large payments across multiple routes

### Generalized State Channels
- Application framework: plug-in state transition functions
- Composability: chain multiple applications within a channel
- Conditional execution: state updates contingent on external data
- Timeout handling: what happens if one party stops responding
- State channel apps: gaming, auctions, trading, streaming payments

### Network Operations
- Node software: requirements, configuration, monitoring
- Channel management: automated opening, closing, rebalancing
- Watchtower services: monitoring for fraud while parties are offline
- Backup and recovery: channel state backup for data loss protection
- Network bootstrap: initial liquidity provisioning, node incentives

## OUTPUT FORMAT
State channel network design with protocol specification, dispute resolution flows, routing algorithms, and operational guide.

## CONSTRAINTS
- Users must always be able to exit to L1 within bounded time
- System must handle participant going offline gracefully
- On-chain gas costs must be minimal for normal (cooperative) operations
- Privacy: minimize on-chain data leakage about channel activity
- Include analysis of griefing attacks and mitigation strategies