Market insiders question precedent as project defends move as “user protection”

World Liberty Financial (WLFI) has come under fire after freezing hundreds of wallets, including one belonging to Tron founder Justin Sun. The project insists the move was designed to protect users from phishing-related compromises, not to silence market participants. Still, the decision has stirred concern across the crypto industry: if they can freeze Sun’s wallet, who might be next?


WLFI’s Defense: Protecting Users, Not Blocking Traders

WLFI stated on X (formerly Twitter) that it only intervenes to protect its community:

“WLFI only intervenes to protect users, never to silence normal activity.”

According to the project, 272 wallets were blacklisted this week. Of these:

  • 215 wallets were linked to phishing attacks.
  • 150 wallets were compromised through support channels.

Justin Sun’s wallet was included in this freeze, even though his transfers did not align with WLFI’s token crash.


Onchain Data Clears Sun of Market Manipulation

At first glance, Sun’s outbound transactions created speculation that he was selling WLFI tokens during the downturn. But blockchain analytics from Nansen tell a different story:

  • Sun transferred 50 million WLFI ($9.2M) on Sept. 4 at 09:18 UTC.
  • This was hours after WLFI’s sharpest price drop, meaning the transfers followed the crash rather than triggered it.

Additional Nansen data showed a $12M WLFI transfer from HTX to Binance by a third-party market maker. However, with WLFI’s $700M+ daily trading volume, this move was too small to move the market on its own.


What Really Drove WLFI’s Decline?

Insiders and trading desks point instead to broad shorting and dumping activity across exchanges as the primary driver of WLFI’s sharp fall.

  • A BitGo-to-Flowdesk transfer, flagged by Nansen, coincided with the start of the downturn.
  • Market participants say this aligns more closely with WLFI’s slide than any activity linked to Justin Sun.

Simply put: the crash was fueled by leveraged selling pressure, not by one investor’s transfers.


Industry Concerns: Precedent and Power

While WLFI’s explanation focuses on security against phishing, the freezing of high-profile wallets has unnerved traders, whales, and market makers. Many are now asking:

  • Could legitimate traders find their funds frozen if WLFI deems it “suspicious”?
  • What precedent does this set for decentralized projects exercising centralized control?

As one insider put it: “If they can do it to Sun, who’s next?”

WLFI’s wallet freezes highlight the tension between security and decentralization. While phishing protections are important, freezing wallets belonging to major investors has raised doubts about fairness and transparency. With shorting and dumping identified as the real culprits behind WLFI’s crash, the debate now shifts to governance: who gets to decide when wallets are frozen, and how far can this power go?

Disclaimer

This content is for informational purposes only and does not constitute financial, investment, or legal advice. Cryptocurrency trading involves risk and may result in financial loss.

Buy Crypto
You will be redirected to BloFin
logo_blockto.io

Blockto.io

info@blockto.io

Address: Overvliet 21, 3545NG, Utrecht

Blockto.io Copyright © 2026, All rights reserved

News
Rates
Buy
Events
We use cookies to personalize content and ads, provide social media features, and analyze our traffic. In accordance with GDPR/AVG and EU cookie regulations, data is processed only with your consent. We may share information about your use of our website with our social media, advertising, and analytics partners, and you can manage or withdraw your consent at any time. View more
Cookies settings
Accept
Privacy & Cookie policy
Privacy & Cookies policy
Cookie name Active

Privacy Policy

At BitxJournal.com, we respect your privacy and are committed to protecting your personal data. This Privacy Policy explains how we collect, process, store, and protect personal information in accordance with the General Data Protection Regulation (GDPR) and AVG (EU privacy legislation).

1. Data Controller

BitxJournal.com acts as the data controller for all personal data processed through this website.

2. Personal Data We Collect

We may collect and process the following categories of data:

Personal Data

  • Name and email address (when you subscribe to newsletters or contact us)

Technical & Usage Data

  • IP address, browser type, operating system

  • Device information

  • Pages visited, referral sources, and interaction data

This data is collected via cookies, log files, and analytics technologies.

3. Legal Basis for Processing

We process personal data only when a lawful basis exists, including:

  • Consent – when you explicitly agree (e.g., cookies, newsletter sign-up)

  • Legitimate interest – to operate, secure, and improve our website

  • Legal obligation – when required by applicable laws

You may withdraw your consent at any time.

4. Purpose of Data Processing

Your data is processed for the following purposes:

  • Operating and maintaining the website

  • Improving content, usability, and performance

  • Sending newsletters or updates (only with consent)

  • Analyzing traffic and user behavior

  • Responding to inquiries or support requests

5. Cookies & Consent Management

We use cookies and similar technologies in compliance with EU Cookie Law.

  • Non-essential cookies are placed only after explicit user consent

  • Users may accept, reject, or manage cookie preferences at any time

  • Consent can be withdrawn without affecting prior lawful processing

Detailed cookie information is available in our Cookie Settings panel.

6. Third-Party Data Processing

We may share limited data with trusted third-party service providers, including:

  • Analytics providers (e.g., Google Analytics)

  • Advertising partners (for personalized or non-personalized ads)

These third parties act as data processors and process data only under contractual obligations compliant with GDPR/AVG.

7. International Data Transfers

Where data is transferred outside the European Economic Area (EEA), we ensure appropriate safeguards are in place, such as Standard Contractual Clauses (SCCs) or equivalent legal mechanisms.

8. Data Retention

We retain personal data only for as long as necessary to fulfill the purposes outlined in this policy or as required by law.

9. Data Security

We implement appropriate technical and organizational security measures to protect personal data against unauthorized access, alteration, disclosure, or destruction.

10. Your GDPR Rights

Under GDPR/AVG, you have the right to:

  • Access your personal data

  • Rectify inaccurate or incomplete data

  • Request data erasure (“right to be forgotten”)

  • Restrict or object to processing

  • Data portability

  • Withdraw consent at any time

  • Lodge a complaint with a supervisory authority

11. Changes to This Privacy Policy

We reserve the right to update this Privacy Policy at any time. Any changes will be posted on this page with a revised effective date.

12. Contact Information

For privacy-related inquiries or GDPR requests, contact:

📧 Email: support@blockto.io
🌐 Website: https://blockto.io

Save settings
Cookies settings