Cardano Critical Integrations V2

System2mo ago1 post

On-chain changes

  • 23,000,000 ₳paid tostake17xz...6ghh5qjr

Abstract

This governance action requests the withdrawal of ₳23,000,000 (USD 5,750,000 based on $0.25c) from the Cardano Treasury to cover a focused ‘Year 2’ contracted cost and a 12-month enhancement & maintenance program for the critical integrations already delivered or currently being integrated under the first Cardano Critical Integrations Budget (“CCI V1”): Circle (USDCx), LayerZero, Pyth Price Feeds, Dune Analytics, and a new full native integration of Fireblocks.

The CCI V2 initiative provides the necessary funding for the ongoing operation and optimization of infrastructure previously established. While CCI V1 was responsible for delivering the primary foundational framework and launch readiness, CCI V2 ensures that this infrastructure remains functional, reliable, and equipped with advanced features to support the expanding needs of the ecosystem.

Fund administration

Funds will be administered by Intersect under the Treasury Reserve Smart Contract Framework over a 12 month delivery window. Drawdowns occur only after signed agreements and Statements of Work are submitted and verified. Funds are expected to be ringfenced and held in stablecoins, until such time that they are needed.

Prior Treasury Receipt Disclosure

Pursuant to Article II, Section 7, Item 2 of the Cardano Blockchain Ecosystem Constitution, the proposer discloses that the prospective recipient of this Treasury Withdrawal, acting through the Pentad steering structure with Intersect as Administrator, received ₳70,000,000 from the Cardano Treasury in the prior 24 month period under the “Cardano Critical Integrations Budget” (gov_action1lqun78lcznfa2gek49m3ydslakfnm8heargfp8sax9fk54yl6ghsqp042zv).

The following integrations have either been successfully launched on mainnet or are currently in the implementation phase under CCI V1: Circle (USDCx on Cardano), LayerZero cross-chain messaging and bridge infrastructure, Pyth pricing oracles, and Dune Analytics coverage. V2 exists only to sustain, optimize and extend what V1 built, with the addition of Fireblocks institutional custody as a new integration funded within this withdrawal.

Motivation & rationale

CCI V1 Contracted Year 2 Licensing/Platform fees

All primary integrations from CCI V1 - specifically Circle, LayerZero, Pyth, and Dune - require ongoing annual payments for licensing, services, or attestations to remain operational. These recurring costs represent the necessary subscription investment for top-tier infrastructure access. To prevent the risks of inadequate maintenance funding, treasury commitments must be planned around this annual baseline. Accordingly, this proposal incorporates the contracted Year 2 expenses for these foundational CCI V1 integrations.

Maintenance Requirements by Integration

The integrations delivered under CCI V1 are live infrastructure. Keeping them live carries ongoing operating costs that must be funded year over year. Without funded maintenance, the usability of the integrations deteriorates:

  • Circle (USDCx): Attestor infrastructure and operations, monitoring, and the operational oversight from contract administrator.

  • LayerZero: Maintenance of the V1-delivered cross-chain messaging and bridge infrastructure: Cardano endpoint operations, DVN (security) configuration and validator set support, and protocol-version compatibility work as LayerZero ships upstream upgrades.

  • Pyth Network: Oracle feed continuity, push and pull publisher incentives, and Cardano-specific infrastructure.

  • Dune Analytics: Subgraph coverage, schema maintenance, and Cardano-dedicated dashboard refresh cycles.

Maintaining these systems is not optional for a chain that holds itself as infrastructure-ready. Competitive L1 ecosystems fund infrastructure maintenance as a recurring operating cost.

Fireblocks Native Integration

Fireblocks is a core custody and digital asset operations platform for institutional market participants, including exchanges, custodians, fintechs, asset managers, and market makers. Native Cardano support gives these institutions a standard way to custody, transfer, and manage ADA and Cardano Native Tokens (CNTs) through infrastructure they already use.

CCI V2 funds the full native integration of Cardano as a supported blockchain within Fireblocks. The integration is expected to cover core Cardano asset support, including ADA, CNT custody and transfer, and the technical foundations for Cardano-specific workflows such as ADA staking and governance delegation. This lowers the operational barrier for institutions to support Cardano assets, reduces the need for bespoke custody infrastructure, and strengthens Cardano’s readiness for exchange listings, regulated custody, treasury management, and institutional adoption.

