Daily News 19

Tag: Institutional custody

  • Cardano Foundation, Fireblocks Open Native Tokens to Institutions

    Cardano Foundation, Fireblocks Open Native Tokens to Institutions

    Key Highlights

    • Cardano Foundation and Fireblocks announced a technical roadmap to bring Cardano Native Tokens (CNTs) onto Fireblocks’ institutional custody platform by March 2027, covering CIP-26 and CIP-68 token standards.
    • The integration will allow thousands of banks, exchanges, payment firms, and fintechs using Fireblocks to custody, send, and receive CNTs with the same security and policy controls applied to other digital assets.
    • Fireblocks, which secures over $16 trillion in digital asset transactions, has supported ADA since 2021; this move eliminates manual steps previously required for CNT custody and positions Cardano-issued assets directly in front of institutional infrastructure users.

    Cardano Foundation and Fireblocks Map Institutional Custody Path for Native Tokens

    The Cardano Foundation, the Swiss nonprofit overseeing the Cardano blockchain ecosystem, announced on September 24 a strategic integration with Fireblocks to bring Cardano Native Tokens (CNTs) onto the institutional custody platform. The move represents a significant infrastructure upgrade: tokens minted directly on the Cardano blockchain—rather than through separate smart contracts—will become standard assets on Fireblocks, accessible to the thousands of banks, exchanges, payment firms, and fintechs that rely on the platform for digital asset operations.

    Native Tokens Receive Standard Asset Treatment

    CNTs are distinguished by their on-chain architecture: they are minted alongside Cardano’s native currency, ADA, without requiring a separate contract deployment. The integration covers two key Cardano Improvement Proposals—CIP-26, the Cardano Token Registry, and CIP-68, the on-chain metadata framework. Once support is live, tokens built to either standard will be treated as standard assets on Fireblocks rather than bespoke additions requiring manual configuration. Cardano Foundation chief executive Frederik Gregaard framed the development as an infrastructure play critical for institutional adoption.

    “Institutions rarely adopt a new asset on its own. Adoption happens through trusted infrastructure,” he said. “Bringing Cardano Native Tokens onto Fireblocks puts the assets issued on Cardano in front of the exchanges, payment firms and fintechs that build on that infrastructure every day.”

    A 2027 Rollout Timeline, Not an Immediate Launch

    The announcement outlines a technical roadmap rather than a finished deployment. The Cardano Foundation stated that support is expected by March 2027, with both organizations planning to scope further DeFi and ecosystem integrations over the same year. The notice does not report new token issuance or institutional purchases of ADA. Stephen Richardson, Fireblocks’ chief strategy officer and head of banking, emphasized the dual criteria institutions evaluate before engaging with new assets.

    “the network the asset lives on and the infrastructure they’ll engage with managing that asset.”

    Richardson noted that Cardano has spent a decade building credibility through peer-reviewed research, formal verification, and a governance model institutions can scrutinize, while Fireblocks supplies the security and policy controls that more than 100 banks rely on.

    Extending Cardano’s Institutional Push

    The Fireblocks integration extends a series of institutional-focused moves by the Cardano Foundation. Earlier this year, the nonprofit opened a blockchain lab at the University of Brasília to expand its Latin American footprint and has backed a capital-markets blockchain risk framework aimed at traditional finance. For issuers of stablecoins and tokenized real-world assets on Cardano, standard Fireblocks support removes a practical barrier: those assets can now reach the same institutional rails as ADA instead of waiting for a custodian to add each token individually by hand.

    Why This Matters

    The integration signals a maturation of Cardano’s infrastructure layer for institutional finance. By embedding CNTs directly into Fireblocks’ policy and security framework—used by over 100 banks and securing more than $16 trillion in transaction volume—Cardano removes a longstanding friction point: the need for custodians to manually whitelist each native token. This standardization is particularly consequential for the emerging tokenized real-world asset (RWA) and stablecoin sectors on Cardano, where institutional custody is a prerequisite for scale. The March 2027 target also aligns with broader industry timelines for regulated digital asset infrastructure, suggesting coordination with evolving regulatory frameworks in major jurisdictions.

    Frequently Asked Questions

    When will Cardano Native Tokens be available on Fireblocks?

    The Cardano Foundation stated that support is expected by March 2027. This is a technical roadmap announcement, not an immediate launch.

    Which token standards are covered by the integration?

    The integration covers CIP-26 (Cardano Token Registry) and CIP-68 (on-chain metadata framework). Tokens built to either standard will become standard assets on Fireblocks.

    Does this mean institutions can immediately custody any CNT?

    No. The integration must be built and deployed first. Once live, Fireblocks’ existing institutional clients—including banks, exchanges, payment firms, and fintechs—will be able to custody, send, and receive supported CNTs using the same security and policy controls applied to other digital assets on the platform.

  • Swiss Bank Shields Bitget Institutional Clients as Retail Funds Remain Frozen

    Swiss Bank Shields Bitget Institutional Clients as Retail Funds Remain Frozen

    Key Highlights

    • Bitget confirmed a Sept. 24 wallet breach that transferred approximately $387.5 million in assets to attacker-controlled addresses, affecting hot and warm wallet layers while cold wallets remained secure.
    • Sygnum Bank’s Protect service offers Bitget institutional clients an off-exchange custody route where pledged collateral—including Bitcoin, Ethereum, stablecoins, and U.S. Treasuries—is held in segregated, bankruptcy-remote Swiss accounts, reducing direct exposure to exchange wallets.
    • Withdrawals remain suspended as of Sept. 25; Bitget cites a User Protection Fund holding 5,500 BTC (valued above $464 million at the time of the breach) to cover qualifying losses, with a withdrawal-status update promised by Sept. 26 04:00 UTC.

    The Breach and Immediate Response

    Bitget detected unauthorized transfers at 18:31 UTC on Sept. 24, initially estimating the loss at roughly $351.6 million. A Sept. 25 update raised that figure to approximately $387.5 million after a fuller accounting that included Zcash and TRON transfers; the exchange emphasized the revision did not represent a fresh wave of unauthorized activity. Bitget stated the breach reached portions of its hot and warm wallet layers while cold wallets remained secure. The exchange said it identified and remediated the underlying vulnerability, contained the incident, and engaged Mandiant and SlowMist to assist the investigation.

    Withdrawals were paused immediately, with deposits and trading left operational. Bitget’s notice promised to announce a withdrawal plan or status by Sept. 26 at 04:00 UTC. For ordinary customers, a displayed balance and the ability to trade do not by themselves provide an exit while withdrawals are unavailable.

    Sygnum’s Off-Exchange Custody Alternative

    On the same day as the breach, Sygnum announced that Bitget’s institutional clients could trade against collateral held at the Swiss bank instead of placing that collateral in Bitget’s wallets. Under the Protect service, eligible clients onboard with Sygnum, sign a contractual framework, open a Protect portfolio, and pledge assets—Bitcoin, Ethereum, stablecoins, and U.S. Treasuries are listed as eligible collateral—before receiving exchange margin. Bitget mirrors the balance as trading margin.

    Sygnum describes the collateral as held in segregated accounts off the bank’s balance sheet and bankruptcy remote under Swiss banking law. The arrangement is intended to keep pledged assets outside Bitget’s estate should the exchange face financial distress, and to reduce direct custody exposure to Bitget’s own wallets. The announcement is dated Sept. 24 but does not state when client access became operational, whether the integration preceded or followed the 18:31 UTC breach, how many Bitget clients have onboarded, any Bitget-specific collateral balance, or whether Sygnum-held assets were involved in the incident. Public figures for Protect’s total assets and the trading-volume share of all integrated exchanges do not measure Bitget client uptake.

    User Protection Fund and Recovery Outlook

    For users holding ordinary balances on Bitget, the exchange pointed to its User Protection Fund. In its initial Sept. 24 notice, Bitget said the fund was worth more than $464 million and that the then-estimated $351.6 million incident fell within its coverage. The fund’s public page lists 5,500 BTC and states users may claim for qualifying losses from platform-wide events beyond their own actions or trading behavior, with Bitget reserving the right to assess and investigate claims. The dollar value of the Bitcoin-denominated fund moves with BTC’s price; Bitget’s August report put the fund’s monthly average at $382 million and its month-end value near $432 million on the same 5,500 BTC holding.

    Bitget also said it froze some affected assets through work with industry partners, but its Sept. 25 update did not quantify the frozen or recovered amount. The next measurable tests are a confirmed withdrawal timetable, a firmer loss and recovery accounting, and the terms of any fund disbursement.

    Why This Matters

    The incident highlights a structural tension in crypto custody: even when institutional collateral is segregated off-exchange with a regulated bank like Sygnum, trading still depends on the exchange’s order, margin, and settlement processes. Public materials do not establish that a Protect client can instantly reclaim pledged collateral during an exchange disruption, nor that operational problems could never delay settlement. Conversely, they do not show that any Sygnum client is blocked from its collateral in this incident. The arrangement creates an optional boundary between institutional collateral and Bitget wallet custody—Bitget’s ordinary balances faced exchange-wallet exposure, while Institutional Protect keeps pledged collateral off-exchange with Sygnum. Missing facts include Bitget-specific Protect uptake and the contract terms governing collateral release and settlement when the exchange is under strain.

    Frequently Asked Questions

    How much was stolen in the Bitget breach and which wallets were affected?

    Bitget estimates approximately $387.5 million in assets were transferred to attacker-controlled addresses. The breach reached hot and warm wallet layers; cold wallets were not compromised.

    What is Sygnum Protect and how does it differ from keeping funds on Bitget?

    Sygnum Protect lets eligible institutional clients pledge collateral—such as Bitcoin, Ethereum, stablecoins, and U.S. Treasuries—in segregated, bankruptcy-remote accounts at the Swiss bank. Bitget mirrors that collateral as trading margin, but the assets remain off Bitget’s balance sheet and outside its wallets, reducing direct custody exposure.

    When will Bitget withdrawals resume and are user funds insured?

    Withdrawals remain suspended as of Sept. 25. Bitget promised an update by Sept. 26 04:00 UTC. The exchange cites a User Protection Fund holding 5,500 BTC (valued above $464 million at the time of the breach) to cover qualifying platform-wide losses, subject to claim assessment and investigation.