zama-blind-voting

Deploy Zama fhEVM contracts for encrypted DAO voting with TEE finalization.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/leomanza/delibera.xyz --skill zama-blind-voting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zama-blind-voting
Source: https://github.com/leomanza/delibera.xyz/tree/main/.claude/skills/zama-blind-voting
Command: npx skills add https://github.com/leomanza/delibera.xyz --skill zama-blind-voting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enables confidential DAO governance by preventing plaintext vote disclosure and vote manipulation on-chain.

Core Features & Use Cases

  • Deploy fhEVM blind voting contracts to Zama (devnet or local mock) so proposals can be registered and votes can be cast securely.
  • Cast encrypted votes with FHE using euint32 (approved/rejected) and homomorphically accumulate tallies with FHE.add() without exposing individual choices.
  • Finalize and publish results via TEE-only control so only the authorized Phala TEE can decrypt aggregates and publish the approved/rejected outcome.
  • Settle outcomes back to NEAR governance by forwarding the verdict to the coordinator using coordinator_resume.
  • Use Case: A DAO wants paid, privacy-preserving deliberation where multiple workers cast encrypted votes and the DAO receives only the final tallies and verdict.

Quick Start

Ask the coordinator to activate confidential voting mode by setting task_config.voting_mode to "confidential" so it deploys DeliberaVoting on Zama and orchestrates encrypted voting, TEE finalization, and NEAR settlement.

Frequently Asked Questions about zama-blind-voting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement confidential DAO voting with FHE to prevent plaintext vote leakage?

You can implement confidential DAO voting by deploying a Zama fhEVM contract that registers proposals and accepts encrypted euint32 votes. The contract homomorphically accumulates tallies using FHE.add() without exposing individual ballot choices on-chain.

How does a trusted execution environment finalize encrypted voting tallies?

A Phala TEE finalizes encrypted voting tallies by enforcing TEE-only control over the finalize and publish calls. It decrypts the aggregated FHE results only after the voting deadline passes, ensuring the final approved or rejected outcome is auditable.

Can I settle Zama fhEVM voting outcomes back to the NEAR blockchain?

Yes, you can settle Zama fhEVM voting outcomes back to NEAR governance. The process forwards the finalized approved or rejected verdict to the coordinator using the coordinator_resume function for cross-chain settlement.

When do I need fully homomorphic encryption for DAO governance voting?

You need fully homomorphic encryption for DAO governance voting when preventing plaintext vote disclosure and on-chain vote manipulation is critical. It enables privacy-preserving deliberation where workers cast encrypted ballots and the DAO receives only final tallies.

Does confidential voting require a coordinator-driven deliberation workflow?

Yes, confidential voting requires a coordinator-driven deliberation workflow. The coordinator activates confidential voting mode by setting task_config.voting_mode, deploying the contract, and orchestrating the encrypted voting, TEE finalization, and NEAR settlement.