Fireblocks Year 1 cost is included in CCI V2 and covers the Fireblocks blockchain integration fee and the initial annual platform fee.

Enhancements and Ad Hoc Tooling

Any new integration layer needs tooling around it to become usable, and deeper connectivity across the ecosystem’s dApps surfaces new tooling requirements continuously. This is a feature of live infrastructure. Examples include: monitoring and alerting enhancements around attestors and oracle feeds, improved reconciliation tooling between smart contract state and off-chain counterparties, observability infrastructure for cross-chain flows, and operational automation where manual intervention has been heavier than planned. A ring-fenced enhancement and tooling reserve allows the Steering Committee to fund these targeted upgrades within the 12 month window without standing up a separate governance action for each one. This reserve will go back to the treasury if not used.

Current Gap and Urgency

While initial development and launch are funded as one-off costs as covered in CCI V1, the ongoing work of keeping them live beyond year 1, secure, operational, and effective remains a continuous responsibility for as long as the network depends on them. CCI V1 contracting ran through 2025 and into early 2026. Several operating agreements expire or require renewal decisions within the 12 month window this V2 covers. Without a ratified V2 budget in effect, individual maintenance line items would require individual treasury actions, each with its own governance timeline, creating operational gaps in infrastructure the ecosystem now depends on.

Why Treasury Funding

Placing the CCI V2 budget under Intersect administration continues the constitutional framework already in effect for CCI V1: separate auditable addresses, auto-abstain delegation, milestone validation, independent audits, dispute resolution, and public reporting. This preserves community oversight and decentralized governance over the integration pipeline, without reinventing the administration structure that CCI V1 already established.

Steering Committee

The Pentad Steering Committee established as part of CCI V1 provides high-level business direction and integration governance for this initiative. The committee oversees maintenance prioritization, enhancement reserve deployment, and working group stewardship. Its purpose is to ensure that each agreement and drawdown delivers measurable ecosystem value and that decisions are made in the best interest of the Cardano community.

The Steering Committee operates as a five-member group representing Input Output Global, the Cardano Foundation, EMURGO, Midnight Foundation, and Intersect (non-voting, acting as Administrator). Members act independently to maintain neutrality. Together, they evaluate maintenance and enhancement priorities, approve disbursements against the ring-fenced categories, and supervise the Pentad working groups.

While ultimate accountability sits with the Steering Committee, dedicated sub-working groups continue to take operational responsibility across commercial, legal, technical delivery, analytics, and community and communications. Conflict of interest policies apply to all Steering Committee members when making allocation and disbursal decisions.

Scope of CCI V2:

  1. Operations & Maintenance: Operations and Maintenance: 12 months of ongoing operational costs for the CCI V1 integrations. Covers contracted Year 2 platform and licensing fees payable to integration partners, smart contract and protocol-compatibility upgrade work, ongoing developer support for live deployments, and the Cardano-side infrastructure required to keep each integration operational. This infrastructure includes attestor operations for Circle USDCx, DVN and endpoint operations for LayerZero, infrastructure for Pyth Price Feeds, and subgraph and schema maintenance for Dune Analytics.

  2. Fireblocks Native Integration: Full native integration of Cardano as a supported blockchain within the Fireblocks institutional platform. Scope includes support for ADA and Cardano Native Tokens (CNTs), with technical foundations for Cardano-specific workflows such as ADA staking and governance delegation. Costs cover the blockchain integration fee and Year 1 annual platform fee.

  3. Enhancement & Tooling Reserve: A ring-fenced fund for ad hoc technical upgrades and the "connective layer." This includes:

    1. SDKs & Reference Implementations: Lowering the barrier for dApps and wallets (e.g., the USDCx SDK).
    2. Protocol Compatibility: Updates to ensure integrations evolve alongside Cardano’s protocol standards.
  4. Compliance & Oversight: Necessary legal, audit, and administrative costs and constitutional oversight.

    Drawdown Oversight: Controlled by the Steering Committee based on defined scope, adoption metrics, and semi-annual reporting.

Exclusions

CCI V2 excludes the following:

  • New Tier-1 Integrations: Uncontracted targets from V1 (e.g., USDT0, specific custodial solutions, or new OFTs) are excluded and will be presented as separate governance actions if required.
  • Application Layer: Direct investment into individual dApps is excluded; these remain the domain of independent funding, however continuous onboarding support is provided by Intersect.

