Cardano Adds Reusable DAO Building Blocks

Input Output has completed two reusable protocols that give Cardano developers a foundation for managing application configuration and decentralized decision-making. Reported in the September 11, 2026, development update, the delivery covers settings changes and a governance lifecycle spanning proposals, voting and closure.

Contracts Library Supports Cardano Application Governance

The contracts-library belongs to the Cardano Developer Experience initiative. It develops standardized components that teams can adapt to their applications, with an emphasis on DeFi.

The settings protocol manages configuration changes, while the DAO protocol organizes participation through voting positions, proposals and votes. Their scope is governance within applications built on Cardano.

The accompanying specifications describe how the contracts behave, and the off-chain implementations provide the code needed to interact with them.

Settings Changes Separate Proposal From Execution

According to the DevX documentation, the settings protocol separates submitting a change from applying it. A proposer records a pending value and its application time without modifying the active configuration. A separate authorized role applies the change after the required delay.

The DAO implementation uses three cooperating validators for voting positions, proposals and votes. Its lifecycle covers proposal preparation, support gathering, voting, tallying and closure.

A voting position can support multiple concurrent proposals. The documented model locks the largest individual stake commitment rather than adding all commitments together.

Reference Implementations Require Application Checks

The library’s delivery plan calls for contracts prepared for auditing. The completion announcement does not report a finished security audit or production deployment of these components.

The reference settings implementation includes a data-validation function that currently accepts all values. Integrators must add checks defining which configurations their applications permit. The DAO specification also documents limitations, including one tally operation per transaction and no deadline for vote cancellation.

The two protocols connect through a settings UTxO from which the DAO reads its governance parameters at runtime. This keeps those parameters outside the validator code and gives developers a defined connection between application configuration and the proposal-and-voting lifecycle.