RIVALCORE
COMPETITION WITH A MEMORY

A result becomes history only after it earns trust.

This beta process explains how RivalCore challenges, verifies results, handles disputes, and updates progression without pretending every submission is automatically final.

Beta placeholder · approval pendingVersion 1Published
01

1. Create or accept a challenge

Players choose an exact game, mode, region, platform, team size, season, and rules version. Acceptance locks those competitive dimensions so a result cannot silently move to a different ladder.

02

2. Lock the match room

The accepted roster and rules snapshot are preserved with the match. Participants use the private room for scheduling, check-in, evidence, and result confirmation.

03

3. Report and confirm

A participant reports the complete result. Other participants may confirm it or open a dispute. Unconfirmed and disputed submissions do not update public ratings.

04

4. Finalize exactly once

Finalization is atomic and idempotent: the match state, participant placements, rating ledger, Mastery ledger, records, and audit trail commit together or not at all.

Versioned and auditable: administrators cannot overwrite this document in place. An edit publishes a new version and records the change in RivalCore’s audit log. This version’s change note is “Initial transparent beta placeholder”.

See how verification works Read the community code
RanksLFGMatchesTrust