CCI V2 is scoped to four cost categories:

Contracted integration costs
Contracted annual license, platform, service, and attestation fees payable to Circle, LayerZero, Pyth and Dune under existing commercial agreements. These are the subscription costs of access to tier-one infrastructure and recur for as long as each integration is live. Fireblocks integration fee and the initial annual platform fee for Year 1 is also included.

Maintenance costs
Cardano-side operational costs to keep each integration live: attestor and relayer operations, endpoint and oracle feed continuity, partner-side protocol upgrade compatibility work, monitoring and alerting, and pass-through infrastructure expenses.

Enhancement and tooling reserve
Ring-fenced reserve for targeted upgrades to the monitoring, reconciliation, observability, and operational tooling around the V1 integrations. Drawdown requires Steering Committee approval against a defined scope request. A minimum allocation to this line is necessary to make the raw integrations usable at all: without shared connective tooling - SDKs, reference implementations, and builder-facing libraries - the raw integration endpoints are not accessible to most builders and every dapp has to build its own bridge to each integration, which is a tax that each dapp and the entire ecosystem pays on every new deployment. The reserve delivers broad benefit at marginal cost by providing white-glove tooling support to dapp builders rather than forcing each team to solve the same problems independently.

Legal, audit, contract administration, and contingency
Due diligence, independent audits (satisfying Article II.7.4), legal and compliance costs, contract administration, and a small contingency reserve to accommodate market shifts within the 12 month window.

The ₳23,000,000 request reflects the cost of running the CCI V1 integrations for a 12 month period, plus the Fireblocks Year 1 costs (integration fee and Year 1 annual fee). It also includes the enhancement and tooling reserve, and the audit and contingency lines constitutionally required. The figure is set to fit within the applicable Net Change Limit at the time of submission and is denominated in ada consistent with TREASURY-03a.

High-level budget breakdown

Due to confidentiality obligations with several integration partners, specific vendor-level costs cannot be publicly disclosed. The breakdown is presented by category and as a percentage of the total request. The Steering Committee is entrusted with executive decisions on allocation within each category. Unused funds at the end of the 12 month period will be returned to the Cardano Treasury.

Category Allocation (₳) Allocation % Description
Integration and maintenance costs 20,700,000 ~90% Operating costs for CCI V1 integrations: Circle USDCx, LayerZero, Pyth, and Dune. Includes licensing, platform, attestor, relayer, oracle, custody, infrastructure fees, and Fireblocks blockchain integration fee and Year 1 annual fee.
Enhancement and tooling reserve 1,150,000 ~5% Ring-fenced reserve for ad hoc upgrades to monitoring, reconciliation, observability, and operational tooling around CCI V1 integrations. This reserve will be returned to the treasury if not used.
Legal, audit, and contract administration 1,150,000 ~5% Due diligence, independent audits, legal and compliance, contract administration. Satisfies Article II.7.4.
Total 23,000,000 100%

Explicit Exclusions

The following are explicitly excluded from this withdrawal. Each may be brought as its own governance action so the community can vote on priority, pace, and preferred lead entity. Nothing in this withdrawal funds, pre-commits, or reserves capacity for any of them.

New integrations:

  1. Tether (USDT0) integration: May be brought as an individual community governance action following Pentad working group alignment and direct commercial negotiation.
  2. LayerZero OFT (Omnichain Fungible Token) expansion: Extensions to LayerZero beyond the V1 messaging and bridge infrastructure (including OFT standard deployment) may be brought as an individual community governance action.
  3. Additional DeFi, custodial, analytics, and compliance integrations: Any new integration outside the CCI V1 perimeter may be brought as an individual community governance action.

Application and ecosystem layer:

  1. Dapp funding and individual project investments. Dapp grants, individual protocol investments, and application-layer funding are not included in this withdrawal. New or existing external or community funding vehicles may be sought to support on a case by case basis, led by Dapp or individual project/s. Venture funding for early-stage teams is the role of existing vehicles such as Draper Dragon and Cardano Foundation Venture Capital.
  2. External liquidity attraction and DeFi liquidity deployment. Any treasury-funded liquidity programs will be brought as separate governance actions, scoped independently and reviewed on their own merits.
  3. Marketing, content creator/KOL, and events programs. Any marketing or events funding will be brought as separate governance actions.
  4. Dapp upgrade programs and application layer tooling beyond the V1 integration perimeter. Out of scope for this withdrawal.

