Governance Stack - irl.coop

Core Requirement: "Action as Vote"

The governance layer isn't just for allocating funds; it gates actions (sending emails, publishing files).

• Bridge: Lit Protocol (PKP) acts as the "hand" that executes the action once the "brain" (Governance Contract) approves it.

Option A: The "Reliable Standard" (DAO DAO / Osmosis)

Leveraging existing, battle-tested tooling in the Cosmos ecosystem.

• Engine: DAO DAO (CosmWasm).
• Chain: Osmosis (or Neutron/Juno).
• Pros:
  • Zero dev time for contracts (UI/Contracts exist).
  • Deep integration with verifyable on-chain assets.
  • Users understand it.
• Cons:
  • Public Voting: Everyone sees who voted for what (unless using specialized modules). In small groups ("Swim Buddies"), public voting causes social friction.

Option B: The "Double Privacy" Stack (Secret + Namada)

Building for social safety and treasury privacy.

1. The "Conscience" (Secret Network)

Role: Governance & Voting.

• Why: Encrypted inputs. Bob's vote is encrypted. Only the final tally is revealed (or just "Pass/Fail").
• Social Safety: Prevents social retaliation in friend groups.
• Mechanism: Custom SNIP-721 (Membership) + Voting Contract.

2. The "Vault" (Namada)

Role: Shielded Treasury.

• Why: Multi-Asset Shielded Pool (MASP).
• Privacy:
  • The group's total balance is hidden.
  • Incoming "Support Tokens" and outgoing payments are shielded.
  • Prevents the group from becoming a public "honeypot" target.

The Integration Flow (Temporal + Lit)

Regardless of chain, the flow looks like this:

1. Trigger: User clicks "Send Email" (or "Pay Kayaker") in dashboard.
2. Hold: System creates a Draft and a Governance Proposal on Secret Network.
3. Vote: Members sign txs (with Google/Wallet auth) to vote Yes/No on Secret.
4. Resolve:
   • Temporal watches the Secret contract.
   • When Proposal = PASSED:
     • Action (Email/Web2): Lit PKP signs the API release.
     • Action (Payment - The "Soft TEE" Approach):
       • Challenge: Generating ZK proofs requires the raw key.
       • Solution: Use the group's private Zo Container as an ephemeral "Soft TEE".
       • Process:
         1. Lit Nodes release key shards to the Zo Container (authorized by the "Passed" vote).
         2. Zo Container reconstructs the key in RAM.
         3. Zo runs namada client transfer (generating the ZK proof).
         4. Transaction broadcast.
         5. Critical: Zo wipes the key from RAM immediately.
       • Trust: Relies on the security of the irl.coop infrastructure (Admin access = Key access during the 10s window). Acceptable for small/medium groups.

Recommendation

For irl.coop (real-world groups): Privacy is critical. Standard DAOs fail for social groups because nobody wants to be the "bad guy" publicly. Secret Network (or a private voting module) seems closer to the "coop" ethos.