# Governance and Automation

CurveYield 2.0 is designed to be controlled by the CurveYield DAO, with automation handling routine strategy, reward, bridge, and fee operations.

The governance goal is true DAO control, not symbolic governance. CurveYield is designed so DAO-controlled infrastructure owns the system rather than a founder wallet, deployer wallet, or private core-team multisig retaining final override authority.

## DAO ownership model

CurveYield's production ownership model routes control through:

1. CurveYield DAO governance through Aragon.
2. Cross-chain messaging for supported remote chains.
3. DAO-controlled Safe multisigs or governance executors on each chain.
4. Contracts and treasuries owned by those DAO-controlled addresses.

The DAO control path covers:

* pool factory wrapper parameters;
* fee policy registries;
* settlement contracts;
* permanent liquidity vaults;
* treasury recipients;
* vault managers and strategy permissions;
* credit market parameters where CurveYield controls them;
* bridge ownership and fee recipients;
* cross-chain control systems;
* incentive programs and reward streams;
* tokenomics and revenue-routing settings;
* emergency or pause roles where those roles exist.

The DAO / owner target for the Phase 1 Base pool infrastructure is:

`0x7142b1Cc5F91A736A62e77581F406338328F05bC`

## No founder override

CurveYield's governance standard is that production contracts and treasuries are controlled by DAO-governed infrastructure, and the founder does not retain unilateral owner overrides after production ownership transfers are complete.

Public contract references list ownership information where it is available.

## Aragon DAO and cross-chain control

CurveYield is moving toward an Aragon DAO-controlled model where DAO decisions can control contracts and treasuries across supported chains.

The intended model is not a symbolic vote followed by manual team execution. The intended model is onchain governance capable of controlling the addresses that own contracts, treasuries, fee routes, and risk parameters.

Public governance pages list final Aragon, Safe, executor, and cross-chain control addresses as they become part of the public deployment set.

## Automation model

CurveYield is automation-first. Automation reduces manual operations, lowers overhead, improves consistency, and keeps more protocol value inside the ecosystem.

Keepers perform bounded operations such as:

* allocating idle vault deposits when thresholds are met;
* harvesting rewards;
* claiming Merkl distributions;
* switching reward modes when the expected improvement exceeds the configured threshold;
* compounding reward tokens into the vault's underlying asset;
* settling pool fees;
* topping up approved keeper gas balances within caps;
* publishing vault rates across chains;
* monitoring route health and withdrawal assumptions.

Automation does not replace governance. Keepers operate inside permissions, caps, and routes approved by governance or DAO-authorized managers.

## Operating standard

CurveYield uses automation, simulations, monitoring, and AI-assisted tooling to reduce operating overhead. Production decisions still require public source code, contract verification, testing, live monitoring, permission caps, incident response planning, and governance review for major changes.

## Superfluid reward streaming

CurveYield has been developing Superfluid-style automated reward streaming incentives.

Reward streaming can make incentives more precise than manual reward campaigns. It may be used for LPs, vault participants, strategic liquidity, or partner programs where approved by governance.

Public stream details are listed when a stream is active for a supported product, including supported token, chain, funding source, stream controller, and governance permissions.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.curveyield.com/architecture/governance-and-automation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.