Tweag Core Cardano Infrastructure: Treasury Withdrawal 2026–2027
149 DReps voted · 51 with a rationale
Open a row to read the rationale.
- Yes 624.8K ₳ Rationale
Resubmission, ₳18,263,496 / $4,565,874 at $0.25, 3 Reduction: 53% smaller, and the work package count dropped from 17 to 3. Peras v1 (cryptography, KillSwitch, mainnet readiness, support), History Expiry (partial-history nodes to cut SPO storage costs), Conformance Testing (both Peras and Leios).
A PDF version of this rationale is also made available.
I'm switching to a yes because the structural problem that drove my no vote has been resolved, not just resized. My original concern wasn't about Tweag's competence on Cardano's core infrastructure, it's that 17 work packages submitted as a single pipeline prevented the kind of granular evaluation this treasury process exists to provide. That concern doesn't disappear by default just because a team resubmits; it disappears when the resubmission actually addresses it. Here, three work packages remain, and they're interdependent for a coherent reason rather than bundled for convenience: conformance testing is the correctness scaffolding that has to exist before Peras can be trusted on mainnet, and History Expiry exists specifically to absorb the storage cost consequences that Peras and Leios throughput increases create for SPOs. That's a single technical program with three components, not seventeen unrelated asks wearing one cover sheet.
Peras going to mainnet is the production-readiness step that makes Cardano's prior research investment in faster finality actually matter, dropping from roughly twelve minutes to roughly two minutes is the kind of improvement that changes what's buildable on Cardano, and it's complementary to, not duplicative of, the Leios research work I already voted to fund. History Expiry is the decentralization safeguard that has to exist alongside that throughput growth, because full-history storage requirements becoming economically prohibitive for smaller SPOs is exactly the kind of centralizing pressure that erodes the network from the bottom up rather than the top down.
Tweag's track record carries real weight here. This is a team that's been embedded in Cardano's consensus and ledger work since January 2018, built Ouroboros Genesis, and contributed directly to Peras's own design, they are not making a case for capability, they're continuing work they've already proven they can do. At ₳18,263,496, less than half the prior ask, with an explicit $176-per-hour engineering rate disclosed and a dual-review acceptance structure running through both IOG and an independent third-party assessor, this is a tighter, more accountable, and more honestly scoped proposal than what I voted no on. The prior no was a request for better structure, not a rejection of the work. Tweag has delivered a better structure. - Yes 589.2K ₳ Rationale
Yes. This proposal invests in critical core infrastructure that strengthens Cardano's scalability, resilience and usability, delivering faster transaction finality through Peras while reducing operational costs for SPOs and improving developer tooling. This epresents a strategic investment in Cardano's long-term growth and competitiveness.
- No 587.1K ₳ No rationale
- Yes 559.5K ₳ No rationale
- Yes 534.3K ₳ Rationale
Critical to get Peras V1 to mainnet and increase the finality time. Enhancing everything about the network from security to scalability
- Yes 466.2K ₳ No rationale
- Yes 445.1K ₳ No rationale
- Yes 431.4K ₳ No rationale
- Yes 426.2K ₳ No rationale
- Abstain 385.6K ₳ Rationale
Abstaining, as I’m part of the Cardano Constitution Committee Tingvard.
Reading proposals and staying updated, just like you.
Thanks to all fellow DReps who are also doing the hard work.
Follow and DM me on X: @kenerik if you have any questions. - Yes 382.6K ₳ No rationale
- No 377.3K ₳ No rationale
- Yes 314.4K ₳ No rationale
- Yes 313.1K ₳ No rationale
- Yes 298.6K ₳ Rationale
I voted for the 2-year Tweag withdrawal. Its unfortunate that it did not pass. Happily they have resubmitted and I see no reason not to support it.
- No 295.2K ₳ No rationale
- Yes 279.5K ₳ No rationale
- Yes 271.5K ₳ No rationale
- Abstain 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 — Tweag Core Cardano Infrastructure: Treasury Withdrawal 2026–2027 [EN]
This is a quick-check vote. I am not taking a position here on the technical merit, strategic relevance, or necessity of the proposed work.
My vote is NO due to insufficient budget granularity.
The proposal requests a large treasury withdrawal but does not provide enough detail to allow an independent assessment of whether the requested amount is proportionate. It references an average rate of USD 176/hour and uses FTE-based costing, but it does not clearly disclose how many people will work on the project, what roles they will perform, how hours are allocated across milestones, what seniority mix is assumed, or how the estimated workload was derived.
For a treasury withdrawal of this scale, this level of budget detail is not sufficient. DReps should not be required to infer the actual staffing model or rely primarily on trust in the proposer and later contracting arrangements. Without a clear breakdown of personnel, responsibilities, hours, and milestone-level costs, the budget cannot be adequately verified before voting.
For this reason, I vote NO.
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 — Tweag Core Cardano Infrastructure: Treasury Withdrawal 2026–2027 [PT]
Voto: NÃO
Este é um voto de quick check. Não será tomada posição, aqui, sobre o mérito técnico, a relevância estratégica ou a necessidade do trabalho proposto.
O voto é NÃO devido à granularidade insuficiente do orçamento.
A proposta solicita uma retirada relevante do Tesouro, mas não fornece detalhes suficientes para permitir uma avaliação independente sobre a proporcionalidade do valor solicitado. A proposta menciona uma taxa média de USD 176 por hora e utiliza uma estimativa baseada em FTE, mas não informa com clareza quantas pessoas trabalharão no projeto, quais funções serão exercidas, como as horas serão distribuídas entre milestones, qual composição de senioridade foi assumida ou como o volume de trabalho estimado foi calculado.
Para uma retirada do Tesouro dessa escala, esse nível de detalhamento orçamentário não é suficiente. DReps não deveriam precisar inferir o modelo real de alocação de equipe nem depender primariamente da confiança no proponente e em arranjos contratuais posteriores. Sem uma decomposição clara de pessoas, responsabilidades, horas e custos por milestone, o orçamento não pode ser adequadamente verificado antes do voto.
Por esse motivo, o voto é NÃO.
- Yes 257K ₳ Rationale
I am voting YES on “Tweag Core Cardano Infrastructure: Treasury Withdrawal 2026–2027.” This revised proposal directly addresses the concerns I had with the earlier 39.8M ADA, multi‑year, 17‑package version by narrowing the scope to three clearly critical components (Peras v1, History Expiry, and conformance testing), reducing the budget to 18.26M ADA, and constraining funding to a single 2026–2027 cycle. Peras fast finality, sustainable SPO storage via History Expiry, and stronger conformance/testing infrastructure for Peras and Leios are foundational for Cardano’s next growth phase, and Tweag has an established track record delivering this class of core infrastructure.
The custody and governance setup uses audited treasury contracts, auto‑abstain delegation, milestone‑based disbursements, and explicit proportional refund conditions for undisbursed or de‑scoped work. In this narrower and time‑bounded form, I view the proposal as a focused, high‑impact public‑goods investment in Cardano’s core protocol stack, and I am satisfied that it now fits both my treasury‑discipline expectations and the ecosystem’s need to get Peras and related infrastructure safely to mainnet.
- Yes 245K ₳ Rationale
This work delivers Peras v1 to mainnet (faster finality, ~2 min vs ~12 min) - the one item with no other funded delivery vehicle in the 2026 cycle - plus History Expiry (SPO storage economics under Leios) and Conformance Testing to de-risk both. The resubmission cuts scope from 17 packages to 3 and budget ~54% (₳18.26M vs ₳39.79M), keeping the load-bearing work and dropping peripheral tooling. Tweag has led Cardano consensus/ledger since 2018, with a disclosed rate card ($176/hr, ₳0.25/ADA) and ₳11.07M prior receipts tracked on-chain. The only tradeoff vs the original proposal is losing Peras v2's Hard Fork Combinator window, which is acceptable since v1 mainnet is the priority and v2 can follow later, hopefully in better market conditions with a stronger Ada value.
- No 238.2K ₳ No rationale
- Yes 237.5K ₳ No rationale
- Yes 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 ₳ No rationale
- Yes 195.9K ₳ No rationale
- Yes 190.9K ₳ No rationale
- Yes 190.2K ₳ No rationale
- No 183.7K ₳ No rationale
- Yes 182K ₳ No rationale
- Yes 180.9K ₳ No rationale
- Yes 142.3K ₳ No rationale
- Yes 131.7K ₳ No rationale
- Yes 100.3K ₳ No rationale
- Yes 72.1K ₳ No rationale
- Yes 65.9K ₳ No rationale
- No 60.4K ₳ No rationale
- No 49.3K ₳ No rationale
- Abstain 45.2K ₳ No rationale
- No 37.8K ₳ No rationale
- Yes 15.5K ₳ No rationale
- No 6.8K ₳ No rationale
- Yes 974.8 ₳ No rationale
- Abstain 289.1 ₳ No rationale
- No 31.5 ₳ No rationale
- No 0 ₳ No rationale