Treasury Withdrawals (4b10e579#0)
187 DReps voted · 73 with a rationale · 1 changed their vote · 3 re-voted unchanged
Open a row to read the rationale.
Changed votes: 1 to yes, together voting with 2.7M ₳ of voting power.
- Yes185K ₳No rationale
- Yes182.7K ₳No rationale
- Yes161.1K ₳Rationale
I’m voting yes on this first withdrawal because it’s about setting things up properly, not spending big money yet. The proposal clearly shows where the funds go — legal structure, smart contracts, and audits — and includes solid oversight and reporting. Having this foundation in place lets the community properly judge any larger liquidity deployment later.
- Yes157.8K ₳No rationale
- No149.8K ₳Rationale
While I support enhancing Cardano DeFi and stablecoin liquidity long-term, this initial spend on setup (including Cayman legal entity costs) is premature. With the U.S. Clarity Act markup actively underway, debating critical rules on stablecoin yields, DeFi interfaces, and asset certification that could directly impact Cardano's ecosystem, we should conserve treasury funds for targeted regulatory advocacy, legal defenses, or compliance initiatives if/when needed. Let's hold off until regulatory clarity emerges and revisit with stronger safeguards. This is consistent with my previous No vote on the respective budget proposal.
- Yes138.6K ₳No rationale
- Yes126.4K ₳No rationale
- Yes124.6K ₳No rationale
- No108.3K ₳No rationale
- No90.6K ₳Rationale
Governance Action Report
1. Introduction
A Treasury Withdrawal governance action requests 500,000 ADA from the Cardano Treasury to establish the legal framework and smart contract infrastructure required for the Stablecoin DeFi Liquidity Budget. The withdrawal covers three components: (1) formation of a Cayman Islands Foundation Company (FC) as the legal vehicle for fund management, (2) development of an administrating smart contract and user interfaces, and (3) a comprehensive security audit of the smart contract system.
All funds are to be received by an Amaru contract administered by a 9-person Interim Committee with a 5-of-9 multisignature requirement for disbursements. Named service providers include Walkers (Cayman) LLP for legal work, Invariant0 LLC for auditing, and Sundae Labs for Amaru contract setup and support. The proposal includes an ADA-denominated cost breakdown, notes that some values (e.g., director fees) are estimates, and states that monthly reporting and on-chain oversight mechanisms will apply.
2. Governance Action Analysis
Positive aspects
1) “Rails first” structuring (governance and controls before large capital deployment)
Building the legal structure + contract + audit + governance before releasing the bulk of the capital signals operational maturity.
Separating “setup” (500k ADA) from “capital deployment” (49.5M ADA) reduces the risk of “releasing everything” without:
an audited contract,
a legal framework,
selection processes,
oversight mechanisms.From a governance standpoint, this aligns with the idea that the treasury should fund institutional infrastructure when it increases auditability and discipline.
2) Internal coherence and governance design with checks
The original Info Action lays out a relatively complete model:
5-of-9 multisig for executive actions,
a dRep-based tDAO with impeachment, election, and shutdown powers,
the ability to freeze operations and allow only return-to-treasury flows.Having the contract hold LP tokens and assets increases on-chain auditability (at least in theory), because tracking fund state and protocol positions becomes easier.
3) Stablecoin liquidity has a plausible economic rationale
Stablecoin liquidity is often a real bottleneck for:
onboarding,
lower-friction trading,
lower slippage,
greater attractiveness for market makers,
higher DeFi composability.A slippage reduction KPI (e.g., “50% reduction”) connects to practical utility for users and traders and can be interpreted as a collective benefit (not only for a single app).
4) Attempt to avoid a “pure grant” (treasury return narrative)
The design mentions revenue return to the treasury (e.g., 15% of monthly revenue converted and sent; annual return expectations).
This creates a “treasury deployment with return” narrative rather than “treasury donation.”
In theory, this is closer to “capital allocation” than “subsidy with no consideration.”
Negative aspects
1) Constitutional risk and institutional transition risk (nullification)
The Treasury Withdrawal was submitted during a period when a new Constitution was being voted on.
If constitutional changes alter requirements, the action may become invalid or require rewriting.
This is not a legal detail. It is a direct governance risk. If CC members were already voting against it, the probability of being blocked was high early on.
2) “Info Action as authorization” does not hold under the new Constitution
The CC critique is coherent: under the current Constitution, Budget Info Actions are non-binding and therefore cannot “authorize” or “ground” a withdrawal.
If the Withdrawal depends on “approved by Info Action” as its legitimacy base, it starts with a structural defect.
Without a transition/grandfathering clause, the CC tends to evaluate only the current text and require the Withdrawal to be self-contained, without “references as substitutes.”
3) Mutable documentation (GitHub) vs immutability requirement
If supporting documentation points to mutable URLs, this violates an explicit constitutional immutability requirement (as alleged by some CC members).
Even with a “commit hash,” if the primary URL or evidence package is not explicitly immutable, it remains vulnerable to:
later content changes,
ambiguity about which version was “approved.”This compromises integrity and verifiability.
4) Severe institutional problem: KPIs and commitments outside the binding document
A central point: with Info Actions losing normative effect, everything not inside the Treasury Withdrawal does not exist as an enforceable commitment.
If KPIs (slippage, returns, reporting) stayed in the Info Action and were not carried into the Withdrawal:
they cannot be enforced,
continuity cannot be conditioned,
ex post claims that “they promised” cannot be justified.This destroys accountability. What remains is reputational trust, which is the opposite of robust governance.
5) Conceptual issue: “DeFi” label vs centralized execution
The naming is criticized: calling it “DeFi Liquidity Budget” can mislead perception.
Execution is centralized:
committee,
legal structure,
integration with desks/OTC,
administrative decisions.The community may interpret “DeFi” in the strong sense (operational decentralization), but the mechanism looks closer to an administered fund with governance.
This matters because many people vote on headlines, not full reading.
6) Overlap / double funding with already-approved initiatives (PentaD as example)
A medium-weight argument is raised: another large initiative is already approved and funded with the objective of integrations and improvements that tend to impact liquidity and attractiveness.
Even if it is not “the same thing,” there is overlap in outcomes:
stablecoin/integrations may increase liquidity indirectly,
improved on/off-ramp infrastructure and partnerships may change the landscape.If significant capital is already allocated to this “vector,” adding another 50M on the same axis may be inefficient.
7) Structural critique: subsidy for commercial niche and market distortion
This is treated as a high-weight argument:
Treasury funding for open source/public goods makes sense (market failure, low commercial appeal).
Treasury funding for commercial projects should require harder consideration (equity-like, loan, robust revenue share, or another mechanism that internalizes risk).
Subsidizing liquidity may become a band-aid that:
does not solve the structural cause of DeFi weakness in Cardano,
creates dependence on incentives,
repeats market patterns (temporary yield farming, mercenary liquidity).DeFi in Cardano has had enough time (years) and many initiatives have already failed. Before allocating more, there should be:
a diagnosis,
a retrospective,
an evaluation of historical ROI,
an understanding of what went wrong.8) Proposed return is low for high risk (poor risk/return profile)
The annual return KPI (e.g., 4%) looks low relative to:
stablecoin depeg risk,
impermanent loss risk,
oracle / market structure risk,
committee operational risk,
regulatory/jurisdictional risk,
smart contract / bridge / custody / desk risk.A comparison is made implicitly to conservative real-world alternatives where similar returns do not require this degree of operational and crypto-specific risk.
Result: too much risk for too little upside in terms of treasury return.
9) “If it’s so good, VC funds it” argument
A provocative but relevant point is raised:
If the risk/return profile were truly attractive and well-priced, private capital (VC/market makers) could fund it.
This reinforces the “treasury as subsidy” thesis: if the market does not fund it, risk-adjusted return may not be good enough, or the design depends on the treasury as a patient donor.
10) Preference for investment in research and structural solutions
A superior long-term alternative is suggested:
invest a fraction of this amount into research and development of DeFi models suited to eUTXO,
architecture standards, tooling, primitives, design space,
a decentralized and replicable approach.This targets causes rather than symptoms (liquidity) and reduces dependence on recurring capital injections.
11) Budget is still crude and weakly anchored to external references
Notes such as “director fees estimated” and high-level breakdowns are flagged.
Even with auditor-days, the following are missing:
salary references,
benchmarks,
vendor quotes,
robust justification for amounts.For an “administrative/legal” phase, precision should be higher because this is where “governance and control” is being purchased.
Risks and concerns
1) Psychological trade-off: sunk cost trap (even if small vs total)
Even if it is “only” 500k vs 50M (1%), there is still risk of psychological and institutional bias:
“we already spent on structure, so now we must go all the way.”
This effect is treated as minor, but acknowledged as possible. In governance, “minor” effects can become dominant narratives.
2) Real risk of money loss due to non-binding sequence
Because withdrawals are separate and non-binding, a plausible scenario exists:
Withdrawal 1 approved,
structure built,
Withdrawal 2 not approved due to market change, NCL ceiling, budget competition, or political support loss.In that case, 500k becomes sunk cost and fails to achieve the macro objective.
This is not exotic: governance shifts quickly, especially with NCL revisited frequently.
3) Technical and operational risks remain even with “anti-collusion”
Even with reputation and governance mechanisms, risks remain:
collusion (5 signatures can be obtained),
process failures (protocol/desk selection),
conflicts of interest,
human error in management,
political capture of the tDAO,
“soft corruption” via indirect incentives.Mitigation exists, but risk does not go to zero. Capital size amplifies any failure.
Potential impacts
Economic — Allocating 50M ADA now is a large share of the current NCL (without needing exact fractions). In a constrained environment, the evidentiary and return bar should be higher. The annual return KPI (e.g., 4%) looks low relative to the risk bundle (depeg, IL, oracles, operational, regulatory, technical). Subsidizing liquidity may create incentive dependence and repeat mercenary liquidity dynamics. If the market does not fund it, risk-adjusted return may not be strong, or the design depends on the treasury as a patient donor.
Technical — An audited contract is proposed, but technical and operational risks remain: depeg, impermanent loss, oracle/market structure, smart contract/bridge/custody/desk risk, plus process failures and human error.
Governance / political — Constitutional change may invalidate the action or require rewriting. Non-binding Budget Info Actions weaken the “approved by Info Action” base. Commitments outside the binding document reduce enforceability (KPIs, reporting, shutdown). Non-binding sequencing across withdrawals creates sunk-cost risk if the second stage fails. Risk of tDAO political capture and multisig collusion remains.
Reputational — “DeFi Liquidity Budget” may mislead perception while execution is centralized (committee, legal structure, administrative decisions). Many vote on headlines, not full reading.
3. Vote and Rationale
Vote: NO
The core of the negative vote is conceptual and economic, not only constitutional:
rejection of subsidizing a commercial niche in a constrained environment,
high opportunity cost,
low return for high risk,
risk of repeating the pattern of subsidized DeFi initiatives that do not sustain.Additionally, even if the concept were acceptable, the current design fails on formal governance:
dependency on a non-binding Info Action,
absence of binding KPIs inside the Withdrawal,
risk of “phase 1 approved, phase 2 rejected.”What could move toward ABSTAIN or YES (conditional, but unlikely)
Macro change (more bullish market, more treasury slack).
Size reduction (smaller share of NCL).
More convincing and robust return to treasury (better risk/return pricing).
KPIs, metrics, reporting, and shutdown conditions inside the binding document.
Better-defined risk mitigations (depeg, IL, oracles, operational risk).
Explicit coordination with already-approved initiatives, reducing overlap.
A “post-mortem” / evaluation stage of past DeFi investment history before another large allocation.
4. Conclusion
Separating “setup” from “capital deployment” reduces premature release risk, but formal failures and economic risks remain: reliance on a non-binding Info Action, KPIs outside the enforceable document, sunk-cost risk across withdrawals, and a weak risk/return profile for subsidizing a commercial niche in a constrained environment.
- Yes85.7K ₳No rationale
- Yes83.9K ₳Rationale
I am in favor of this treasury withdrawal request. I have already voted in favor of the budget info action and gave my rationale for that on the info action vote metadata. This action is about ensuring that the team is handling the funds in a responsible way, and I believe that they are. I am satisfied with the proposed process that this well known and respected team is putting forward to handle the funds. It should also be noted that, at current market rates, I wonder if there will still be enough funds to do everything that is being put forward, but that certainly does not mean that I think we should not give this team a chance to work that out.
On a separate note, I acknowledge that this withdrawal action is likely unconstitutional under the new constitution. This is, however, not the role of DReps to assess, and I believe all the rules as intended have been adhered to, between the withdrawl and budget info action. The choice to grandfather this will be up to the constitutional committees. - Yes77.2K ₳No rationale
- No74.5K ₳No rationale
- No65.9K ₳No rationale
- Yes58.5K ₳No rationale
- Yes56.1K ₳No rationale
- Yes55.1K ₳Rationale
As much as I have my concerns, which I previously expressed during the info action vote, I support the Cardano DeFi liquidity budget under the terms described in the info action. I have no say on constitutionality of the proposal as I do not serve on the CC and therefor as much as I both acknowledge and agree with the concerns brought up by both CC members who've voted on this proposal (Tingvard and Cardano Japan Council), they do not influence my opinion on whether this proposal should pass or not (from the perspective of an independent DRep not serving on the CC).
- No51.8K ₳Rationale
No, The Defi liquidity budget is at the high-end of the total treasury, the delivery is unclear and improper update to the community.
More explanation needs to be involved when the project is late in delivery.
- Yes48.7K ₳Rationale
Good!
- No48K ₳No rationale
- No45.3K ₳No rationale
- Yes28.8K ₳No rationale
- Yes26.7K ₳Rationale
Yes, all requirements have been met that I specified I needed for withdrawals. See the original IOG 'temperature check' proposal.
- Abstain15.7K ₳No rationale
- Yes15.3K ₳No rationale
- Yes10.7K ₳Rationale
I like this proposal, so vote yes.
- Abstain8.4K ₳No rationale
- Yes6.8K ₳No rationale
- Abstain4.1K ₳No rationale
- Abstain3.4K ₳No rationale
- No1.2K ₳Rationale
It's not clear all the basic fundamentals as to why we need this as an ecosystem. You outline how you will obtain funding but you don't describe the products we are funding and why we need it. Development of what type of smart contracts and for what? Seems expensive and unclear.
- Yes675.6 ₳No rationale
- Yes167.1 ₳No rationale
- No116.1 ₳No rationale
- Abstain4 ₳No rationale
- Abstain0 ₳No rationale