Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
LABS
Glossary

Zodiac

Zodiac is an open standard and collection of reusable modules for extending the capabilities of Gnosis Safe, enabling complex DAO governance patterns like roles, delays, and bridges.
Chainscore © 2026
definition
DAO FRAMEWORK

What is Zodiac?

Zodiac is a collection of open-source tools and standards for building modular, interoperable DAOs on Gnosis Safe.

Zodiac is an open-source framework and collection of Ethereum Improvement Proposals (EIPs) designed to make Decentralized Autonomous Organizations (DAOs) modular, upgradeable, and interoperable. Originally developed by the Gnosis Guild, it extends the capabilities of the Gnosis Safe multisig wallet by enabling a 'Reality Module' pattern, where governance logic is separated from the treasury. This allows DAOs to adopt, swap, and combine different governance mechanisms—such as multisig, token voting, or futarchy—without migrating funds or redeploying core contracts, significantly enhancing flexibility and security.

The core innovation of Zodiac is its modular architecture, which introduces the concept of an Avatar and Modules. The Avatar is the DAO's treasury contract (typically a Gnosis Safe), while Modules are separate, attachable contracts that contain executable logic. Key module types include the Reality Module for executing on-chain actions based on off-chain votes (via tools like Snapshot), the Delay Module for introducing a timelock on proposals, and the Exit Module for enabling members to redeem their share of the treasury. This separation allows for risk containment, as a compromised module does not directly endanger the main treasury.

Zodiac's standards, particularly EIP-2535 (Diamond Standard) and EIP-3722 (Avatar Standard), provide the technical backbone for this interoperability. The Avatar Standard defines a common interface that any treasury contract can implement, allowing any compliant module to control it. This has led to a vibrant ecosystem where projects like Colony, DAOstack, and Tally have built Zodiac-compatible tools, enabling DAOs to create custom governance stacks. For example, a DAO could use a Snapshot vote processed by a Reality Module, with a Delay Module enforcing a 48-hour waiting period before the Safe executes the transaction.

The framework fundamentally shifts DAO design from monolithic, rigid structures to composable legos. This addresses critical pain points like upgradeability and vendor lock-in. A DAO can start with a simple multisig, later integrate token voting via a module, and eventually delegate specific authorities to sub-DAOs or specialized managers—all without a complex and risky migration. By standardizing how modules interact with treasuries, Zodiac reduces integration overhead and fosters a competitive market for governance tooling, empowering DAOs to evolve their processes as their needs change.

In practice, Zodiac is most commonly encountered through integrations with popular DAO tooling platforms. The Gnosis Safe interface natively supports adding Zodiac modules, and governance platforms like Tally provide user-friendly interfaces for creating and managing proposals through Reality Modules. Its adoption by major DAOs like ShapeShift and mStable demonstrates its utility for production-grade decentralized organizations. As a set of standards rather than a single product, Zodiac's primary impact is enabling the composability and experimentation essential for the next generation of DAO governance.

how-it-works
MODULAR SMART ACCOUNT STANDARD

How Zodiac Works

Zodiac is an open standard for building modular smart contract accounts on Ethereum, enabling the decomposition of a wallet's functionality into replaceable, interoperable modules.

Zodiac works by implementing the EIP-2535 Diamond Standard, which allows a single smart contract account (the Diamond) to delegate its logic to a collection of independent, swappable contracts called facets. This architecture separates a wallet's core functionality—such as transaction execution, ownership management, and security policies—into discrete modules. A central Diamond Proxy forwards function calls to the appropriate facet based on a pre-configured lookup table, enabling a single contract address to possess an unlimited and upgradeable set of capabilities without the storage and gas limitations of traditional monolithic contracts.

The standard introduces key components that define its modular ecosystem. The Avatar is the core Diamond contract that holds the assets and serves as the identity for a DAO or user. Modules are the facets attached to the Avatar, each governing a specific permission or action, such as a Reality Module for optimistic oracle-based execution or a Bridge Module for cross-chain governance. A Modifier is a special type of module that can intercept and condition transactions before they reach their target, enabling complex security rules. This design allows teams to mix and match modules from different developers, creating a custom, composable smart account.

