Cardano Critical Integrations V2
203 DReps voted · 61 with a rationale
Open a row to read the rationale.
- Yes 271.5K ₳ No rationale
- Yes 261.3K ₳ No rationale
- Yes 260K ₳ No rationale
- No 258.6K ₳ Rationale
Review Methodology Disclaimer [EN]
Due not only to the unusually high volume of Treasury Withdrawal Governance Actions and budget proposals submitted in April and May 2026, but also to the lack of meaningful incentives for DReps to perform proposal analysis work, it is not feasible to apply my full standard review framework and reporting template to every proposal.
My standard analysis process usually requires approximately four hours of work per Governance Action. During that process, I research the proposal, review supporting materials, compare different perspectives from DReps and other ecosystem participants, and weigh both positive and negative arguments before reaching a reasonably qualified decision. Even with the use of artificial intelligence to automate parts of the workflow and improve productivity, a responsible evaluation still requires substantial human review, judgment, and contextual understanding.
In addition, this work does not end with the vote itself. It also involves writing and publishing rationales, preparing reports or summaries, communicating the reasoning publicly, and socializing the analysis through public channels and social media. This creates a significant workload, especially when dozens of proposals must be reviewed in a short period.
At present, this work carries no clear financial incentive and only limited reputational incentive, despite requiring substantial time, attention, and accountability. In practice, it is not sustainable to dedicate near full-time effort over several weeks or months to this activity without any form of compensation or institutional support.
Since I have a clear standard for my work and do not want to lower the quality of my judgment, I will reduce the scope of my analysis where necessary rather than rush decisions or produce superficial rationales. This means prioritizing focused due diligence over exhaustive review.
Under these constraints, my methodology during this period will focus on identifying critical strategic, operational, governance, reputational, or execution-related risks that could materially compromise a proposal’s viability, accountability, or successful delivery. In practical terms, this means narrowing my research toward the most critical gaps that may make approval unjustifiable. Where such a serious risk is identified, I may use it as the basis for a rejection vote.
This approach also helps reduce review overload: proposals with clear and material gaps would likely require rework regardless, so voting against them when those gaps are significant can be a responsible way to preserve review capacity while maintaining minimum due diligence.
Examples of such high-priority concerns may include, but are not limited to:
- Serious delivery failures in previous funded proposals;
- Significant unresolved delays in ongoing work;
- Major reputational or accountability issues within the ecosystem;
- Lack of credible execution capacity;
- Structural governance or transparency concerns;
- Severe budgetary or coordination risks.
Where I do not have sufficient time for a deeper evaluation, and no significant red flags or imminent execution risks are identified, I may abstain rather than issue an underdeveloped approval or rejection rationale.
This does not mean that other dimensions of proposal quality are unimportant. It means that, under current constraints, I will prioritize a narrower but still responsible review scope that preserves minimum due diligence, avoids rushed decisions, and keeps the quality of my judgment at an acceptable standard.
Governance Action Report
1. Introduction
This Treasury Withdrawal requests ₳23,000,000 from the Cardano Treasury to fund CCI V2, a 12-month continuation, enhancement, and maintenance program for Cardano Critical Integrations.
The request covers ongoing operational and contracted Year 2 costs for integrations delivered or currently being integrated under CCI V1: Circle USDCx, LayerZero, Pyth Price Feeds, and Dune Analytics. It also includes a new full native integration of Cardano into Fireblocks, intended to support ADA, Cardano Native Tokens, and technical foundations for Cardano-specific workflows such as staking and governance delegation.
Funds would be administered by Intersect under the Treasury Reserve Smart Contract Framework. Drawdowns would occur after signed agreements and Statements of Work are submitted and verified. The proposal states that unused funds would be returned to the Cardano Treasury at the end of the 12-month period.
The budget is divided into three high-level categories: ₳20,700,000 for integration and maintenance costs, ₳1,150,000 for an enhancement and tooling reserve, and ₳1,150,000 for legal, audit, and contract administration. Vendor-level costs are not publicly disclosed due to confidentiality obligations.
The prospective recipient, acting through the Pentad steering structure with Intersect as Administrator, previously received ₳70,000,000 from the Cardano Treasury under the CCI V1 budget.
2. Governance Action Review
Risks and concerns
Cardano governance currently lacks a formal conflict-of-interest policy governing how DReps should participate in Treasury Withdrawal votes when they are direct beneficiaries, formal representatives, executives, employees, founders, controlling stakeholders, or otherwise institutionally linked to the entity requesting funds.
This is a weakness in the current governance framework. Some DAOs within the Cardano ecosystem already have explicit guidelines addressing conflicts of interest, which shows that such standards are both feasible and desirable.
In the absence of formal rules, each DRep effectively becomes their own arbiter of what constitutes acceptable conduct. For that reason, a personal standard based on basic governance prudence has been adopted.
It has been publicly stated that when a DRep votes YES on a Treasury Withdrawal proposal from which they, or the institution they formally represent, directly benefit, the general position will be to vote NO. This is not necessarily a judgment on the technical or strategic merits of the proposal itself, but rather a position on governance process, conflict management, and institutional legitimacy.
It would be unhealthy for the ecosystem to normalize situations where delegated voting power is used to support funding requests that benefit the same entity exercising that voting power.
In this case, the concern is amplified by the scale of the voting power involved. The DReps associated with this proposal control approximately 1.2 billion ADA in delegated voting power, placing them among the most influential governance actors in the Cardano ecosystem.
3. Vote and Rationale
Vote: NO
The vote is based on governance process, conflict management, and institutional legitimacy, not necessarily on the technical or strategic merits of the proposal itself.
Cardano governance currently lacks a formal conflict-of-interest policy governing how DReps should participate in Treasury Withdrawal votes when they are direct beneficiaries, formal representatives, executives, employees, founders, controlling stakeholders, or otherwise institutionally linked to the entity requesting funds.
In the absence of formal rules, each DRep effectively becomes their own arbiter of what constitutes acceptable conduct. For that reason, a personal standard based on basic governance prudence has been adopted.
When a DRep votes YES on a Treasury Withdrawal proposal from which they, or the institution they formally represent, directly benefit, the general position will be to vote NO.
It would be unhealthy for the ecosystem to normalize situations where delegated voting power is used to support funding requests that benefit the same entity exercising that voting power.
In this case, the concern is amplified by the scale of the voting power involved. The DReps associated with this proposal control approximately 1.2 billion ADA in delegated voting power, placing them among the most influential governance actors in the Cardano ecosystem.
4. Conclusion
The NO vote reflects a governance-process position. In the absence of a formal conflict-of-interest policy, delegated voting power should not be normalized as a tool to support Treasury withdrawals that directly benefit the same entity or institution exercising that voting power.
Nota sobre metodologia e escopo de análise [PT]
Devido não apenas ao volume excepcionalmente alto de Treasury Withdrawal Governance Actions e propostas orçamentárias submetidas em abril e maio de 2026, mas também à falta de incentivos significativos para que DReps realizem o trabalho de análise de propostas, não é viável aplicar meu framework completo de revisão e meu template padrão de relatório a todas as propostas.
Meu processo padrão de análise normalmente exige aproximadamente quatro horas de trabalho por Governance Action. Durante esse processo, eu pesquiso a proposta, reviso materiais de suporte, comparo diferentes perspectivas de DReps e de outros participantes do ecossistema, e peso argumentos positivos e negativos antes de chegar a uma decisão razoavelmente qualificada. Mesmo com o uso de inteligência artificial para automatizar partes do fluxo de trabalho e aumentar a produtividade, uma avaliação responsável ainda exige revisão humana substancial, julgamento e entendimento contextual.
Além disso, esse trabalho não termina no voto em si. Ele também envolve escrever e publicar rationales, preparar relatórios ou resumos, comunicar publicamente a justificativa e socializar a análise por meio de canais públicos e mídias sociais. Isso cria uma carga de trabalho significativa, especialmente quando dezenas de propostas precisam ser avaliadas em um curto período.
Atualmente, esse trabalho não possui incentivo financeiro claro e oferece apenas incentivo reputacional limitado, apesar de exigir tempo, atenção e responsabilidade substanciais. Na prática, não é sustentável dedicar um esforço próximo de tempo integral durante várias semanas ou meses a essa atividade sem qualquer forma de compensação ou apoio institucional.
Como tenho um padrão claro para o meu trabalho e não quero reduzir a qualidade do meu julgamento, irei reduzir o escopo da minha análise quando necessário, em vez de tomar decisões apressadas ou produzir justificativas superficiais. Isso significa priorizar uma diligência focada em vez de uma revisão exaustiva.
Sob essas restrições, minha metodologia durante este período se concentrará em identificar riscos críticos estratégicos, operacionais, de governança, reputacionais ou relacionados à execução que possam comprometer materialmente a viabilidade, a accountability ou a entrega bem-sucedida de uma proposta. Na prática, isso significa concentrar minha pesquisa nos gaps mais críticos que possam tornar a aprovação injustificável. Quando um risco sério desse tipo for identificado, poderei usá-lo como base para um voto de rejeição.
Essa abordagem também ajuda a reduzir a sobrecarga de revisão: propostas com gaps claros e materiais provavelmente exigiriam retrabalho de qualquer forma, então votar contra elas quando esses gaps forem significativos pode ser uma forma responsável de preservar capacidade de análise enquanto se mantém uma diligência mínima.
Exemplos dessas preocupações de alta prioridade podem incluir, mas não se limitam a:
- Falhas graves de entrega em propostas anteriormente financiadas;
- Atrasos significativos e não resolvidos em trabalhos em andamento;
- Problemas graves de reputação ou accountability dentro do ecossistema;
- Falta de capacidade crível de execução;
- Preocupações estruturais de governança ou transparência;
- Riscos severos de orçamento ou coordenação.
Quando eu não tiver tempo suficiente para uma avaliação mais profunda, e nenhum alerta significativo ou risco iminente de execução for identificado, poderei me abster em vez de emitir uma justificativa de aprovação ou rejeição pouco desenvolvida.
Isso não significa que outras dimensões da qualidade de uma proposta não sejam importantes. Significa que, sob as restrições atuais, priorizarei um escopo de revisão mais estreito, mas ainda responsável, que preserve uma diligência mínima, evite decisões apressadas e mantenha a qualidade do meu julgamento em um padrão aceitável.
Relatório de Ação de Governança
1. Introdução
Esta Treasury Withdrawal solicita ₳23.000.000 do Tesouro da Cardano para financiar o CCI V2, um programa de 12 meses de continuidade, aprimoramento e manutenção das Cardano Critical Integrations.
A solicitação cobre custos operacionais contínuos e custos contratados do Ano 2 para integrações entregues ou atualmente em integração no CCI V1: Circle USDCx, LayerZero, Pyth Price Feeds e Dune Analytics. Também inclui uma nova integração nativa completa da Cardano ao Fireblocks, destinada a oferecer suporte a ADA, Cardano Native Tokens e bases técnicas para fluxos específicos da Cardano, como staking e delegação de governança.
Os fundos seriam administrados pela Intersect sob o Treasury Reserve Smart Contract Framework. Os saques ocorreriam após a submissão e verificação de acordos assinados e Statements of Work. A proposta afirma que fundos não utilizados seriam devolvidos ao Tesouro da Cardano ao final do período de 12 meses.
O orçamento é dividido em três categorias de alto nível: ₳20.700.000 para custos de integração e manutenção, ₳1.150.000 para uma reserva de aprimoramento e tooling, e ₳1.150.000 para custos jurídicos, auditoria e administração contratual. Custos por fornecedor não são divulgados publicamente devido a obrigações de confidencialidade.
O potencial recebedor, atuando por meio da estrutura de steering da Pentad com a Intersect como Administradora, recebeu anteriormente ₳70.000.000 do Tesouro da Cardano sob o orçamento CCI V1.
2. Análise da Ação de Governança
Riscos e preocupações
A governança da Cardano atualmente não possui uma política formal de conflito de interesse regulando como DReps devem participar de votos de Treasury Withdrawal quando são beneficiários diretos, representantes formais, executivos, empregados, fundadores, stakeholders controladores ou de outra forma institucionalmente vinculados à entidade que solicita os fundos.
Isso é uma fraqueza no atual framework de governança. Algumas DAOs dentro do ecossistema Cardano já possuem diretrizes explícitas tratando de conflitos de interesse, o que mostra que tais padrões são tanto viáveis quanto desejáveis.
Na ausência de regras formais, cada DRep efetivamente se torna seu próprio árbitro do que constitui uma conduta aceitável. Por essa razão, foi adotado um padrão pessoal baseado em prudência básica de governança.
Foi declarado publicamente que, quando um DRep vota SIM em uma proposta de Treasury Withdrawal da qual ele, ou a instituição que formalmente representa, se beneficia diretamente, a posição geral será votar NÃO. Isso não é necessariamente um julgamento sobre os méritos técnicos ou estratégicos da proposta em si, mas sim uma posição sobre processo de governança, gestão de conflitos e legitimidade institucional.
Seria prejudicial para o ecossistema normalizar situações em que poder de voto delegado é utilizado para apoiar solicitações de financiamento que beneficiam a mesma entidade que exerce esse poder de voto.
Neste caso, a preocupação é ampliada pela escala do poder de voto envolvido. Os DReps associados a esta proposta controlam aproximadamente 1,2 bilhão de ADA em poder de voto delegado, colocando-os entre os atores de governança mais influentes do ecossistema Cardano.
3. Voto e Justificativa
Voto: NÃO
O voto se baseia em processo de governança, gestão de conflitos e legitimidade institucional, não necessariamente nos méritos técnicos ou estratégicos da proposta em si.
A governança da Cardano atualmente não possui uma política formal de conflito de interesse regulando como DReps devem participar de votos de Treasury Withdrawal quando são beneficiários diretos, representantes formais, executivos, empregados, fundadores, stakeholders controladores ou de outra forma institucionalmente vinculados à entidade que solicita os fundos.
Na ausência de regras formais, cada DRep efetivamente se torna seu próprio árbitro do que constitui uma conduta aceitável. Por essa razão, foi adotado um padrão pessoal baseado em prudência básica de governança.
Quando um DRep vota SIM em uma proposta de Treasury Withdrawal da qual ele, ou a instituição que formalmente representa, se beneficia diretamente, a posição geral será votar NÃO.
Seria prejudicial para o ecossistema normalizar situações em que poder de voto delegado é utilizado para apoiar solicitações de financiamento que beneficiam a mesma entidade que exerce esse poder de voto.
Neste caso, a preocupação é ampliada pela escala do poder de voto envolvido. Os DReps associados a esta proposta controlam aproximadamente 1,2 bilhão de ADA em poder de voto delegado, colocando-os entre os atores de governança mais influentes do ecossistema Cardano.
4. Conclusão
O voto NÃO reflete uma posição sobre processo de governança. Na ausência de uma política formal de conflito de interesse, poder de voto delegado não deve ser normalizado como ferramenta para apoiar Treasury Withdrawals que beneficiam diretamente a mesma entidade ou instituição que exerce esse poder de voto.
The concern is further intensified by recent ecosystem discussions around delegation practices associated with the Yoroi wallet. EMURGO leadership has publicly acknowledged concerns regarding aspects of that delegation experience and the need to revisit those practices. Against that backdrop, exercising this concentrated voting power in support of a funding request benefiting the same institution creates a serious appearance-of-conflict issue.
Even where no formal rule is violated, governance legitimacy depends not only on procedural compliance, but also on whether conflicts are managed in a way that preserves trust in the decision-making process.
My vote therefore reflects concerns about conflict-of-interest management, voting power concentration, governance precedent, and institutional legitimacy.
- No 257K ₳ Rationale
I am voting NO on “Cardano Critical Integrations V2.” This proposal requests an additional ₳23M only months after the community approved ₳70M for CCI V1, which was described as a performance- and milestone-based budget administered over “up to 24 months.” The proposers have not provided a clear, DRep-facing reconciliation of that original ₳70M: how much is committed, how much has been spent, how much remains, and which Year-2 obligations were explicitly excluded from the original scope. Without that reconciliation, it is not possible to judge whether this second withdrawal is genuinely necessary, or whether we are being asked to pre-fund renewals and integration work that should already have been anticipated within V1.
The additional explanations and governance details provided in this proposal are welcome, but they still do not answer the core questions I must be able to resolve as a DRep. They do not clearly explain why the original CCI V1 budget of ₳70M, defined over “up to 24 months,” does not already cover the relevant maintenance and renewal costs, when the CCI V2 “Year 2” period precisely begins and ends, or how the non-NDA portion of this new budget is allocated between external vendor/licence costs and Cardano-side engineering, infrastructure operations, support, tooling, administration, and Pentad-related work. At the same time, ~90% of the requested amount is bundled into a single “integration and maintenance” line, combining licensing, platform fees, attestor/DVN/oracle operations, Fireblocks integration, and Cardano-side work without a non-vendor-specific breakdown. Confidentiality around individual contracts may be commercially understandable, but using that confidentiality to justify such a large opaque bucket is not acceptable at Treasury scale.
I support Critical Integrations for Cardano, and I recognise that a NO vote here may be unpopular and I accept that. My responsibility as a DRep is to protect the Treasury and approve funding only when the scope, timing, and budget are sufficiently clear to evaluate. Supporting Critical Integrations and requiring clarity are not contradictory positions. I would like to support this proposal, but budget and scope clarity are not optional. In its current form, this governance action leans heavily on the discretion of the Steering Committee and on bi-annual reporting, while asking DReps to approve a very large, bundled request without access to the underlying Statements of Work, pricing logic, or a clear separation between one-off integration work and steady-state Year-2 maintenance.
My conditions for a future YES are straightforward. First, explain why the original CCI V1 proposal does not already cover the relevant costs over its stated 24-month period, with a concrete reconciliation of committed, spent, and remaining funds by category. Second, define the exact 12-month period covered by the CCI V2 “Year 2” budget, including when it starts and ends, and how that aligns with the V1 approval date and partner contract timelines. Third, provide a clearer anonymised breakdown of non-NDA costs, especially separating external vendor/licence costs from Cardano-side engineering, infrastructure operations, support, tooling, administration, and any Pentad-related or contractor work. Until these points are addressed in a way that DReps and the wider community can independently assess, I cannot responsibly vote YES on this treasury withdrawal. - Yes 238.2K ₳ No rationale
- Abstain 215.5K ₳ No rationale
- Yes 212.5K ₳ No rationale
- No 208.6K ₳ Rationale
- Treasury runway is shrinking rapidly and must be protected.
1.51 - 1.62B ADA remains ($260M USD at ~0.16 USD/ADA). The 350M ADA 2026-27 NCL already risks ~21% drawdown. Aggressive prior spending + ADA weakness demands selectivity to avoid depletion before real adoption. - Infrastructure is important, but it is not the primary bottleneck. Cardano's core tech is solid. The ecosystem stalls on adoption, liquidity, developer experience, and compelling use cases (DeFi, RWAs, revenue-generating apps). Broad infrastructure funding without adoption KPIs won't drive organic ADA demand.
- Hoskinson's concerns deserve respect, but governance requires balance. Core maintenance matters for competitiveness. DRep duty is long-term sustainability: not unlimited spending. Past allocations often failed to yield proportional TVL/users/ADA utility. Prioritize evidence-based proposals.
- Better capital allocation strategy: Favor high-leverage use-case initiatives — especially RWAs and revenue-generating applications that commit to direct revenue or ADA return mechanisms back to the treasury, with clear milestones, private co-funding, and proven traction. Target specific tech unlocks only when tightly tied to measurable adoption impact. This builds real value without creating dependency.
- Treasury runway is shrinking rapidly and must be protected.
- Yes 203.6K ₳ Rationale
I trust the organisations involved to deliver.
- Yes 198.1K ₳ No rationale
- Yes 195.9K ₳ No rationale
- Yes 190.2K ₳ No rationale
- No 183.7K ₳ No rationale
- Yes 182K ₳ No rationale
- Yes 180.9K ₳ No rationale
- Yes 150.1K ₳ No rationale
- Yes 142.3K ₳ Rationale
I support the budget proposed by IOG for the development of PENTAD 2 and consider strengthening DeFi infrastructure and Cardano’s technical capabilities to be strategically important for the ecosystem. However, I would like to add a critical reflection regarding the direction part of the data and oracle infrastructure is taking.
I do not believe it is constructive to allocate resources toward integrating critical dependencies on external oracle providers such as Pyth while, at the same time, native Cardano oracle projects like Orcfax are left abandoned or without sufficient support. A blockchain aspiring to technological sovereignty and long-term resilience should not depend exclusively on external infrastructure for critical parts of its DeFi stack.
The recent history of the ecosystem should serve as a warning. Cardano relied for a period on the NOMAD bridge as one of the main arteries for bringing USDT and USDC liquidity into Cardano DeFi. After years of apparently functioning normally, it took only a few days after becoming truly systemic infrastructure within the ecosystem for the well-known multimillion-dollar hack to occur, severely damaging confidence and security around that infrastructure.
Beyond the specific responsibilities of that incident, the strategic lesson is clear: depending on external components for critical infrastructure introduces risks that Cardano does not fully control.
For this reason, I believe Cardano should prioritize supporting at least one truly native, decentralized, and economically sustainable oracle within its own ecosystem. The existence of native alternatives does not mean rejecting external integrations such as Pyth, but rather avoiding excessive dependency and providing Cardano DeFi with redundancy, technological sovereignty, and long-term strategic security.
I especially invite Charles Hoskinson and ecosystem entities to reflect on the importance of preserving fundamental native capabilities within Cardano, particularly in areas as sensitive as oracle infrastructure.
- Yes 137.6K ₳ No rationale
- Yes 137.3K ₳ No rationale
- Yes 131.7K ₳ No rationale
- Yes 115.6K ₳ No rationale
- Yes 111.7K ₳ No rationale
- Yes 100.3K ₳ No rationale
- Yes 88.7K ₳ No rationale
- Yes 79.8K ₳ No rationale
- Yes 72.1K ₳ No rationale
- Yes 69.8K ₳ No rationale
- Yes 65.9K ₳ No rationale
- Yes 61.9K ₳ No rationale
- Yes 61.8K ₳ No rationale
- Abstain 60.4K ₳ No rationale
- Yes 55.9K ₳ No rationale
- Yes 53K ₳ No rationale
- No 49.3K ₳ No rationale
- Yes 48.4K ₳ No rationale
- No 45.2K ₳ No rationale
- No 37.8K ₳ No rationale
- Yes 34.1K ₳ No rationale
- Abstain 27.3K ₳ No rationale
- Yes 26.3K ₳ No rationale
- Yes 25.7K ₳ No rationale
- Yes 15.5K ₳ No rationale
- Yes 11.3K ₳ No rationale
- Yes 10.7K ₳ No rationale
- No 8.1K ₳ No rationale
- Yes 6.8K ₳ No rationale
- Yes 1.7K ₳ No rationale
- Yes 974.8 ₳ No rationale
- Yes 18 ₳ No rationale