Hybrid-Chain Arena · Esports demonstration

Every match has a story.
Make it verifiable.

Connect the competition, the audience, and the evidence. Arena brings match events, spectator participation, player achievements, and creator-revenue projections into one inspectable experience.

A synthetic CS2 match, not a live competition. Demo credits only; no real funds move.

Different perspectives. A connected record.Conceptual illustration—not a live feed or a settlement diagram.

Explore the experience

One match.
Five ways to understand it.

Choose a view below. You can inspect the public demonstration without an account; controlling the shared playback requires presenter permission.

Arena Admin
Synthetic CS2 fixture · Demo credits only

No real funds move. Escrow, payout, and creator-revenue values are deterministic projections from the Rust Arena Engine.

AXIOM — : — VERTEXCS2 · de_mirage · 2V2Connecting to demo— evidence records

Start with the action.

Follow the score, player statistics, and event sequence. The shared demo clock is controlled by an authorized presenter; a scheduled or paused match may have no events yet.

PLAYER VIEW · LIVE MATCHCONNECTING
TEAM AXIOM0RHEA · ATLAS
:
TEAM VERTEX0NOVA · ECHO
PLAYER POOL PROJECTED0 CRCustomer authorization and Core settlement remain separate
MPC ESCROW APPROVALCUSTOMER CONTROLLED
SIGN IN TO PREPARE APPROVAL

Preparation only · no Core submission, wallet signature, broadcast, or value movement

NORMALIZED GAME FEEDSERVER → EVIDENCE

Waiting for the first authenticated match event…

0.0 / 24.0 SEC · CONNECTING

From the action to the explanation

More than a scoreboard.
A trail you can follow.

Move between the experience and its supporting record without treating a projected outcome as a settled fact.

  1. Follow the event

    The synthetic game feed gives the match a sequence: who acted, what happened, and when. Start with the score and player statistics, then inspect the event trail.

  2. Connect the perspectives

    The Arena Engine derives match state, market views, achievements, and revenue projections. Each view helps explain a different consequence of the same demo match.

  3. Inspect the record

    Arena Proof checks the portable package and evidence-chain links in your browser. Download becomes available only after that verification succeeds.

  4. Keep authorization separate

    A projection is not a payment. Customer authorization, escrow approval, and Core settlement remain separate steps; the demo does not move real value.

Start with your use case

One demonstration.
Different questions to explore.

Competition operators

Evaluate a match experience that connects the scoreboard to the events behind it. See where participant controls and reviewable records fit before planning an integration.

Creators & communities

Explore how a revenue projection is divided and attributed. Use the creator view to understand the model—not as a promise of earnings or a completed payout.

Platform & engineering teams

Trace the boundary between Identity, the Arena Engine, and proof verification. Discuss your game feed, operating rules, and deployment requirements with our team.

Before you go further

Clear boundaries.
Better questions.

What can I do without signing in?

Browse the five demo views and inspect the public synthetic projections. The shared playback is presenter-controlled. Presenter commands and retained demo actions require sign-in and the relevant permissions.

Is this a live match or a real-money market?

No. This page demonstrates a deterministic, 24-second CS2 fixture using demo credits. Market positions, escrow, payout, and creator-revenue figures are synthetic projections, not real-money activity.

What does a verified proof establish?

The browser checks the portable Arena package and its evidence-chain links. That check does not independently establish that a real-world match occurred, that a game was fair, or that a payment settled.

Can I use Arena for another game or my own platform?

This demonstration uses CS2. A different game or branded experience needs a review of the event integration, rules, identity controls, and deployment scope. Contact us to assess your requirements; the demo does not establish universal game support or production availability.

Build around the experience

What could Arena bring
to your platform?

Tell us about your game, audience, and operating model. We’ll help identify the integration requirements and the boundaries that matter.

Discuss an Arena integration