Protocol

Results oracle

Match results are published on-chain by an admin group using a multi-signature scheme. No single admin can publish a result unilaterally. Every published result includes a reference to the official source (league or broadcaster data) that underpins it.

If the admin group fails to publish results within the required window, the protocol automatically triggers a full refund to all participants for that matchday. There is no scenario where funds are locked without resolution.

Dispute resolution

After results are published, a 48-hour dispute window opens. During this period, anyone — not just participants — can challenge a result by submitting a deposit on-chain.

If the dispute is valid: The result is corrected, the deposit is returned to the challenger, and the challenger receives a reward from the protocol fund.

If the dispute is invalid: The deposit is forfeited to the protocol fund. This prevents spam disputes.

Prizes are not distributed until the dispute window closes cleanly.

Protocol fee

A 3% fee is applied to every prize pool — both individual pools and squad pools. This fee covers operational costs and ongoing development.

The fee does not go to the jackpot. The jackpot is funded exclusively by unclaimed prizes and empty-tier cascades. This separation is enforced at the contract level.

Decentralisation path

The current oracle (admin MultiSig) is a V1 trust assumption. The admin group is known, accountable, and multi-signature — but it is still a centralised point of truth for match results.

After mainnet launch, the protocol will migrate the oracle to Chainlink Functions. This replaces the admin group with a trustless, on-chain data feed. Once complete, no party can manipulate results — the protocol becomes fully permissionless.

This migration is planned as a post-launch upgrade and will be deployed without changing the core prize distribution or claiming mechanics.

Auditability

All contract code is open source and verified on-chain. Every event — matchday opens, picks submitted, results published, disputes filed, prizes distributed, claims executed — is logged to the chain and queryable through the protocol’s subgraph.