1. Application
Applicant name or organization: DAOplomats
Primary contact / forum handle: @Eren_Targ
Social handle (X and/or LinkedIn):
GitHub profile:
How did you hear about this grant program?: The Shutter DAO 0x36 Impact Pilot Round 1 Grant Guide thread on the Shutter forum
Wallet address for payment (if approved):
Application type:
Round 1 — Proactive grant for defined future work
Round 1 objective (select one):
- Objective 5 — Package a Repeatable Shutter Workflow
Contribution area:
- Research or technical work
- Ecosystem development, partnerships, or business development (supporting role: the outputs are sales and decision material for brainbot’s private-voting integrations)
2. The Shutter need or opportunity
What specific need, opportunity, or gap does this contribution address?
Shutter has strong privacy primitives for encrypted transactions and private governance, but DAO operators still need concrete, repeatable examples showing how those capabilities translate into governance and treasury execution workflows.
This proposal packages a practical demo kit for Shutter-protected DAO execution: a local reference flow where a DAO prepares a sensitive governance or treasury action, publishes a public commitment, keeps the action payload private until the reveal phase, and then verifies that the revealed payload matches the original commitment before execution.
The goal is not to rebuild Shutter’s encrypted mempool, Snapshot, or Safe infrastructure. The goal is to give DAO operators, delegates, and Shutter contributors a reviewable workflow artifact they can inspect, run locally, adapt, and use as a starting point for real integration discussions.
Why is it relevant to Shutter now?
The Round 1 guide asks for defined, reviewable work that advances a concrete Shutter need or opportunity. Objective 5 specifically asks applicants to turn an existing Shutter capability into a reusable workflow for a defined user, operator, or customer segment.
DAOs are a natural user segment for Shutter because they face information-leakage problems around treasury movements, governance execution, vendor selection, swaps, and timed disclosure. Today, those workflows are often either fully public too early or handled informally offchain. A reusable Shutter-style protected execution workflow would help make the value proposition concrete.
What specific demand signal supports this work now?
- The Shutter forum’s Round 1 Grant Guide explicitly identifies repeatable workflows, confidential coordination, timed disclosure, and reusable implementation guides as eligible Objective 5 work.
- Current submitted Round 1 proposals focus on private-voting evidence and PEN operations/adoption. A DAO execution demo kit would cover a different Shutter opportunity: protected action preparation and reveal for DAO governance and treasury operations.
Who benefits from the outcome, and how?
-
Shutter DAO 0x36: Benefits from a concrete demo artifact it can point to when explaining how Shutter-style privacy applies beyond abstract mempool protection.
-
DAO operators and contributors: Benefit from a runnable example of how to structure protected action flows without needing immediate production access to Safe, Snapshot, or Shutter infrastructure.
-
Shutter ecosystem contributors: Benefit from a reusable technical and educational artifact that can support future partner conversations, workshops, and implementation planning.
Value pathway
Validated path toward a pilot, integration, or repeatable workflow
Durable ecosystem, adoption, or public-goods value aligned with Shutter’s mission
Who is the relevant decision-maker, operating owner, funder, partner, or beneficiary group?
The primary beneficiary group is DAO operators and governance contributors evaluating privacy-preserving execution workflows.
The immediate operating owner for this grant is the applicant, who will deliver the public repository, demo, documentation, and handoff material.
The Shutter DAO 0x36 community is the review body and beneficiary for the reusable workflow package.
What problem are they solving, and what evidence supports the value of addressing it?
DAO execution workflows often reveal sensitive information before the DAO is ready to act. Examples include treasury transfers, token swaps, vendor selections, grant decisions, and governance actions where early disclosure can create market, coordination, or security risk.
Shutter’s core value proposition is reducing harmful information leakage through encryption and timed reveal. This grant translates that value proposition into a concrete DAO workflow package with code, schemas, verification steps, and operator documentation.
What Shutter product, deployment, service, or capability would this contribution advance?
This contribution advances Shutter-style encrypted transaction and timed-disclosure workflows for DAO governance and treasury operations.
It does not require production changes to Shutter infrastructure. Instead, it packages the workflow so future integrations with Shutter, Safe-style execution, Snapshot-style governance, encrypted RPC flows, or DAO tooling can be evaluated from a concrete reference point.
What decision, implementation step, or next action should this contribution enable, and by when?
By the Round 1 delivery target, the work should enable Shutter DAO contributors and DAO operators to decide whether this protected DAO execution workflow is worth advancing toward a real pilot with a specific DAO, Safe module, Snapshot flow, or Shutter integration path.
The next action enabled by the grant is a decision-ready pilot package: what the workflow protects, what it does not protect, what integration surface would be needed next, and which DAO workflows are the best first candidates.
What evidence will show progress beyond outreach, general interest, or a speculative concept?
- Build a small public demo kit, not a production integration.
- Runnable local flow: create protected DAO action → publish public memo → commit private payload hash → reveal → verify.
- Include two simple DAO examples: treasury transfer and vendor payout.
- Include JSON examples/schemas for public memo, private payload, commitment, reveal, and verification result.
- Add basic tests: correct reveal passes; modified payload fails.
- Add short operator docs: what it protects, what is out of scope, and how it could map to Shutter, Safe-style treasury execution, or Snapshot-style governance later.
Deliverables and acceptance criteria
| Deliverable | Description | Acceptance Criteria |
|---|---|---|
| Deliverable 1 | Public repository & runnable demo | Public GitHub repository includes setup instructions, working local demo, example inputs, and simple command to run flow end-to-end |
| Deliverable 2 | Protected DAO action schema package | Repository includes JSON schemas and examples for public memo, private payload, commitment, reveal, and verification outputs. |
| Deliverable 3 | Example DAO workflows | Includes at least two worked examples (e.g., treasury transfer, token swap, or vendor payout). |
| Deliverable 4 | Verification & test coverage | Demo includes tests or deterministic checks showing revealed payloads match commitments and modified payloads fail verification. |
| Deliverable 5 | Operator guide & risk writeup | Documentation explains intended users, protected information, non-goals, production assumptions, and integration path. |
| Deliverable 6 | Final forum recap | Final post summarizes shipped artifacts, links repository, explains runnable demo, and recommends pilot next steps. |
Milestone for the second 50% payment
The second 50% payment should be reviewed after the public repository contains the runnable demo, the schema package, at least two worked examples, verification checks, and the operator/risk documentation.
Timeline
| Phase | Timeline | Primary Objective |
|---|---|---|
| Week 1 | Finalize scope & architecture | Finalize workflow scope, payload schemas, and demo architecture. Publish repository skeleton and initial schemas. |
| Week 2 | Core demo development | Build local demo flow for creating a protected DAO action, generating public memo, committing to private payload, revealing, and verifying. |
| Week 3 | Examples & testing | Add worked examples, verification checks, tests, and operator documentation. |
| Week 4 | Documentation & handoff | Complete risk writeup, integration guide, final review pass, and public forum recap. |
Out of scope
This grant does not include production Shutter infrastructure changes, live Safe module deployment, Snapshot production integration, custody of funds, signing real transactions, or claims that the prototype is production-ready.
The deliverable is a reference implementation and workflow package, not a live execution system.
Risks and honest limits
-
The demo may show that some DAO execution workflows require deeper integration with Shutter, Safe, Snapshot, or DAO tooling before they are production-safe. That is useful evidence and will be documented clearly.
-
The prototype will not provide production-grade cryptographic guarantees beyond the reference commitment and verification flow. It will explain where Shutter infrastructure would be required for a real deployment.
-
Adoption by a specific DAO is not a grant milestone. The milestone is delivery of a concrete, reviewable workflow package that can support the next pilot decision.
3. Funding request
Total Amount Requested: $2,500
Budget Rationale
| Category | Cost | Allocation/Scope |
|---|---|---|
| Workflow Design & Architecture | $700 | Workflow design, schemas, and demo architecture |
| Prototype Implementation | $900 | Local prototype implementation and example DAO action flows |
| Testing & Verification | $400 | Verification checks, tests, and reproducible examples |
| Documentation & Guides | $300 | Operator guide, risk writeup, and integration map |
| Polish & Forum Recap | $200 | Final polish, public recap, and post-delivery issue triage |
Payment Structure: 50% after DAO approval/award; 50% after milestone review, consistent with the Round 1 process.
4. Prior compensation and disclosures
Have you, your organization, or a related party received or requested compensation for this work from Shutter or another source?
No
Do you have any financial, professional, or organizational conflict relevant to this application?
No
5. Public discussion
Forum post link: this thread.
Questions or feedback requested from the community: We would welcome community feedback on which DAO execution examples would make this demo kit most useful for Shutter reviewers and future operators. Our current plan is to focus on treasury transfer and vendor payout because they are common, DAO-native workflows where premature disclosure can create coordination or security risk. Feedback on the best future integration path would also be helpful, especially whether the follow-on pilot should prioritize Shutter encrypted transaction flows, Safe-style treasury execution, or Snapshot-style governance.
6. Applicant attestation
We confirm that the information in this application is accurate to the best of my knowledge; that I have disclosed relevant prior compensation and conflicts; and that we understand any award remains subject to the published process and DAO approval. We are also part of the Shutter Security Council.
Name / handle: DAOplomats
Date: 08/10/2026