Cross-chain treasury fragmentation and capital dependency

Context

Curve operates across multiple chains, while treasury assets and protocol liquidity exist in several locations simultaneously — LP positions, DAO-owned liquidity, gauges, and chain-specific deployments.

This creates a gap between the nominal treasury size and the capital that can actually be redeployed quickly across the ecosystem.


Observation

Capital mobility for the DAO is constrained by structural factors such as:

• liquidity locked in Curve LP positions across chains
• governance execution delays for treasury actions
• bridge latency when moving assets between networks
• operational buffers held to manage bridge and execution risk

As a result, a portion of treasury capital is not immediately redeployable even though it appears in the balance sheet.


Questions

For contributors involved in treasury and governance decisions:

  1. What is the typical time from a treasury governance decision to actual capital movement on-chain?

  2. Roughly what portion of DAO-controlled liquidity is effectively non-mobile because it sits inside LP positions or cross-chain deployments?

  3. Does the DAO maintain a consolidated cross-chain treasury balance sheet, or are assets tracked across multiple dashboards and subgraphs?


Motivation

Resolving these constraints can unlock tens of millions of dollars in additional deployable liquidity for the Curve ecosystem and significantly increase capital efficiency across chains.