Any future integration, liquidity program, or marketing program referenced in parallel IOG, Cardano Foundation, EMURGO, Midnight Foundation, or Intersect strategic documents is treated as forward planning only. No funding, commitment, or reserved capacity flows from this withdrawal to any of those items. Each will stand on its own merits when brought to the community.

Administration of Funds

This treasury withdrawal is submitted by Intersect in its role as the Administrator, and has been compiled with the endorsement and collaboration of the Cardano Foundation, Input Output Global, EMURGO, and Midnight Foundation as co-proposers. All treasury funds will be administered by Intersect under Article II, Section 7.5 of the Constitution, using the Treasury Reserve Smart Contract Framework. Intersect acts as the Administrator for the entire budget. Contracting for integrations will be assigned by the Steering Committee based on the best-fit entity that has the required skills, stability, and capacity.

Steering Committee Authority

The Steering Committee will approve maintenance renewals and enhancement reserve drawdowns. Quorum for any allocation decision is 3/4 of all Steering Committee voting members. Once an allocation is approved, Intersect administers and executes the associated disbursements to the contracting entity. The Steering Committee will publish progress reports upon achieving maintenance milestones and upon each enhancement reserve drawdown.

Role of Intersect and Contractual Counterparties

Intersect will receive the funds and administer this budget. Intersect will also, in its capacity as an Administrator, receive regular reporting and insight into budget expenditure. Upon enactment, funds will be received into the Treasury Reserve Smart Contract framework administered by Intersect, with multi-sig oversight from DQuadrant, NMKR, Cardano Foundation, Xbererus, and Sundae Labs.

Funds will be disbursed according to the contracting arrangements. Disbursements will be made directly from the smart contract framework or an institutional-grade custodian to vendors, as selected by the Steering Committee. For maintenance renewals with existing V1 counterparties, disbursements will follow the operational cadence of those contracts. Intersect and the co-proposers will endeavor to negotiate contracts that allow for as much public disclosure as reasonably possible, and the Steering Committee will disclose such information in progress reports.

Co-proposers or other entities chosen by the Steering Committee may, if required, act as the contracting counterparty with a maintenance or enhancement partner. When this occurs, Intersect and the Cardano Development Holdings will enter into a contract with the designated entity defining the scope, obligations, reporting requirements, and drawdown conditions. Intersect will only act as a contracting counterparty when it has completed its own due diligence and satisfied its Delivery Assurance standards.

All contracts established under this program will include clearly defined scope, obligations, reporting requirements, drawdown conditions, and dispute resolution provisions, in order to comply with Article II.7.1 of the Constitution.

Payment Execution and Safeguards

Disbursements will be executed through either smart contracts or institutional-grade custodians. These disbursements will follow the Statements of Work and commercial terms approved by the Steering Committee.

Unused funds and program conclusion

If at the end of the 12 month period the budget has not been fully utilized, all remaining funds will be returned to the Cardano Treasury. A final reconciliation and summary will be included in the oversight reporting by Intersect, in collaboration with the Steering Committee.

Refund Circumstances

Remaining ada will be returned to the Cardano Treasury in any of the following circumstances:

  • Conclusion of the 12 month delivery period with unused balance.
  • Termination of a maintenance or enhancement contract with funds previously earmarked but not yet disbursed.
  • A Steering Committee determination that any specific category (maintenance, enhancement reserve, or administration) has been fully satisfied with balance remaining.
  • Any material change in circumstance that renders continued disbursement inappropriate under the scope of this withdrawal.

Cardano Addresses

Treasury funds will be received and held by Intersect, acting as the Administrator, to a dedicated address addr1xxzc8pt7fgf0lc0x7eq6z7z6puhsxmzktna7dluahrj6g6v9swzhujsjlls7dajp59u95re0qdk9vh8mumlemw89535s4ecqxj which is publicly viewable.
To fulfill constitutional requirements, this address will be delegated to the predefined auto abstain voting option and will not be staked to any Stake Pool Operator (SPO), ensuring that the funds do not influence governance or generate staking rewards. Intersect will ensure oversight and transparency through independent audits and access to information.
Through this arrangement, the Cardano Development Holdings administered by Intersect maintains full custody transparency, enabling verifiable auditing and milestone tracking under Cardano’s constitutional governance framework, satisfying Articles II.7.4, II.7.5, and II.7.6 in particular.

