Cardano Critical Integrations V2 Targets Fireblocks and Long-Term Infrastructure Support

Cardano Critical Integrations V2 has entered the DRep governance debate as a treasury proposal focused on maintaining existing integrations and adding native Fireblocks support for institutional use. The discussion, hosted by Nicolas Cerny, governance lead at the Cardano Foundation, brought together representatives from the Cardano Foundation, EMURGO, Input Output, and the Midnight Foundation to explain why Cardano’s next infrastructure step is tied to operations, vendor commitments, and long-term support.

Pentad Connects CCI V2 to Circle, Pyth, Dune and LayerZero

The first Cardano Critical Integrations program was structured around five infrastructure areas, a tier one stablecoin, institutional custody and wallet infrastructure, an analytics platform, a cross chain bridge, and pricing oracle infrastructure. During the roundtable, speakers pointed to Circle, Pyth, and Dune as the main integrations already delivered or active, while LayerZero remains delayed because of work on the LayerZero side.

Frederik Gregaard, CEO of the Cardano Foundation, described the program as an interoperability effort designed to connect Cardano with other blockchain ecosystems, traditional finance infrastructure, and enterprise grade vendors. He said Cardano had already built a strong base layer, but needed contracted infrastructure partners to support liquidity movement, data services, bridges, and broader institutional access.

Phillip Pon, CEO of EMURGO, framed the first phase as evidence that Cardano’s founding entities and ecosystem organizations could coordinate around concrete infrastructure outcomes. He said the Cardano Foundation, Input Output, EMURGO, Intersect, and Midnight had worked together through the Pentad structure to secure integrations that Cardano had lacked for years.

CCI V2 extends that work by focusing on maintenance, support, and the completion of a full native Fireblocks integration. Jarrell Moroney of Input Output said the proposal is intended to build on the first phase rather than expand into a broad new list of items. He described Circle related maintenance as part of the reason for the second proposal, because stablecoin integrations require support, operations, and contractual commitments after they are launched.

Native Fireblocks Integration Targets Institutional Cardano Access

The central new item in CCI V2 is full native Fireblocks support. Fireblocks is an institutional digital asset infrastructure and custody platform used by financial institutions, asset managers, market makers, exchanges, and other companies that need controlled access to digital assets. Giorgio Zinetti, CTO of the Cardano Foundation, described Fireblocks as a leading institutional custody provider and said many banks, asset managers, and market makers require deep Fireblocks integration before working seriously with Cardano assets.

Pon distinguished the existing SDK based solution delivered by Iagon from a full native Fireblocks integration. He described the Iagon work as live, functional, and useful for the community, but said it is not the same as native Cardano support inside the Fireblocks platform.

According to Pon, native integration would include MPC security for transactions, native signing infrastructure, policy engine support, governance controls, full EUTXO handling, staking support, and standard visibility for Cardano native tokens inside the Fireblocks console and APIs. He also said the integration would treat Cardano native tokens as first class assets, removing the need for custom setup and approval flows for every individual client.

That distinction matters for exchanges and institutional partners that already use Fireblocks. Zinetti said native Fireblocks support could make it easier for those firms to list or support Cardano native tokens, because the technical burden would be reduced. In that model, assets such as $NIGHT could move through a more familiar institutional infrastructure stack rather than requiring bespoke Cardano integrations from each platform.

The roundtable also connected Fireblocks to regulated token use cases. Pon referenced CIP 113 programmable token controls, including seize and freeze functionality for compliant real world asset issuance and institutional stablecoin use cases. That places Fireblocks inside a broader infrastructure discussion that includes custody, exchange access, real world assets, governance controls, and support for Cardano native assets.

DReps Face an Operating Decision on Treasury-Funded Infrastructure

CCI V2 also raises a governance question for Cardano. The proposal asks the ecosystem to fund infrastructure that includes ongoing costs, third party support, and multi year obligations connected to already delivered integrations.

The discussion presented the second phase as a way to maintain existing infrastructure, continue support around $USDCx, and complete the Fireblocks integration needed for institutional custody and exchange workflows.

Fahmi Syed, president of the Midnight Foundation, said Midnight supported the Pentad work because Cardano’s success also supports Midnight’s broader ecosystem. He connected the integrations to liquidity, institutional custody, wallets, oracle infrastructure, interoperable bridges, and applications that can use Cardano and Midnight together. He also said that infrastructure alone does not create adoption, because the ecosystem still needs liquidity, applications, and builders to use the components being delivered.

The roundtable addressed the limits of transparency around commercial infrastructure agreements. Some pricing, vendor, and contract details cannot be fully disclosed because of confidentiality requirements. Pon said conversations with DReps under NDA could provide more information where possible, while public discussion must avoid breaching partner obligations.

Maintenance was also discussed as an operational requirement. Fireblocks related maintenance would be handled by Fireblocks itself, with possible expert support from the Cardano Foundation, Input Output, and Intersect. For Circle related work, the panel discussed the possibility of using institutional providers such as BitGo or Kiln for monitoring and attestation functions, depending on the final structure.

The CCI V2 proposal turns the Critical Integrations program from a delivery question into an operating question. Cardano is no longer only deciding whether to bring major infrastructure partners into the ecosystem. DReps are now weighing how that infrastructure is maintained after launch, who carries operational responsibility, and how treasury funding should support stablecoins, custody, oracle data, analytics, cross chain access, and institutional support for Cardano native assets.