Skip to content

DAO Tooling & On-Chain Governance

In short

DAO tooling lets an organization propose, vote, and execute on-chain without trusting a small multisig. Off-the-shelf products handle the common path; we build the custom logic, scoped roles, cross-chain execution, delegation, delayed and optimistic governance, and treasury controls, on Safe and Zodiac, where governance actually executes.

7,000+
stakers on the KyberDAO portal we built
$2B+
secured across our Safe deployments
130+
Safes deployed, official Safe partner
1M+
developers on Solhint, which we maintain
Trusted by teams building on-chain

DAO tooling is the software that lets a decentralized organization actually govern: propose, vote, and, crucially, execute the result on-chain without handing control to a small multisig. Off-the-shelf products cover the common path, a token, a voting front-end, a treasury Safe, and for many DAOs that is enough.

The engineering work begins where the standard path stops: when a DAO needs permissions scoped to specific roles, execution that spans several chains, optimistic or delayed governance, a custom voting or delegation model, or treasury controls that let contributors act without a full vote every time. That custom logic is what we build, on the two primitives most serious DAOs already run on, Safe and Zodiac.

Protofire builds governance from inside those tools rather than around them. Our public work includes contributions to the Zodiac stack, the composable DAO-tooling library built on programmable accounts, including its Roles and Exit modules and Safe app, an omnichain governance executor that carries a governance decision across chains, and a governance dashboard for MakerDAO.

We also built the KyberDAO governance contracts and its delegation portal, which serves 7,000+ stakers. So when a DAO needs behavior a generic product cannot express, we build it at the module and contract level, where governance actually executes.

On-chain governance is an execution pipeline

We build and customize each stage, from proposal to safe execution.

01

Voting & delegation

Token or NFT voting, delegation, and vote-escrow models that decide who has power and how much.
02

Proposal & tally

Governor or optimistic proposal flow that records intent and reaches a verifiable outcome.
03

Permissions

Zodiac Roles and scoped modules so an outcome executes only the actions it is allowed to.
04

Execution

Safe-based execution, with delay, cross-chain relay, or optimistic settlement as the design requires.
05

Treasury & dashboards

Treasury controls, reporting, and the front-end that makes the whole process usable.
01

What is DAO tooling?

Most people picture governance as voting, but the vote is the simple part. The hard, security-critical part is execution: once a proposal passes, something has to carry it out on-chain, change a parameter, move treasury funds, upgrade a contract, and it has to do so without concentrating that power in whoever holds the keys to the multisig.

A DAO that votes on-chain but executes through a small trusted committee has not really decentralized. Real on-chain governance means the execution path itself is constrained by the vote, which is a contract-engineering problem, not a UI one.

02

What we deliver

Custom Governor contracts, Zodiac Roles and delay modules, optimistic and delayed governance, vote-escrow and delegation logic, and cross-chain execution, built on Safe and Zodiac and hardened before audit.

03

Who is DAO tooling for?

Protocol DAOs come to us when the standard voting product cannot express what they need: role-scoped permissions, delayed or optimistic execution, custom delegation, or governance that acts across several chains. Treasury and multisig operators who have outgrown a plain Safe and need programmable controls, so sub-teams can operate within limits without concentrating power or slowing every action to a vote. New protocols designing their governance who want the execution and treasury architecture built correctly from the start rather than retrofitted after a governance attack or a stuck proposal. Projects migrating governance on-chain who need the contracts, modules, and dashboards to move from an off-chain vote plus a trusted multisig to real, constrained on-chain execution. The common thread is that the governance behavior they need is custom, and it lives in code that controls a treasury and a protocol, so it has to be right.

04

We build governance inside Safe and Zodiac

Protofire is a blockchain development company with 250+ shipped projects across 60+ networks and 95+ protocols since 2016. On governance specifically, we build on the Zodiac stack (Roles and Exit modules, Safe app), we implement cross-chain governance execution on LayerZero, and our public open-source work includes a governance dashboard for MakerDAO.

