A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_URI::$config is deprecated

Filename: core/URI.php

Line Number: 101

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Router::$uri is deprecated

Filename: core/Router.php

Line Number: 127

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$benchmark is deprecated

Filename: core/Controller.php

Line Number: 82

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$hooks is deprecated

Filename: core/Controller.php

Line Number: 82

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$config is deprecated

Filename: core/Controller.php

Line Number: 82

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$log is deprecated

Filename: core/Controller.php

Line Number: 82

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$utf8 is deprecated

Filename: core/Controller.php

Line Number: 82

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$uri is deprecated

Filename: core/Controller.php

Line Number: 82

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$exceptions is deprecated

Filename: core/Controller.php

Line Number: 82

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$router is deprecated

Filename: core/Controller.php

Line Number: 82

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$output is deprecated

Filename: core/Controller.php

Line Number: 82

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$security is deprecated

Filename: core/Controller.php

Line Number: 82

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$input is deprecated

Filename: core/Controller.php

Line Number: 82

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$lang is deprecated

Filename: core/Controller.php

Line Number: 82

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$db is deprecated

Filename: core/Loader.php

Line Number: 396

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_DB_mysqli_driver::$failover is deprecated

Filename: database/DB_driver.php

Line Number: 371

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 132

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 294

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 168

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 237

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 317

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_files_driver.php

Line Number: 358

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$session is deprecated

Filename: core/Loader.php

Line Number: 1283

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$data is deprecated

Filename: core/MY_Controller.php

Line Number: 17

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Cache::$dummy is deprecated

Filename: libraries/Driver.php

Line Number: 188

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$cache is deprecated

Filename: core/Loader.php

Line Number: 1283

A PHP Error was encountered

Severity: 8192

Message: mysqli::real_escape_string(): Passing null to parameter #1 ($string) of type string is deprecated

Filename: mysqli/mysqli_driver.php

Line Number: 392

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$m_db is deprecated

Filename: core/Loader.php

Line Number: 358

A PHP Error was encountered

Severity: 8192

Message: mysqli::real_escape_string(): Passing null to parameter #1 ($string) of type string is deprecated

Filename: mysqli/mysqli_driver.php

Line Number: 392

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$form_validation is deprecated

Filename: core/Loader.php

Line Number: 1283

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property Blog::$agent is deprecated

Filename: core/Loader.php

Line Number: 1283

A PHP Error was encountered

Severity: 8192

Message: mysqli::real_escape_string(): Passing null to parameter #1 ($string) of type string is deprecated

Filename: mysqli/mysqli_driver.php

Line Number: 392

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$load is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$benchmark is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$hooks is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$config is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$log is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$utf8 is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$uri is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$exceptions is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$router is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$output is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$security is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$input is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$lang is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$db is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$session is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$data is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$cache is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$m_db is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$form_validation is deprecated

Filename: core/Loader.php

Line Number: 931

A PHP Error was encountered

Severity: 8192

Message: Creation of dynamic property CI_Loader::$agent is deprecated

Filename: core/Loader.php

Line Number: 931

Polyhedra’s ZKJ token collapses following ‘abnormal on-chain activity’ - Money
Pawns.app

Polyhedra’s ZKJ token collapses following ‘abnormal on-chain activity’

  • The Polyhedra Network (ZKJ) token has plunged 91% after abnormal on-chain activity.
  • Binance has blamed whale exits and a liquidation cascade for the token crash.
  • The upcoming June 19 token unlock may trigger further price drops.

The cryptocurrency market has once again been rocked by a dramatic price collapse, this time involving Polyhedra Network’s native token, ZKJ.

The ZKJ token has suffered an unprecedented decline of over 91% in less than 24 hours, sending shockwaves across exchanges and drawing scrutiny from regulators, investors, and analysts alike.

ZKJ, which had been trading steadily around $2.00 for over a month, crashed to a record low of $0.2676 on June 15, 2025, wiping out nearly $500 million in market capitalisation.

ZKJ token crash

This price crash has raised serious concerns over liquidity risks, tokenomics structure, and the influence of large holders in decentralised finance.

What caused the sudden Polyhedra Network (ZKJ) price collapse?

The ZKJ price collapse began early on June 15 when Polyhedra Network posted on X (formerly Twitter) that a wave of “abnormal on-chain transactions” had struck the ZKJ/KOGE trading pair.

Within hours, the token’s price plummeted by more than 83%, as market participants scrambled to understand what had triggered the meltdown.

Binance later weighed in, attributing the collapse to a liquidity crisis stemming from large-scale withdrawals involving KOGE, a token closely paired with ZKJ.

According to the exchange, these withdrawals created a “liquidation cascade” as major wallets began offloading their holdings.

As KOGE’s USDT pool was drained, traders moved their assets into the ZKJ/USDT pool, which quickly became overloaded.

This sudden shift overwhelmed the system, accelerating the sell-off and deepening the decline in ZKJ’s value.

Massive withdrawals and whale activity

Blockchain data has revealed several wallets that had been actively farming Alpha Points before the crash.

One wallet alone withdrew more than $3.7 million in KOGE and $530,000 in ZKJ.

Two other wallets combined pulled out nearly $5 million, further intensifying the downward spiral.

These actions suggest the involvement of large holders, commonly known as whales, whose exits likely triggered cascading liquidations across leveraged positions.

As prices tumbled, margin calls were activated, leading to forced liquidations that compounded the selling pressure.

Although some community members have speculated about foul play, no leading blockchain analytics platform has verified such claims.

Polyhedra, for its part, insists it is conducting a thorough review and maintains that its core technology remains unaffected.

Binance has altered its Alpha Points rules for ZKJ and KOGE

In response to the unfolding situation, Binance announced a major change to its Alpha Points rewards program.

Starting June 17, trades between Alpha tokens, including ZKJ and KOGE, will no longer count toward Alpha Points calculations.

This policy shift is aimed at reducing systemic risk and discouraging concentrated trading behaviors that can lead to abrupt market failures.

Binance’s decision is being viewed as a proactive step to restore market integrity and reduce manipulation.

Upcoming token unlock adds to the bearish pressure

Further adding to investor anxiety is the imminent unlock of 15.5 million ZKJ tokens scheduled for June 19.

Valued at approximately $10 million, this unlock could flood the market with fresh supply at a time when confidence is already severely shaken.

Given that this represents more than 5% of the current circulating supply, market analysts warn that another sharp drop could occur if holders rush to sell upon unlocking.

The timing could not be worse for a token already reeling from its steep fall.

The post Polyhedra’s ZKJ token collapses following ‘abnormal on-chain activity’ appeared first on CoinJournal.