Acceptance Criteria and Milestone-Based Disbursement

For maintenance drawdowns, acceptance is tied to continuation of operational service-level agreements with existing V1 counterparties. For enhancement reserve drawdowns, acceptance is tied to a Steering Committee approved scope request with defined deliverables and a Statement of Work. A “milestone zero” payment may cover essential setup costs of this initiative, including conversion of ada into a stablecoin for fiat-denominated partner payments, stablecoin minting fees, and custody fees. Converted assets will be held in a regulated custodian. Legal costs for maintenance and enhancement contracting are included in this early operational budget.

Any ada received from the treasury withdrawal will be held by the Administrator in one or more separate, dedicated accounts that can be audited by the Cardano Community, and such accounts shall not be delegated to an SPO but must be delegated to the predefined abstain voting option, in accordance with Article II.7.6. Any conversion of ada into stablecoins or other assets will occur only as part of an approved disbursement under a Statement of Work, and only after the relevant ada has been released from the Administrator's custody to the Treasury Withdrawal Recipient.

Reporting

Intersect and the Steering Committee will publish a bi-annual report covering:

  1. Financial Summary and Treasury Reconciliation: Total funds disbursed, remaining, and audited by category.
  2. Maintenance Status: Status of each CCI V1 integration under the maintenance umbrella (Circle, LayerZero, Pyth, and Dune), including uptime, renewals, and operational health.
  3. Fireblocks integration status: Status of the integration of Fireblocks.
  4. Enhancement Reserve Activity: Each enhancement drawdown, its scope, Statement of Work, and delivered outcome.
  5. Audit and Compliance Statement: Summary of independent audit findings.
  6. Governance and Future Outlook: Proposed next steps and the slate of individual community governance actions expected to follow from Steering Committee consultation and community prioritisation.

Rationale highlights

