Kraken begins automatically liquidating remaining balances associated with two post-incident token migrations on September 28.
The affected Kraken tickers are:
- H — legacy Humanity token;
- HUMANITY — replacement Humanity token on Kraken;
- BDX — legacy Beldex token;
- BELDEX — replacement Beldex token on Kraken.
Withdrawals for all four closed on:
September 25, 2026 at 14:00 UTC
Remaining balances now enter a platform-controlled liquidation period from:
September 28 through October 2, 2026
Why these are migration balances
Both token pairs arose from earlier security/contract incidents.
Humanity
The Humanity team deployed a replacement token after the legacy H incident.
Kraken:
- kept legacy H under ticker H;
- used HUMANITY for the new token so users could distinguish the contracts;
- credited eligible snapshot holders 1:1.
The snapshot was:
June 8, 2026 at 17:25 UTC
The HUMANITY airdrop was scheduled for:
July 1, 2026 at 14:00 UTC
Beldex
Beldex deployed a replacement token after the incident affecting legacy BDX.
Kraken:
- kept legacy token under BDX;
- used BELDEX for the replacement token;
- credited eligible snapshot holders 1:1.
The BDX snapshot was:
June 10, 2026 at 23:36 UTC
The BELDEX airdrop occurred:
July 10, 2026 at 14:00 UTC
The withdrawal decision is already over
Before September 25, users who wanted to keep the actual tokens could withdraw.
That window has closed.
The risk today is therefore not “should I withdraw before liquidation？”
It is:
How will Kraken execute the residual balance when the user no longer controls timing or venue？
Kraken warns proceeds may be minimal or zero
Krakens Beldex notice is unusually explicit.
It says:
- liquidation prices may be significantly below recent reference prices;
- limited liquidity may result in minimal proceeds;
- in some conditions, proceeds may effectively be zero;
- the denomination of liquidation proceeds depends on market conditions and cannot be confirmed in advance.
The same liquidity risk is repeated in the Humanity guidance.
Why migration tokens can be especially illiquid
A replacement-token migration often fragments liquidity:
- old contract may still trade somewhere;
- new contract may have different exchange support;
- ticker symbols can be confusing;
- some holders qualify for airdrops and others do not;
- market makers may stop supporting the old asset;
- CEX deposits/trading can be disabled long before withdrawals close.
Kraken already disabled trading and deposits for these balances.
The exchange is therefore liquidating into whatever external liquidity is available rather than through a normal Kraken order book.
BDX post-snapshot holders have an additional problem
Kraken says users who acquired legacy BDX after the June 10 snapshot were not eligible for the BELDEX airdrop.
Its notice states that there is no claims portal or other recourse for those post-snapshot Kraken buyers through the exchange.
That means liquidation of legacy BDX can occur without the holder having received the replacement token.
Humanity post-snapshot holders have a different claims path
For Humanity, Kraken says H acquired after the snapshot was not eligible for Krakens HUMANITY airdrop.
However, the Humanity team provided its own claims portal for some cases.
Kraken is not involved in that claim process.
This distinction is important:
- Beldex post-snapshot Kraken acquisition: no Kraken claims portal/recourse stated;
- Humanity post-snapshot acquisition: project-side claims process exists, outside Kraken.
Contract confusion risk
Kraken deliberately uses different account tickers because replacement tokens can still display old tickers on-chain.
A user or support operator can therefore confuse:
- old contract;
- new contract;
- exchange ticker.
During forced liquidation, users should rely on transaction/account records and contract addresses, not ticker text alone.
No guaranteed execution currency
Kraken says the currency in which liquidation proceeds are credited cannot be confirmed beforehand.
That prevents WikiBit from stating that users will necessarily receive:
- USD;
- EUR;
- USDT;
- another specific quote asset.
User-control boundary
This event is different from a normal market sell.
A user no longer controls:
- timing;
- execution venue;
- order type;
- minimum price;
- settlement currency.
That is why WikiBit rates it High even though it is an announced delisting rather than a security breach.
Entity boundary
The liquidation is a Kraken asset-support decision.
It does not mean:
- Humanity Protocol is shutting down;
- Beldex is shutting down;
- the replacement contracts are being newly hacked today.
The security incidents explain why migrations occurred, but September 28 is an exchange execution event.
Evidence Status
Confirmed / Official Kraken
- H/HUMANITY withdrawals closed Sep. 25 14:00 UTC.
- BDX/BELDEX withdrawals closed Sep. 25 14:00 UTC.
- Automatic liquidation Sep. 28–Oct. 2.
- Trading/deposits disabled.
- Low liquidity can cause prices far below reference.
- Minimal/no proceeds are possible.
- Proceeds currency cannot be known in advance.
Migration-Specific Confirmed
- Humanity snapshot Jun. 8 17:25 UTC; 1:1 replacement.
- Beldex snapshot Jun. 10 23:36 UTC; 1:1 replacement.
- Kraken uses HUMANITY/BELDEX tickers to distinguish replacements.
Developing
- Actual liquidation prices.
- Total balances liquidated.
- Settlement currency.
- Whether users encounter support disputes.
- Market impact on external venues.
Risk Assessment
High forced-execution risk.
The withdrawal window has already closed. The remaining risk is illiquid, exchange-controlled execution with no guaranteed minimum outcome.
What to Watch Next
First liquidations, realized prices, settlement currency, external-market liquidity, Kraken support cases and any project-side recovery options.
FAQ
Which Kraken assets enter liquidation？
H, HUMANITY, BDX and BELDEX.
When does liquidation happen？
September 28 through October 2, 2026.
Can users still withdraw these balances？
The published withdrawal deadline was September 25 at 14:00 UTC.
Is there a guaranteed liquidation price？
No.
Could proceeds be zero？
Kraken warns limited liquidity can result in minimal or no proceeds.
Are Humanity and Beldex being hacked again？
No. This liquidation is a Kraken delisting/migration consequence, not a newly confirmed exploit.