We built the KyberDAO governance contracts and its delegation portal serving 7,000+ stakers. We are an official Safe partner with 130+ Safes deployed, and Protofire-deployed networks secure $2B+ across 120+ EVM networks, so the account layer governance executes through is one we know deeply.

We also maintain Solhint, the Solidity linter used by 1M+ developers, so the governance contracts we ship are held to the standard we set for the ecosystem. When a DAO needs custom governance, we build it where it executes, not around the edges.

“Once a proposal passes, something has to execute it on-chain without handing that power to whoever holds the multisig keys. Building that constrained execution is the engineering.”

Open source we’ve shipped

The Protofire repositories behind this page

maker-governance-dashboard

→

A MakerDAO governance dashboard

Part of 190+ open-source repositories from Protofire

FAQ

What is DAO tooling?
DAO tooling is the software a decentralized organization uses to govern itself on-chain: to propose changes, vote on them, and execute the outcome without handing control to a small trusted group. It spans the voting and delegation model (who has power and how much), the proposal and tally mechanism (how intent is recorded and an outcome reached), the execution layer (how a passed proposal actually acts on-chain), and the treasury and permission controls (who can spend what, under which limits). Off-the-shelf products cover the common versions of these, a token, a voting front-end, and a treasury Safe. The engineering work is the custom part: scoped permissions, delayed or optimistic execution, cross-chain governance, bespoke delegation, and treasury controls that a generic product cannot express. That custom logic is contract engineering, because it controls a treasury and the power to change a protocol.
How is this different from using Tally, Aragon, or Snapshot?
Those are governance products, and for a DAO whose needs fit the standard path they are often the right tool: a token, off-chain or on-chain voting, and a treasury. We are engineers, and we come in where the product stops. If you need permissions scoped to specific roles, execution that spans several chains, optimistic or delayed governance, a custom voting or vote-escrow model, or treasury controls that let sub-teams act within limits, that behavior lives at the module and contract level, and we build it there, on Safe and Zodiac, the same primitives those products build on. In practice we often complement a governance product rather than replace it: you keep the voting front-end and we build the custom execution, permission, and treasury logic underneath it.
What is Zodiac and why build on it?
Zodiac is a framework of modules that turn a Safe into a programmable governance account. A plain Safe is a multisig: a fixed set of signers approves transactions. Zodiac modules extend it so that other things can control the Safe under defined rules, a Governor contract, an optimistic-governance mechanism, a cross-chain relay, or a Roles module that scopes exactly which actions a given role may execute. Building governance on Zodiac and Safe means the execution layer sits on audited, widely used primitives rather than a bespoke system, and it means a DAO's treasury account and its governance are the same account, not two systems bolted together. We contribute to the Zodiac stack and build custom modules on it, so we work inside the framework rather than treating it as a black box.
Can governance execute across multiple chains?
Yes. A protocol deployed on several chains often needs a single governance decision to take effect everywhere, a parameter change or an upgrade that has to apply on every chain at once, not chain by chain. We build cross-chain governance execution, where a proposal passed on the governance chain is relayed and executed on the others through a cross-chain messaging layer, as we did with an omnichain governance executor. The messaging layer is the security-critical part, since a forged cross-chain governance message could change a protocol everywhere, so we design it with the same care as any cross-chain integration: verified messaging, and constraints on what a relayed decision is allowed to do on each chain.
Do you build the treasury and delegation systems too?
Yes. A DAO has to operate day to day, not just at proposal time, so we build the treasury controls that let contributors and sub-teams spend within scoped, role-based limits without routing every action through a full vote, and the delegation systems that let token holders lend their voting power to representatives. We also build the dashboards and reporting that make treasury activity and governance legible, since governance nobody can follow is governance nobody uses. These sit on the same Safe account the DAO already holds its treasury in, with permissions enforced in code, so operational flexibility does not come at the cost of concentrating control back into a single multisig.

Reviewed by Luis Medeiros, Field CTO at Protofire. Last reviewed: July 2026.

Book a call with Alejandro Losa

Schedule a call with our Web3 Solution Architect to receive practical recommendations and a prompt proposal for upgrading your solution.

Protofire 2026. All rights reserved

Message us on Telegram