Will Cloud9 make a roster change before Septemeber?

This market will resolve to "Yes" if any player joins or leaves Cloud9's main VALORANT roster (defined as the players listed with "Active" status in the roster table on Cloud9's Liquipedia page: https://liquipedia.net/valorant/Cloud9) by August 31, 11:59pm ET, 2026. Otherwise, this market will resolve to "No". As of market creation the active starter roster consists of the following five players: OXY, Zellsis, Jackk, Notexxd, FireBallOps. Name changes or aliases referring to the same player do not qualify as roster changes. Roster change refers to any official signing, transfer, benching to inactive/reserve, release, retirement, or departure of a player from the active starting lineup. This includes adding new players (transfers, free agent signings, or loans), removing players (to bench/inactive, free agency, or other teams), or any change resulting in a different active roster. Coach and staff changes, and temporary stand-ins/substitutes will not count. A player appearing in the active lineup for matches or events solely as a designated substitute or stand-in for a single event does not count toward a roster change. To qualify, a roster change must be officially confirmed by Cloud9 or the player involved; leaks, rumors, or unconfirmed reporting do not count until officially confirmed. A qualifying roster change must occur on or before the deadline, and be reflected in the resolution source. Once the change appears in the resolution source, it must remain live for at least 48 continuous hours to be valid. This 48-hour period may finish after the deadline, so long as the change itself occurred on or before the deadline. If the change is reverted or removed before 48 hours have elapsed, the window resets and will not count toward resolution. The primary resolution source for this market will be Liquipedia (https://liquipedia.net/valorant/Cloud9), however, a consensus of credible reporting may also be used.

• Resolver: official source.
• Deadline: closing date in UTC.
• Disputed outcomes: handled by moderators within 48 hours.