Skip to content

Permanent Match Records

Once the broadcast of a tournament match has ended, FoxLeague writes a small record of it to Autonomys Auto Drive, a permanent public storage network. Every tournament format counts, 1v1 challenges included. Private (invite-only) tournaments count too: only the invited teams can join one, but its results are public. Ranked and casual games get no record, nor do developer tournaments and challenges. The match page then shows a Permanent record on Autonomys link.

A record is one small JSON file (about 1 KB):

  • schema: the record’s version, foxleague.match-record/1
  • network: mainnet
  • match: the match’s public id (the one in its page’s address), tournament or challenge, the kickoff and the end of the broadcast
  • competition: the tournament’s id, title, format and tier, the round, the group and the leg
  • home and away: each team’s name as the match page showed it, its goals and its penalties when the match was decided by them
  • decided_by: regular, extra_time or penalties
  • replay: the match page, the download address of the replay file (.rcg), the file’s size in bytes and its SHA-256 fingerprint
  • recorded_at: when the record was made

Public game data only: no wallet address, no coach name, no e-mail address, no Telegram user id or username, no IP address. The record holds no replay, only its size and its fingerprint. A team is named the way its match page names it when the record is made: a later rename does not change a record already written. The Privacy Policy (section 12) says the same.

After the broadcast has ended, once FoxLeague keeps the replay in its off-site archive. That usually takes a few minutes. On a busy day it can take longer: FoxLeague writes at most a set number of records a day, the newest matches first. A match decided without being played (a walkover) has no replay, so it gets no record.

  1. Open the match page and click Permanent record on Autonomys. The record opens on the public Autonomys gateway.
  2. Download the replay from the record’s replay.download address.
  3. Compute the file’s SHA-256:
    • Linux: sha256sum file.rcg
    • macOS: shasum -a 256 file.rcg
    • Windows (PowerShell): Get-FileHash file.rcg -Algorithm SHA256
  4. The result must equal replay.sha256. The file’s size must equal replay.bytes.

Equal means the replay you downloaded is, byte for byte, the replay FoxLeague recorded when the broadcast ended. The fingerprint is of the file exactly as FoxLeague serves it for download. Should FoxLeague ever change how it serves replays, a record written before keeps the fingerprint of the file as it was served then. This page will say so.

For some matches FoxLeague also keeps the full replay file (.rcg) on Autonomys Auto Drive, after the record. It is byte for byte the file the record’s replay.download address serves: the match as the match engine recorded it, with the two team names, the match engine’s settings (each player’s type included), every position and action of the players and the ball, the referee’s decisions and the score. FoxLeague links it only after checking that its size and its SHA-256 equal the record’s replay.bytes and replay.sha256. Like the record, it is permanent and public. It holds no wallet address, no coach name, no e-mail address, no Telegram user id or username, no IP address. Ranked and casual games, developer tournaments and developer challenges get no replay file. The Privacy Policy (section 12) says the same.

Which matches get one is FoxLeague’s choice within the storage it has on Autonomys: every tournament match and 1v1 challenge whose broadcast ended from a set date, unless FoxLeague keeps only the finals.

When a match has one, its page shows Permanent record and full replay on Autonomys, with a link on each. The replay link opens the file on the public Autonomys gateway: steps 3 and 4 above check it against the record the same way.

The FoxLeague MCP’s tournament detail (get_tournament) gives each finished match its permanent_record: the record’s cid and its url on the gateway. A match with its full replay on Autonomys also gives permanent_replay, its cid and its url. See Connect an AI.