DAO Governance Identity & Voting Credentials

ROLE: You are a DAO governance architect who combines expertise in decentralized identity, voting theory, and blockchain governance mechanisms. You have designed governance frameworks for protocol DAOs, investment DAOs, and social DAOs, and you understand the critical tension between privacy (voters should not be pressured or bribed), transparency (governance should be auditable), and Sybil resistance (one person should not pretend to be many).

OBJECTIVE: Design a governance identity system for a DAO that enables fair, Sybil-resistant voting with privacy protections, verifiable delegation, and credential-based participation rights, all while preserving the decentralized ethos.

TASK:
Design a governance identity system for the following DAO:

**DAO Type:** {{DAO_TYPE}} (e.g., protocol governance, investment club, grants committee, social community, service DAO)
**Membership Model:** {{MEMBERSHIP}} (e.g., token-weighted, one-person-one-vote, reputation-weighted, role-based, hybrid)
**Current Size:** {{SIZE}} (e.g., 100 members, 10K token holders, 100K community members)
**Privacy Requirements:** {{PRIVACY}} (e.g., public votes, private votes with public tallies, fully anonymous, pseudonymous with accountability)
**Existing Infrastructure:** {{INFRASTRUCTURE}} (e.g., Snapshot, Tally, custom Governor contract, no governance yet)

Provide the following system design:

1. **Governance Identity Model:**
   - Member identity types: core contributors (verified, high trust), token holders (pseudonymous, stake-weighted), community members (reputation-based), delegates (authorized representatives)
   - Identity verification levels: what proof is required for each member type — token holding proof, contribution history, skill credential, KYC for legal entities
   - DID integration: how each member's governance identity is linked to their DID, enabling portable governance participation across DAOs
   - Pseudonymity framework: how members participate with persistent pseudonyms that build governance reputation without revealing real-world identity
   - Identity credential: a "DAO Membership Credential" verifiable credential with fields for member role, joining date, contribution score, voting power, delegation status

2. **Sybil Resistance for Voting:**
   - Proof of personhood: integration with BrightID, Worldcoin, Gitcoin Passport, or custom verification for one-person-one-vote scenarios
   - Stake-based Sybil resistance: for token-weighted voting, how to handle concentration (quadratic voting, conviction voting, capped voting power)
   - Reputation-based qualification: minimum reputation score to participate in certain votes, earned through verified contributions
   - Multi-factor identity: combining multiple weak signals (GitHub activity, on-chain history, social verification, attestations from existing members) into a strong Sybil resistance score
   - Attack cost analysis: calculate the cost of creating enough fake identities to influence a vote, and ensure it exceeds the value at stake

3. **Voting Credential System:**
   - Vote eligibility credential: issued per proposal or per epoch, containing: eligible voter DID, voting power, eligible proposal IDs, expiration
   - Credential-gated proposals: certain proposals only votable by members with specific credentials (e.g., technical proposals require "Developer" credential, treasury proposals require "Finance Committee" credential)
   - Delegation credentials: verifiable credential proving "Voter A has delegated their voting power to Delegate B for Category X until Date Y"
   - Delegation chains: how to handle re-delegation, delegation depth limits, circular delegation prevention
   - Vote receipt credentials: after voting, the voter receives a credential proving they participated (for retroactive rewards, future eligibility) without revealing how they voted

4. **Privacy-Preserving Voting:**
   - Private ballot implementation: how to cast votes that are hidden until the voting period ends (commit-reveal scheme, homomorphic encryption, or ZKP-based)
   - Verifiable tally: how to prove the vote count is correct without revealing individual votes (homomorphic tallying, mixnet-based shuffling, ZK rollup of votes)
   - Coercion resistance: preventing vote buying and voter intimidation — ability to change vote before reveal, receipt-freeness properties
   - Selective transparency: some votes are public (signaling, temperature checks), some are private (contentious decisions, elections) — configurable per proposal
   - Audit capability: how authorized auditors can verify vote integrity without deanonymizing voters, time-locked audit access for dispute resolution

5. **Delegation & Representation:**
   - Delegate profiles: public identity with credentials (expertise areas, voting history, conflict of interest disclosures)
   - Delegation marketplace: how members discover and evaluate potential delegates, delegate performance metrics
   - Liquid democracy: real-time delegation changes, per-topic delegation, split delegation across multiple delegates
   - Delegate accountability: voting history transparency, deviation from stated principles tracking, recall mechanisms
   - Compensation: how delegates are compensated for their governance participation, credential-based compensation tiers

6. **Cross-DAO Governance Portability:**
   - Governance reputation credentials: portable proof of governance participation, quality, and expertise across DAOs
   - DAO-to-DAO recognition: how participating well in DAO A gives you credibility in DAO B
   - Multi-DAO identity: managing governance identities across multiple DAOs from a single wallet
   - Governance skill credentials: "Participated in 50+ governance votes", "Authored 10 successful proposals", "Served as delegate with 90%+ satisfaction"
   - Interoperability standards: common credential schemas for governance participation that work across governance platforms (Snapshot, Tally, Aragon, custom)