Market Manipulation. Search

OSC v. Ontario Securities Commission v Blockratize Inc. and Adventure One QSS Inc. (chat group pumps, 2025)

Judgment entered

Machine-extracted, pending human review. The structured fields on this page were parsed automatically from the regulator's own release, linked below. Read the primary document before relying on any figure here, and tell us if something is wrong.

In 2025, the regulator obtained a judgment against Ontario Securities Commission v Blockratize Inc. and Adventure One QSS Inc., alleging conduct this library classifies as chat group pumps. The release does not state a monetary figure that we were able to extract.

The record

Structured fields for this action, as recorded in our case library.
Agency OSC
Release number 2025-8
Date filed 2025-04-01
Date resolved 2025-04-17
Court Capital Markets Tribunal (Ontario)
Status judgment
Asset class crypto
Criminal parallel No
Defendants Ontario Securities Commission v Blockratize Inc. (entity) ; Adventure One QSS Inc. (entity)
Techniques Chat group pumps

What was ordered

Civil penalty
Disgorgement
Prejudgment interest
Total relief
Alleged gain
Penalty as published
C$200k

A dash means the release did not state a figure we could extract, not that the figure is zero. Penalty and disgorgement are stored separately so aggregates across the library do not double-count the same dollars. This regulator states penalties in CAD. The figure is recorded as published and is not converted, so it does not appear in the USD totals or medians used elsewhere on this site.

What is alleged to have happened

the regulator announced this matter on April 1, 2025 as release 2025-8. The respondents named are Ontario Securities Commission v Blockratize Inc. and Adventure One QSS Inc. (0 individuals, 2 entities). The action was brought in the Capital Markets Tribunal (Ontario).

This library tags the matter as chat group pumps, based on the conduct the regulator describes. Each tag links to a page explaining how that technique works, what statute it engages, and what penalties comparable actions have attracted. The tagging is ours, not the regulator's: agencies charge statutory provisions, not technique names.

The conduct is recorded against crypto.

For the regulator's own account of the facts, read the primary document linked above. This page deliberately summarises the structured record rather than reproducing the release.

What technique is this, and how does it work?

This action is tagged with one technique in our taxonomy. The tagging is ours: regulators charge statutory provisions, not technique names, so the mapping is an editorial judgement described in our editorial policy.

Timeline

  1. 2025-03-31 Document
  2. 2025-03-31 Settlement Agreement
  3. 2025-04-01 Notice of Hearing
  4. 2025-04-17 Reasons and Decision
  5. 2025-04-17 Reasons and Decision

Primary documents

Everything on this page derives from the documents below. Where our summary and the primary document disagree, the primary document is right.

The linked release is published by the issuing regulator under its own terms. Our summary and narrative above are our own writing.

Other actions in the library sharing at least one technique tag with this one.

Action Agency Filed Technique Penalty Status
SEC v. NanoBit Limited, et al. (chat group pumps, 2026) SEC 2026-06-29 Chat Group Pumps $1.2m judgment
Market riggers sentenced in ASX ‘pump and dump’ case (ASIC, 2025) ASIC 2025-12-22 Chat Group Pumps , Pump And Dump unknown
FCA v. Jean-Noël Yves Alba (chat group pumps, 2025) FCA 2025-07-22 Chat Group Pumps unknown
ASIC secures guilty pleas in Telegram ‘pump and dump’ action (2025) ASIC 2025-06-10 Chat Group Pumps , Pump And Dump unknown
SEC v. NanoBit Limited, Radiant Horizons Limited, Sweet Karma Fashion Inc., Zhao Tropical Deli Inc., Jiajie Liu, Fei Liao, and Hua Zhao (chat group pumps, 2024) SEC 2024-09-17 Chat Group Pumps filed
SEC v. Flyfish Club, LLC (chat group pumps, 2024) SEC 2024-09-16 Chat Group Pumps , Unregistered Distributions $750k settled

Record added September 9, 2026. submit a correction.