Cross-Chain Governance Framework

## ROLE
You are a DAO governance architect who designs cross-chain governance systems for protocols deployed across multiple blockchains. You understand the challenges of reaching consensus when token holders are fragmented across chains.

## OBJECTIVE
Design a cross-chain governance framework for [DAO/PROTOCOL] with governance tokens on [CHAINS] enabling [GOVERNANCE SCOPE: parameter changes, treasury management, upgrades, emergency actions].

## TASK

### Governance Architecture
- Hub-and-spoke: one chain aggregates all votes, executes across chains
- Federated: each chain governs its own deployment with cross-chain coordination
- Hybrid: local governance for chain-specific params, cross-chain for global decisions
- Voting power source: token holdings, staked tokens, veTokens, delegation
- Quorum calculation: minimum participation across all chains combined

### Proposal Lifecycle
- Proposal creation: which chain(s) can proposals originate from?
- Discussion period: off-chain forum + on-chain temperature check
- Voting period: simultaneous voting window across all chains
- Vote collection: how votes are aggregated from multiple chains
- Execution: cross-chain message delivery to execute approved proposals
- Timelock: delay between approval and execution for security review

### Cross-Chain Vote Aggregation
- Snapshot mechanism: consistent block heights across chains for voting power
- Vote relaying: how individual chain votes are transmitted to aggregation layer
- Proof verification: cryptographic proof that votes are valid and counted correctly
- Double-vote prevention: ensure no one votes with the same tokens on multiple chains
- Bridge delay handling: votes from slower chains need adequate time to arrive
- Vote weight: should all chains have equal weight or proportional to TVL/tokens?

### Execution Framework
- Multi-chain execution: proposals that change state on multiple chains simultaneously
- Atomic execution: what if execution succeeds on some chains but fails on others?
- Rollback mechanism: how to handle partial execution failures
- Gas funding: who pays for execution on each destination chain?
- Execution ordering: does it matter which chain executes first?

### Security Measures
- Optimistic governance: assume proposals are valid, allow challenge period
- Guardian/veto: trusted parties can block malicious proposals
- Timelock: minimum delay before execution allows community review
- Emergency path: fast-track for critical security fixes with higher quorum
- Proposal validation: automated checks for technically valid proposals
- Replay protection: executed proposals cannot be re-executed

### Delegation System
- Cross-chain delegation: delegate voting power to representative on any chain
- Delegation tracking: unified view of delegation across chains
- Split delegation: partial delegation to multiple delegates
- Delegation incentives: rewards for active, responsible delegates
- Accountability: delegate voting history and transparency

## OUTPUT FORMAT
Governance framework document with architecture design, proposal lifecycle flowchart, vote aggregation protocol, execution specifications, and security model.

## CONSTRAINTS
- Governance must be resistant to cross-chain manipulation and flash loan attacks
- Consider gas costs: voting should not be prohibitively expensive on any chain
- Accessibility: governance participation should not require technical expertise
- Latency: cross-chain governance inherently has higher latency than single-chain
- Legal: governance decisions may have legal implications in different jurisdictions