Why some of the largest DReps voted for and against, in their own words.

  • Yes584.2M ₳

    Summary Yoroi DRep votes YES on “Cardano Critical Integrations V2” as the necessary operational continuation of infrastructure the Cardano ecosystem already depends on. Rationale Maintenance of live infrastructure is not optional. The CCI V1 integrations are...

    Summary
    Yoroi DRep votes YES on “Cardano Critical Integrations V2” as the necessary operational continuation of infrastructure the Cardano ecosystem already depends on.
    Rationale
    Maintenance of live infrastructure is not optional.
    The CCI V1 integrations are in production. Circle USDCx, LayerZero, Pyth, and Dune Analytics each carry recurring licensing, attestation, and operational costs that must be renewed for the integrations to remain functional. Allowing these to lapse would degrade infrastructure that protocols and users already rely on, and funding them through a single ratified budget is more efficient than managing each renewal as a separate governance action.

    Fireblocks expands institutional access at a logical moment.
    Institutional adoption requires custody infrastructure that meets regulatory and operational standards. A native Fireblocks integration gives exchanges, asset managers, and custodians a standard pathway to support ADA and Cardano Native Tokens without bespoke solutions. Including Year 1 Fireblocks costs within this cycle, alongside existing maintenance, is a sensible sequencing decision.

    Governance and oversight structure is adequate.
    The Pentad Steering Committee provides cross-organizational oversight with quorum requirements for disbursements, and Intersect administers funds under the established treasury smart contract framework. The lack of vendor-level cost disclosure is noted as a limitation, but the combination of multi-party governance, milestone-based drawdowns, and mandatory return of unused funds provides sufficient accountability for Yoroi to support this proposal.

    Conclusion
    Yoroi votes YES on CCI V2 as a necessary and appropriately governed commitment to sustaining the institutional integration infrastructure Cardano has already invested in building.

  • Yes435.8M ₳

    Voting YES on "Cardano Critical Integrations V2." USDCx is necessary for DeFi. After all, the only product use case that has been advantageously adopted in the blockchain industry is stablecoins (excluding internal money games). USDCx currently has limited...

    Voting YES on "Cardano Critical Integrations V2."
    USDCx is necessary for DeFi. After all, the only product use case that has been advantageously adopted in the blockchain industry is stablecoins (excluding internal money games). USDCx currently has limited transaction volume, but it is worth maintaining. As for the other features, I have confirmed that multiple DApp developers intend to use them.


    「Cardano Critical Integrations V2」にYESを投票します。

    USDCxはDefiに必要です。結局のところ、ブロックチェーン業界で唯一、優位に利用されているプロダクトユースケースはステーブルコインのみです(内部的なマネーゲームを除き)。USDCxは現在Txボリュームは限定的ですが、維持する価値があります。
    その他の機能についても、複数のDApps開発者が利用したい意向を確認しました。

  • As a DRep, I have decided to vote NO on the proposal: Cardano Critical Integrations V2 My rationale: The first Critical Integrations proposal, CCI V1, requested ₳70,000,000 and explicitly stated: "Funds will be administered by Intersect under a performance...

    As a DRep, I have decided to vote NO on the proposal: Cardano Critical Integrations V2

    My rationale:

    The first Critical Integrations proposal, CCI V1, requested ₳70,000,000 and explicitly stated:

    "Funds will be administered by Intersect under a performance and milestone-based structure over a period of up to 24 months."

    It also stated that the budget covered integration work and related expenses, including deployment development, licensing fees, maintenance costs, and additional infrastructure required to support the integrations.

    The current CCI V2 proposal now asks for an additional ₳23,000,000 to cover a focused “Year 2” contracted cost and a 12-month enhancement and maintenance program.

    This includes platform and licensing fees, maintenance, operational costs, Cardano-side infrastructure, developer support, and related services for integrations that were already part of CCI V1.

    In my view, these categories appear to substantially overlap with what the original ₳70,000,000 budget was already expected to cover over a period of up to 24 months.

    Before asking the Cardano Treasury for additional funds, the proposers should provide a clear reconciliation of CCI V1: how much of the ₳70,000,000 has been committed, how much has been spent, how much remains, which partner contracts are already covered, and which Year-2 obligations were not included in the original budget.

    The V2 proposal also does not clearly define when “Year 2” begins.

    The V2 proposal says the new funds will be administered over a 12-month delivery window. Still, it does not clearly specify whether that period begins upon enactment, receipt of funds, contract signature, first drawdown, or the renewal dates of existing partner agreements.

    This is especially important because CCI V1 was approved near the end of 2025 and was described as a budget administered over a period of up to 24 months.

    Public announcements also suggest that some integrations are still relatively recent: USDCx was announced in February 2026, and Pyth live integration was announced in May 2026.

    In that context, asking for an additional “Year 2” budget already in May 2026 appears premature unless the proposers clearly explain why V1 does not cover these costs and when the Year-2 period actually starts and ends.

    Without that clarity, DReps cannot properly assess whether this proposal is timely, necessary, or an early renewal of costs that should already have been anticipated.

    I understand that some vendor-level costs may be protected by confidentiality obligations and NDAs. I do not expect the proposers to disclose sensitive commercial terms for specific partners if that would violate agreements or harm negotiations.

    Confidentiality around vendor pricing does not prevent the proposal from providing a clearer non-vendor-level breakdown.

    The proposal allocates ₳20,700,000, approximately 90% of the total request, to “Integration and maintenance costs,” but this category combines many different items: licensing, platform fees, attestor operations, relayers, oracle infrastructure, custody, Fireblocks costs, infrastructure fees, and maintenance.

    DReps are not told how much of this amount is expected to go to external NDA-covered vendors, how much is for Cardano-side engineering, how much is for work performed by Pentad-related teams or contractors, and how much is pass-through infrastructure or operational overhead.

    That distinction matters. Confidential vendor pricing can remain private, but DReps should still be able to evaluate whether non-confidential engineering, support, and FTE-like costs are reasonable and not already covered elsewhere.

    The current structure requires DReps to approve a large treasury withdrawal before they have access to the underlying contracts, commercial terms, vendor-level pricing, or detailed allocation logic.

    The proposal says that Statements of Work will be submitted and verified, and that some information will be disclosed through progress reports, but it does not make clear whether DReps will be able to review the relevant SoWs before approval or before drawdowns. This creates a governance gap: DReps are accountable for approving treasury withdrawals, but they cannot independently verify the full basis for the spending decision at the time of voting.

    For future proposals of this kind, I would support a stronger DRep-facing oversight mechanism.

    A reasonable solution could be a small group of DRep-elected representatives, bound by NDAs and strict conflict-of-interest rules, who can inspect the relevant contracts and drawdown requests confidentially.

    They would not disclose sensitive vendor terms, but they could provide public attestations that the spending matches the approved scope and that the split between vendor costs, internal engineering, infrastructure, administration, and overhead is reasonable.

    I must mention that I have read Intersect’s Critical Integrations status reports, and I acknowledge that they provide useful progress updates on the integrations.

    However, they do not provide the clarity I need as a DRep: they do not clearly explain why the original CCI V1 budget does not cover the relevant costs over its stated period of up to 24 months, when the CCI V2 “Year 2” period precisely begins, or how the non-NDA portion of the budget is broken down.

    I want to be very clear: I support Critical Integrations for Cardano. I also understand that a NO vote may be unpopular and may bring public criticism. I accept that.

    As a DRep, my responsibility is to protect the Treasury and approve funding only when the scope, timing, and budget are clear enough to evaluate.

    Supporting Critical Integrations and requiring clarity are not contradictory. I want to support this proposal, but clarity is not optional. Until the key questions are answered, I cannot responsibly vote YES.

    My conditions for approval are:

    1. Explain why the original CCI V1 proposal does not already cover the relevant costs over its stated period of up to 24 months.

    2. Define the exact period for the CCI V2 “Year 2” budget, including when the 12-month window starts and ends.

    3. Provide a clearer anonymized breakdown of non-NDA costs, especially separating external vendor/license costs from Cardano-side engineering, infrastructure operations, support, tooling, administration, and any Pentad-related or contractor work.

    Until these points are clarified, I cannot support the proposal in its current form.

    If you'd like to support my work, consider delegating to the MANDA pool and backing me as a DRep. Your support is the only way I can get time for governance.

    MANDA Pool ID:
    pool1c3fjkls7d2aujud8y5xy5e0azu0ueatwn34u7jy3ql85ze3xya8

    My DRep ID:
    drep1y2m0g4r66pyaw3p7u454wc0p4f0ygm8ueaev0mgd3tvwm7sskqwqp

  • No73.1M ₳

    I vote NO. I refuse to fund a second iteration when initial deliverables remain unfinished, despite administrative closure by Intersect. Furthermore, the highly unprofessional social conduct of contributors damages our brand. We demand full technical...

    I vote NO. I refuse to fund a second iteration when initial deliverables remain unfinished, despite administrative closure by Intersect. Furthermore, the highly unprofessional social conduct of contributors damages our brand. We demand full technical delivery and absolute professional maturity.

    A PDF version of this rationale is also made available.

    I am formally registering a NO vote on the Cardano Critical Integrations V2 Treasury Withdrawal. Whilst maintaining core infrastructure is undeniably important, I cannot support a request of this magnitude given the glaring issues surrounding both technical delivery and professional conduct.

    Firstly, I categorically refuse to authorise twenty three million ADA for a second iteration when numerous integrations from the initial funding round remain glaringly unfinished. The fact that Intersect has administratively classed the first phase as closed does not alter the reality on the ground that the original scope of work is incomplete. A public Treasury should never issue secondary funding while primary deliverables remain undelivered. The community expects absolute technical completion before any subsequent capital is unlocked. Compounding this issue is the proposal's financial structure, which once again sweeps over twenty million ADA into an opaque bucket entirely devoid of granular accountability.

    Furthermore, I must express my profound disappointment regarding the highly unprofessional conduct displayed by certain contributors to this proposal across our social channels. Cardano is a mature, professional ecosystem, and we fiercely protect our reputation and brand integrity. When individuals approach the public Treasury to request millions of dollars in community funds, we expect them to conduct themselves to the absolute highest standards of professionalism and decorum. The recent behaviour witnessed in the community falls drastically short of this mark and is fundamentally unacceptable.

    Until the outstanding deliverables from the first budget are fully completed on mainnet, and the individuals representing these proposals demonstrate the maturity and respect expected of enterprise infrastructure stewards, I will not support this withdrawal.

See all 65 rationales