Sygnum extends bank-backed trading collateral to institutional accounts, whereas a sudden withdrawal freeze enforced by Bitget leaves standard customer funds heavily reliant on internal exchange safeguards.
Following a September 24 wallet breach, Bitget reported that roughly $387.5 million in digital assets moved toward hacker-controlled addresses. While deposits and trading stayed active, the platform kept withdrawals frozen through statements released on September 25.
During the breach, Sygnum publicized that corporate Bitget users could execute trades using collateral stored securely at the Swiss bank rather than depositing those assets directly into Bitget wallets.
This contrast challenges the guarantee of off-exchange custody. It forces observers to question which holdings remain safe from platform hacks, and what elements still rely on the exchange during trade halts or withdrawal freezes.
Sygnum’s pathway serves qualified corporate traders who register directly with the Swiss lender. Both firms omitted details regarding how many Bitget users leverage this service, nor did they clarify if any bank-secured collateral was linked to the recent exploit.
A Breach Emerges Alongside a New Custody Route
Bitget announced that its security systems identified unauthorized transfers at 18:31 UTC on September 24. Initial bulletins estimated the impacted capital at roughly $351.6 million, noting that the breach affected specific hot and warm storage tiers while cold reserves stayed secure.
During a September 25 update, Bitget increased its estimated stolen funds to approximately $387.5 million following a comprehensive ledger audit that incorporated Zcash and TRON transactions. Management clarified that this adjustment stemmed from recalculations rather than a secondary breach wave.
Bitget stated that internal teams isolated and fixed the root vulnerability to secure the platform. According to the exchange, security firms Mandiant and SlowMist were aiding the ongoing forensic probe.
Bitget announced via bulletin that payouts were temporarily disabled while funding and market operations continued normally. Leadership pledged to publish a payout recovery schedule or status report by September 26 at 04:00 UTC.
For a standard Bitget user, a visible portfolio value alongside active market access fails to guarantee an exit path while withdrawal capabilities remain suspended.
Sygnum noted that corporate Bitget traders can leverage its Protect offering for spot and derivatives markets, provided that pledged margin assets are kept under Swiss bank custody. Bitget then mirrors this capital as trading collateral.
Bitcoin, Ethereum, stablecoins, and United States Treasuries are accepted by the financial institution as eligible collateral. Under the published procedure, clients are required by Sygnum to complete onboarding, sign a legal framework, open a Protect portfolio, and pledge assets before trading margin is granted.
Sygnum outlines that pledged assets are kept inside isolated, off-balance-sheet accounts that are protected by Swiss banking legislation against insolvency. Storing collateral within the financial institution lowers direct exposure to security risks tied to Bitget wallets.
This structure also addresses fears that pledged reserves would stay outside the corporate estate if a platform experiences insolvency. These mechanisms define the framework as outlined by Sygnum.
Dated September 24, the announcement omits when corporate access became active. Furthermore, it avoids clarifying whether the integration preceded the 18:31 UTC exploit or emerged afterward. The release also fails to identify any onboarded Bitget users, specify platform-related collateral totals, or state if bank-secured assets were compromised during the breach.
The Limits of Custody and a Separate Backstop
Metrics published within the release regarding overall Protect reserves and total trading volume across linked exchanges fail to reflect actual Bitget user adoption rates.
The public Protect page promotes adaptable collateral deposits and withdrawals. However, the platform omits the specialized Bitget agreement that dictates when pledged assets can be freed, how positions are settled, or what occurs to margin capital when Bitget freezes its payout services.
A mirrored trading balance maintained at a platform differs fundamentally from standard customer funds that can be withdrawn at will.
Market execution relies entirely on platform matching engines, margin calculations, and settlement infrastructure even though pledged assets are stored externally. According to Sygnum, segregated custody can minimize vulnerabilities tied to Bitget wallet breaches and corporate insolvency.
Public disclosures fail to confirm that a Protect user can instantly recover pledged assets during a platform outage, nor do they guarantee that operational hiccups would never delay settlement processes. Simultaneously, the documents do not indicate that any Sygnum customer faces restricted access to collateral during the current incident.
This structure establishes an optional barrier separating institutional reserves from Bitget wallet storage.
For account holders with funds stored on Bitget, management directed attention toward its internal User Protection Fund. Within its preliminary September 24 bulletin, Bitget asserted that this reserve pool exceeded $464 million, ensuring that the estimated $351.6 million exploit fell comfortably inside its coverage capacity.
The public fund portal catalogs 5,500 BTC, stating that users may file claims for qualifying losses stemming from systemic events beyond individual control or trading activity. Furthermore, Bitget retains full authority to evaluate and investigate all submitted claims.
The fiat value of a Bitcoin-backed reserve fluctuates alongside market pricing. Bitget’s August report placed the monthly average of the fund at $382 million, while closing the period near $432 million using the identical 5,500 BTC holding.
Bitget additionally reported that management froze portions of the compromised funds through cooperation with industry partners, though its September 25 update omitted figures for the secured or recovered sums. Upcoming milestones include a definitive withdrawal timeline, precise loss and recovery calculations, and the criteria governing any reserve payouts.
Regarding the custody comparison, missing details include specific Bitget adoption rates for Protect and the governing contract clauses that dictate collateral release and trade settlement while the platform experiences distress.