In practice, a DAO using Zodiac might deploy an Avatar as its treasury. It could then attach a Safe (from Gnosis Safe) as its transaction execution module, a Delay Modifier to impose a timelock on high-value transactions, and a Reality Module to allow token-based voting on proposals that execute automatically via an oracle. Because modules are hot-swappable, the DAO can later replace its voting module without migrating assets or changing its primary treasury address. This provides unparalleled flexibility, allowing protocols to evolve their governance and security models over time while maintaining a persistent on-chain identity.

The interoperability of Zodiac modules fosters a vibrant ecosystem where developers can create specialized components—like cross-chain bridges, automated treasury managers, or custom role-based access systems—that work seamlessly with any Zodiac-compatible Avatar. This stands in contrast to closed, monolithic smart account systems, as it prevents vendor lock-in and encourages innovation through competition. By standardizing the interfaces between the Avatar, Modules, and Modifiers, Zodiac ensures that security audits and best practices can be applied consistently across the ecosystem, reducing the attack surface for complex DeFi and DAO operations.

Ultimately, Zodiac's modular architecture addresses critical limitations in smart contract design: upgradeability without migration, functional specialization without bloat, and collaborative development without fragmentation. It provides the foundational plumbing for advanced on-chain organizations, enabling them to act as sophisticated, programmable economic agents. As the standard gains adoption, it is becoming a critical piece of infrastructure for DAOs, institutional DeFi, and any application requiring flexible, secure, and future-proof smart account management.

key-features
ZODIAC

Key Features

Zodiac is a modular framework of open-source tools and standards for building composable, upgradeable, and secure DAO tooling on Ethereum and Gnosis Chain.

01

Modular Architecture

Zodiac promotes a modular design where DAO components are separate, interoperable contracts. This allows for:

  • Composability: Tools like a delay module or a reality.eth oracle can be mixed and matched.
  • Upgradeability: Individual modules can be replaced without a full DAO migration.
  • Reduced Risk: Isolates functionality, limiting the attack surface of any single component.
02

The Avatar Pattern

A core design pattern where a Zodiac Avatar (a smart contract) acts as the sovereign identity of a DAO. This Avatar:

  • Holds Assets: Owns the DAO's treasury (tokens, NFTs).
  • Executes Transactions: Modules with the correct permissions can execute arbitrary calls from the Avatar.
  • Enables Interoperability: Any tool that can interact with a standard Ethereum address can interact with the DAO via its Avatar.
03

Roles & Permissions

Zodiac uses a flexible role-based access control system, often implemented via the Roles modifier. This allows a DAO to:

  • Delegate Authority: Grant specific capabilities (e.g., 'mint tokens', 'add liquidity') to modules or individual addresses.
  • Enforce Multi-Sig: A Safe multisig is a common Avatar, where transactions require M-of-N signatures from owners.
  • Create Hierarchies: Build complex permission trees, such as a sub-DAO that can only manage a specific asset pool.
04

Reality.eth Oracle Integration

Zodiac provides a standard bridge to the reality.eth oracle (formerly Reality.eth) for on-chain execution of off-chain decisions. The process is:

  1. A question (e.g., "Transfer 100 ETH to address X?") is posted to the oracle.
  2. Token holders or delegates vote off-chain using tools like Snapshot.
  3. The oracle attests the final result on-chain.
  4. A Zodiac oracle module reads this attestation and executes the transaction from the Avatar.
05

Delay & Exit Modules

Critical safety modules that introduce friction and optionality into DAO governance.

  • Delay Module: Imposes a mandatory timelock (e.g., 24-72 hours) on executed transactions, allowing token holders time to review and potentially cancel malicious or erroneous actions.
  • Exit Module: Allows members to ragequit or exit the DAO with a proportional share of the treasury assets, typically based on a verified Snapshot vote. This is a key credible neutrality and safety mechanism.
