Woofun AI reports that HTX executive Molly issued a formal denial on August 20, asserting that internal reviews found no evidence of official HTX accounts participating in the address-poisoning transfers central to the ongoing dispute with Kraken. The statement explicitly distances Huobi Global SA from the alleged illicit activity, attributing the transactions instead to independent user actions following the restriction of their funds on the competing exchange. This position serves as a direct rebuttal to earlier reports suggesting platform-level complicity, yet it simultaneously highlights the structural ambiguity inherent in cross-chain compliance investigations where wallet control and user agency are often conflated.

The timeline of events reveals a critical divergence in investigative scope between the two entities. Molly's disclosure on August 20 relied on an internal review that specifically targeted official HTX accounts, concluding that none were involved in the cited transfers.

However, this narrow focus fails to address the broader ecosystem of user-controlled wallets that may have interacted with the same addresses. By limiting the inquiry to exchange-controlled infrastructure, HTX effectively sidesteps the question of whether its users acted independently or were facilitated by platform mechanisms. The distinction between an exchange's official wallet and a customer's personal wallet is legally and technically significant, yet the public record provided by HTX does not clarify how this separation was maintained or verified during the review process.

A more critical variable is the lack of granular data regarding the specific wallets examined and their transaction histories. While HTX claims to have separated exchange-controlled addresses from those belonging to its users, no public ledger data or hash references were released to substantiate this claim. The absence of disclosed transaction history means that external auditors cannot independently verify whether the funds in question originated from HTX's hot or cold wallets or from user-initiated transfers. This opacity creates a verification gap where the assertion of non-involvement remains unproven by on-chain evidence. Without a transparent list of examined wallets and their corresponding transaction routes, the conclusion that official accounts were not involved rests entirely on HTX's internal assertions rather than immutable blockchain data.

From Kraken's compliance perspective, the issue is framed differently, focusing on deposit exposure rather than source origin. A screenshot included in later updates appeared to show a Kraken Support notice stating that a specific deposit had exposure to Huobi Global SA, warning that transactions involving sanctioned entities can lead to account restrictions. This notice illustrates why the two parties may be addressing different facets of the same case: HTX asks whether its official wallets sent the funds, while Kraken reviews whether a customer's deposit can be linked to a particular entity or address cluster. The screenshot, while illustrative, cannot independently authenticate the email or establish Kraken's full position, but it underscores the complexity of compliance checks where indirect exposure can trigger restrictions regardless of direct platform involvement.

Woofun AI data shows that the financial stakes in this dispute remain largely unverified, particularly regarding the $4.2 million figure cited by Molly. This amount was described as the highest known sum associated with restricted funds, yet the post failed to publish the number of affected users, supporting account records, or a detailed list of balances. Consequently, the $4.2 million should be interpreted as HTX's description of a single reported individual case rather than evidence of aggregate frozen assets. There is no proof that Kraken froze this total amount across all accounts, nor that the funds were directly connected to the alleged address-poisoning transfers. The lack of comprehensive data limits the ability to assess the true scale of the impact on HTX users.

Partial resolution emerged hours later when Molly announced that several affected Kraken users had their accounts unfrozen, supported by a private-chat screenshot showing a user confirming restored access. While this represents a meaningful change for the individual cases described by HTX, it does not establish a platform-wide reversal of Kraken's compliance stance. The post does not specify how many accounts were released, the duration of their restrictions, whether any assets remained unavailable, or the rationale behind Kraken's decision to lift the restrictions. The inclusion of a private-chat screenshot provides anecdotal evidence of recovery but lacks the transparency required to confirm a systematic change in policy or a broad-based resolution to the dispute.

The public record currently supports only a limited conclusion: an HTX executive has denied official-account involvement, and some users have regained access at Kraken. It does not yet reveal who controlled the disputed wallets, why each account was reviewed, or whether the reported cases were interconnected. The remaining questions regarding wallet ownership and compliance methodology persist, leaving the core dispute unresolved. This marks a recurring pattern in cross-exchange compliance conflicts where partial disclosures and anecdotal evidence fail to provide a comprehensive understanding of the underlying technical and regulatory dynamics.