The Circuit Just Got Three Layers Deep
The 2026 RLCS season started on November 14, 2025, and will end on September 20, 2026. That is a ten-month window. Inside it, RLCS 2026 is the fifteenth season of the Rocket League Championship Series, and it introduces new features including the inaugural Kick-Off Weekend and the integration of 2v2, extending the league to three competitive game modes. Three competitive game modes. That is not a minor formatting change. It is a structural multiplication of the administrative surface area.
Many of the key additions from 2025 will remain in place: two online splits, two Majors, the continuation of 1v1 competition, and an expanded Rocket League World Championship featuring 20 teams. The total prize pool for the 2026 season is $6.1 million, spread across different competitions and different game formats. Following last season’s addition of 1v1s to the competitive circuit, RLCS 2026 will feature 2v2s as a third competitive game mode. RLCS 2v2s will have their own Opens and be featured at LANs just as 1v1s were throughout RLCS 2025. The calendar structure follows suit: the season is structured around six open events and four Major LAN events. The Kick-Off LAN was a new addition, a season-opener event that took place at BLAST Studios in Copenhagen, Denmark, from December 5 to 7, 2025, helping determine qualification for Major 1 and regional slots. Major 1 landed in Boston at Agganis Arena in February, and the second Major of the season took place in Paris at La Défense Arena from May 20 to 24, 2026. The season culminates at the World Championship. The RLCS 2026 World Championship has been extended to a six-day event and will feature the 16 teams with the most RLCS Points plus 4 teams from the Last Chance Qualifiers, marking the biggest tournament in Rocket League esports. It begins with the Play-In, where the teams seeded 13 through 20 compete in an eight-team double-elimination bracket, with the top four advancing to the Group Stage. The 2v2 World Championship will take place from September 15 to 20, 2026, featuring four teams competing over a total prize pool of $170,000 USD.
The roster rules are where the administrative weight becomes significant. As teams headed into the new season, they needed to take note of important updates to roster eligibility. All rosters must field a majority of players who are residents or citizens of the region they are competing in. For standard 3-player rosters, at least two players must meet regional eligibility requirements through citizenship or permanent legal residency. Teams that choose to register a substitute (4-player roster) will need to ensure that three of the four players meet regional eligibility requirements. There are seven participating regions: Europe, North America, South America, Oceania, Middle East and North Africa, Asia-Pacific, and Sub-Saharan Africa. That means seven separate eligibility frameworks, each with its own country list, each with its own citizenship and residency standards, all requiring verification before a player can appear in a regional open. In practice, organizations like FUT Esports signed entirely North American starting rosters following the new RLCS rule, which states that the majority of players on a team must meet regional eligibility requirements through citizenship or permanent legal residency. The rule reshaped off-season roster construction across the entire circuit. Someone is checking all of this. That someone is BLAST administrators, working off-chain, manually.
No .rocketleague Onchain. Nothing Close.
There is no registered onchain TLD for .rocketleague. A search of the active Web3 naming landscape — across Freename, ENS ecosystem registries, and Handshake-based name systems — returns nothing registered, nothing claimed, nothing deployed under the .rocketleague namespace. Web3 TLDs are powered by blockchain name systems including Handshake, Ethereum Name Service, and other decentralized naming protocols, with domain records kept on-chain, making them transferable and tamper-evident. Psyonix and Epic Games, the entities behind the Rocket League intellectual property, have not staked a position in any of these systems. Neither has BLAST, the tournament operator running the circuit’s day-to-day administration. The .rocketleague namespace — the most direct brand-native TLD for a competitive circuit of this scale — sits unclaimed.
This is not unusual in esports. Most major circuits have not connected their competitive infrastructure to onchain identity systems at all. The Web3 crossover that has happened in the Rocket League orbit has been peripheral: fan activations, NFT merchandise, and partnership announcements, not credential infrastructure. XBorg, the gaming protocol and sister company to SwissBorg, announced a partnership with Team BDS aimed at creating an esports project combining gaming with blockchain technology, reinventing roles in the esports ecosystem. That was 2023. It was fan-facing. It had nothing to do with player eligibility verification, roster attestation, or RLCS point tallies. The competitive identity layer — who is on which team, which region they qualify for, how many points they hold — has never moved onchain. TLDs are no longer just about websites; they now anchor digital identity, payments, and onchain interactions. The gap between what TLDs now enable and what RLCS currently deploys is structural.
What compete.rocketleague Would Actually Do
Start with the problem as it exists today. RLCS 2026 has players competing across seven regions, under three game modes, with citizenship and residency eligibility rules applied to rosters of three or four players per team, across six online Opens per split before two Majors and a six-day World Championship. A full breakdown of which countries fall under each RLCS region, along with the exact eligibility rules, can be found in the official RLCS rulebook. The rulebook is a PDF. The verification is a manual process. When a team registers for an RLCS Open, once a team places in the top 16 in an Open, they receive points, and teams with points only retain their points throughout a season if their roster does not change. Every roster change triggers a re-verification cycle. All of this is administered by humans, reconciled in spreadsheets, confirmed through email threads and submitted documentation.
A compete.rocketleague namespace — a sovereign onchain TLD owned by the circuit operator — changes the architecture of this problem. Each player in the circuit gets a subdomain. Call it atomic.compete.rocketleague. That subdomain is a wallet address, an identity endpoint, and a credential container. Onto it, BLAST administrators could sign attestations: regional eligibility status, active team membership, cumulative RLCS point totals per split, game mode participation flags. These attestations are onchain, signed by BLAST’s own keys, and permanently readable by any agent or interface with access to the chain. The W3C Verifiable Credential model already supports exactly this structure. The AP2 framework uses W3C Verifiable Credentials called “mandates” — cryptographically signed documents that represent user intent and approved transaction parameters — providing non-repudiable proof of consent for every transaction. The same primitive, applied to competitive credentials instead of commerce, creates player attestations that are non-repudiable, timestamped, and agent-readable.
The agentic use case is not speculative from a technical standpoint. ERC-8004 and x402 form a complete autonomous transaction loop — ERC-8004 answers “who you are” and “how trustworthy you are” through on-chain identity and reputation, while x402 handles “how agents pay each other” via HTTP-native micropayments. Substitute credential verification for payment and the same loop applies to circuit administration. An automated eligibility agent — operating on behalf of BLAST — could query atomic.compete.rocketleague at the point of Open registration, verify that the team roster holds valid regional citizenship attestations for the current season, confirm that the point total is accurate, and return a pass/fail in milliseconds. No administrator needs to open a support ticket. No rulebook PDF needs to be cross-referenced manually. The World Foundation’s AgentKit is a toolkit that lets AI agents carry cryptographic proof they are backed by a unique human via the World ID system, and by integrating with Coinbase and Cloudflare’s x402 protocol for stablecoin micropayments, it aims to make AI agents verifiable economic participants rather than suspicious automated traffic. The competitive circuit equivalent is an agent that treats player credentials as verifiable data rather than submitted documentation. x402 and comparable protocols solve how agents pay — but they do not solve who is paying. In both protocols, payments are associated with wallet addresses — anonymous hexadecimal strings with no inherent identity or access control. The same gap exists in credential verification: signatures need an identity anchor to mean anything. A compete.rocketleague SLD map — subdomains issued per player, signed per season — is that anchor.
The 2v2 expansion makes this more acute, not less. After Major 2, RLCS will host 2v2 Opens, and regional winners from NA, EU, SAM, and MENA will qualify for a spot at the Rocket League 2v2 World Championship 2026. Four regions, a separate bracket, a separate set of eligible duos, a separate prize pool of $170,000. That is a distinct identity population — 2v2 teams are not necessarily the same as 3v3 teams, and player eligibility needs to be tracked per mode, per region, per split. The administrative surface area just doubled on one axis. An onchain player identity endpoint handles the multiplicity cleanly: the same player subdomain can carry attestations for multiple game modes, multiple regional opens, and multiple seasons. A spreadsheet cannot do that without collapsing under its own version control.
Consider also the transparency benefit for the players themselves. Teams with points only retain their points throughout a season if their roster does not change. Under the current system, a roster change triggers an administrative review process that is opaque to the player until BLAST confirms or denies the result. With signed onchain attestations, the state of a team’s RLCS points is public, verifiable by third parties, and auditable by anyone who holds the player’s subdomain address. Disputes about point retention after roster changes become resolvable against an immutable record rather than a backend database query. The circuit grows more legible to the players who compete in it.
The Scoreboard Is Running. The Identity Layer Is Not.
RLCS 2026 is the most structurally complex Rocket League circuit ever run. Three game modes. Seven regions. Six online Opens per split. Two Majors. A six-day World Championship for 20 teams. Citizenship and residency eligibility rules applied to every roster in every region. $6.1 million in prize money distributed across multiple formats. All of it administered by BLAST, verified off-chain, reconciled manually. The circuit is scaling the competitive product. The identity infrastructure is not scaling with it.
ERC-8004 is the 2026 standard for trustless AI agent identity and reputation on Ethereum — think of it as the “Passport” for the Agentic Web. The x402 protocol, launched in May 2025 by Coinbase and Cloudflare, uses USDC and EIP-712 signatures and as of early 2026 has processed over 115 million transactions. The infrastructure for onchain identity and agent-readable credential endpoints is not theoretical. It is live. What does not exist yet is compete.rocketleague — the namespace that would connect RLCS player identities to that infrastructure. The circuit has a rulebook. It does not have a registry.
The author holds onchain positions related to this topic. This post reflects independent editorial judgment.