06

Cross-Chain & Bridge Compatibility

Zodiac's design is chain-agnostic, but it has deep integration with the Gnosis Chain ecosystem. Key tools include:

  • Omni Bridge: A canonical bridge for moving assets between Ethereum and Gnosis Chain.
  • Zodiac Bridge Module: Allows a DAO on one chain (e.g., Ethereum) to control an Avatar on another chain (e.g., Gnosis Chain) via bridge messages. This enables cross-chain treasury management and governance.
core-modules
SAFE EXTENSIONS

Core Zodiac Modules

Zodiac is a collection of open-source, composable modules that extend the functionality of the Safe (formerly Gnosis Safe) multi-signature wallet standard, enabling complex on-chain governance and automation.

examples
ZODIAC

Real-World Examples

Zodiac's modular design enables a variety of governance and treasury management patterns, from multi-chain DAOs to automated protocol operations.

06

DAO-to-DAO Collaboration via Zodiac

Two DAOs can collaborate using a shared Zodiac Safe. They use a Reality Module where each DAO's Snapshot space votes. The proposal only executes if both spaces pass it, enabling trust-minimized, conditional cooperation, such as co-funding a grant or jointly governing a liquidity pool.

2+
DAOs Required for Execution
ecosystem-usage
ZODIAC

Ecosystem Usage

Zodiac is a collection of open-source tools and standards for building modular, interoperable DAOs and smart accounts on Gnosis Safe. It enables complex, multi-chain governance and automation.

technical-details
MODULAR GOVERNANCE STANDARD

Zodiac

Zodiac is an open standard for composable and upgradeable DAO tooling, enabling the creation of modular governance systems.

Zodiac is an open standard and collection of Ethereum smart contract libraries that enable the creation of modular, upgradeable, and interoperable DAO (Decentralized Autonomous Organization) tooling. Developed by the Gnosis Guild, its core philosophy is to decompose monolithic governance systems into a collection of replaceable components—like avatars, guards, and modules—that can be mixed, matched, and upgraded over time. This modularity allows DAOs to adapt their governance and treasury management strategies without requiring a full migration to a new smart contract system.

The architecture is built around three primary components: the Avatar, which is the contract that holds a DAO's treasury and is the ultimate executor of actions; Modules, which are plug-in contracts authorized to make calls on the Avatar's behalf (e.g., for voting, multisig, or automation); and Guards, which are contracts that can be attached to Modules or the Avatar to set custom rules and security conditions for transactions. This separation of concerns allows for high flexibility, as a DAO can use a Safe multisig as its Avatar, a Snapshot-based voting module for proposals, and a reality.eth oracle guard to verify off-chain execution conditions.

A key innovation of Zodiac is the Roles modifier, which implements a capability-based security model. Instead of a simple allow/deny list, the Roles system grants modules specific permissions (or capabilities) to interact with target contracts, providing fine-grained control over what a DAO's modules can do. This is a more secure and flexible pattern than traditional ownership-based models, reducing the attack surface by limiting modules to pre-authorized actions on specific contracts.

In practice, Zodiac has become a foundational layer for the DAO tooling ecosystem. It is the standard that enables platforms like Colony, Tally, and Syndicate to build customizable governance interfaces on top of Gnosis Safe. Its interoperability means a proposal passed in a Snapshot vote on Tally can be automatically executed by a Zodiac module, bridging the gap between off-chain signaling and on-chain execution. This has made it a critical infrastructure for treasury management, protocol upgrades, and guild coordination across Web3.

The standard's emphasis on composability and upgradeability directly addresses common DAO pain points, such as vendor lock-in and governance rigidity. By allowing DAOs to swap out voting mechanisms, treasury management strategies, or security layers piecemeal, Zodiac future-proofs governance systems. Its open-source nature and extensive documentation have fostered a rich ecosystem of community-developed modules and guards, cementing its role as a public good for decentralized governance.

security-considerations
ZODIAC

Security Considerations

