Skip to main content
AVOID.NET

v2 → v3

Scores

trust_score20 → 22
severity_base— → —
score_modifier-8 → -8

Sections

Case Overview and Procedural History

unchanged

Named Defendants and Plaintiffs → Parties and Class Definition

unchanged

RICO Allegations and Predicate Acts → RICO, Securities and Consumer-Protection Allegations

unchanged

MEV Mechanism at the Center of the Claims → MEV and Jito Labs Allegations

unchanged

Role of Each Defendant → Alleged Roles within the Enterprise

unchanged

Whistleblower Evidence and Internal Communications → Whistleblower Evidence: Alleged Internal Chat Logs

unchanged

Defendants' Responses and Legal Strategy → Platform Revenue, Alleged Retail Losses and Independent Data

unchanged

Legal Merits and Expert Commentary → Defendants' Responses and Defence Arguments

unchanged

Broader MEV Litigation Landscape → Alleged Misconduct Toward Plaintiffs' Counsel

unchanged

Market and Ecosystem Impact → Unverified Rumor: Co-founder Detention in Brazil

unchanged

(section 11) → Legal Merits, Commentary and the Broader MEV Litigation Landscape

unchanged

(section 12) → Market and Ecosystem Impact

unchanged

Timeline events

+ added2024-01 — (no description)
+ added2025-01-16 — (no description)
+ added2025-04 — (no description)
+ added2025-05 — (no description)
+ added2025-05-07 — (no description)
+ added2025-08-07 — (no description)
+ added2025-12 — (no description)
+ added2025-12-17 — (no description)
+ added2026-01-13 — (no description)
+ added2026-01-27 — (no description)
~ changed2024-03: “” → “”
~ changed2025-01-30: “” → “”
~ changed2025-02: “” → “”
~ changed2025-07-22: “” → “”
~ changed2025-07-23: “” → “”
~ changed2025-09: “” → “”
~ changed2025-09-05: “” → “”
~ changed2025-09-26: “” → “”
~ changed2025-09-30: “” → “”
~ changed2025-10-15: “” → “”
~ changed2025-12-09: “” → “”
~ changed2026-01-07: “” → “”
~ changed2026-01-23: “” → “”
~ changed2026-02-13: “” → “”
~ changed2026-02-20: “” → “”

Accepted submissions

No changes to accepted submissions.

Each version is bound to the decision event that created it. Verify the chain anchor for either via the audit log.

v2 hash: b66cc065921e6a835dd3cfe19f55dcbfbc16ca3147c0ff1b2afc5cf24933dd4a
v3 hash: 52d1526d09014570b20c35770edca01522854617bd746e694819788bc603d5d1