Zodiac is a set of open standards and tools for building modular smart contract accounts, primarily used to create and manage DAO governance structures. Its composable nature introduces unique security trade-offs.

01

Module Trust & Attack Surface

The core security model is module-based. The main safe is a minimal contract, with all functionality delegated to attached modules. This means:

  • The attack surface expands with each new module.
  • A vulnerability in any single module can compromise the entire safe.
  • Rigorous auditing of third-party modules is critical, as they execute with the safe's full permissions.
02

Role & Permission Management

Zodiac relies on roles (via modules like Roles) to gatekeeper sensitive actions. Key risks include:

  • Over-permissioned roles that grant excessive power to a single address.
  • Role escalation vulnerabilities where a module with one permission can gain another.
  • Static permissions that don't adapt to changing threats, requiring manual updates.
03

Bridge & Cross-Chain Risks

Modules like the Connext Bridge or Celery enable cross-chain governance, introducing complex risks:

  • Bridge trust assumptions: Reliance on the security of the external bridging protocol.
  • Message verification failures: A compromised relay or incorrect proof could execute malicious payloads.
  • Replay attacks across chains if nonce or domain management is flawed.
04

Governance Delay & Emergency Response

Modules such as the Reality Module or Delay Modifier introduce timelocks for security. Considerations:

  • Timelock bypass: If a malicious proposal passes, the delay provides a window for a fallback mechanism (e.g., an Exit Module) to be triggered.
  • Emergency response latency: The very security delay can hinder rapid reaction to an active exploit.
  • Oracle manipulation affecting on-chain execution of off-chain votes.
05

Composability & Upgrade Paths

The power of Zodiac is its composability, but this creates upgrade complexity:

  • Tight coupling: Modules may have undocumented dependencies on each other's state.
  • Immutable links: Some module connections can be difficult to remove without a full safe migration.
  • Standardization gaps: Not all modules follow identical security patterns, increasing review burden.
ARCHITECTURE COMPARISON

Zodiac vs. Native Governance

A technical comparison between the modular Zodiac framework and a protocol's native, monolithic governance implementation.

Governance FeatureZodiac (Modular)Native (Monolithic)

Core Architecture

Composable modules (Avatar, Roles, Delay, etc.)

Integrated, hardcoded smart contract system

Upgrade Path

Module-by-module; hot-swappable components

Full protocol upgrade or migration required

Execution Flexibility

Any call via Avatar; multi-chain via Connext

Limited to predefined protocol functions

Security Model

Defined per module (e.g., Delay, Multisig)

Baked into core protocol logic

Development Overhead

Assemble existing standards (EIP-2535)

Build and audit custom system from scratch

Gas Cost for Proposal Execution

Higher (additional delegatecall overhead)

Lower (optimized for specific actions)

Time to Finality

Configurable via Delay Module

Fixed by protocol parameters

Ecosystem Integration

Pluggable with DAO tools (Safe, Snapshot)

Often requires custom frontends and tooling

ZODIAC

Frequently Asked Questions

Common questions about Zodiac, a modular framework for building and composing DAO tooling on Gnosis Safe.

Zodiac is a collection of open-source, interoperable tools and standards designed to transform a standard Gnosis Safe multisig wallet into a modular, composable DAO (Decentralized Autonomous Organization) framework. It works by deploying a series of specialized smart contract modules that attach to a Safe, each granting it new capabilities. For example, a Reality Module enables on-chain execution based on oracle-reported outcomes, while a Bridge Module allows the Safe to interact with other blockchains. This modular approach allows DAOs to customize their governance, treasury management, and operational logic without needing to deploy a monolithic, custom smart contract system from scratch.

ENQUIRY

Get In Touch
today.

Our experts will offer a free quote and a 30min call to discuss your project.

NDA Protected
24h Response
Directly to Engineering Team
10+
Protocols Shipped
$20M+
TVL Overall
NDA Protected Directly to Engineering Team
Zodiac: Open Standard for DAO Governance Modules | ChainScore Glossary