A market for football judgment, settled as competition.
Soccit is a competitive football prediction application in which participants commit fixture-specific forecasts, receive points when those forecasts match official results or events, and compete for rewards held in match-specific vaults.
The system is designed around three properties: predictions must be attributable to a wallet, their lock conditions must be auditable, and competition outcomes must follow an explicit scoring and settlement policy. Solana provides account state, transaction authorization, and settlement rails; a live-football data provider supplies fixtures, lineups, scores, and events; Soccit services reconcile these sources into the application experience.
This paper describes the intended Season 01 system. It is a product and protocol specification, not a claim that every dependency is decentralized or trustless. Where off-chain data, orchestration, or administrative settlement remains necessary, those boundaries are stated directly.
Football expertise is abundant. Verifiable competition is fragmented.
Football audiences continually form high-resolution judgments: the likely final score, which starter will be replaced, when a tactical change will occur, or how a match state will evolve. Conventional prediction products often compress that knowledge into an odds selection, while informal competitions lack durable proof of when a call was made and how the winner was determined.
Soccit treats a prediction as a time-bound competitive action. The participant expresses a specific football claim; the claim is associated with a fixture and wallet; the result is evaluated under a published rule; and the reward outcome is tied to the corresponding match competition.
Support predictions beyond a binary winner selection.
Record who committed a call and under which match conditions.
Turn accuracy into transparent points, rank, and reward allocation.
Specific rules, user custody, and legible state.
- 01Deterministic competition rulesPrediction types, point values, tie-break behavior, fee treatment, and prize shares should be explicit before participation.
- 02User-controlled authorizationThe participant’s wallet approves the transaction. Soccit does not require custody of the wallet or authority to sign on the user’s behalf.
- 03Fixture-scoped stateEvery competition is associated with one football fixture, its match account, entry conditions, participant set, and settlement state.
- 04Live legibilityThe interface must surface the current score, minute, lineup, match status, transaction state, and leaderboard state without implying stronger finality than exists.
- 05Composable data boundariesOn-chain state, official sports data, and application services remain separable so each source can be audited and improved independently.
Actors, accounts, and authoritative sources.
The system comprises participants, application services, a live-data source, Solana programs and accounts, and an operator responsible for ingestion and settlement operations. These roles do not carry equal authority.
- Participant
- A user represented by a Solana wallet. The wallet authorizes entry and prediction transactions and is the destination identity for rewards.
- Match account
- A program-derived Solana account associated with a fixture. It records competition parameters such as teams, entry fee, pool state, status, settlement flag, and winner addresses.
- Prediction account
- A wallet- and fixture-associated record containing the encoded prediction and lock context used for scoring and ranking.
- Live-data source
- The provider of fixture metadata, official lineups, match status, goals, substitutions, cards, and match timing consumed by Soccit’s ingestion services.
- Soccit services
- The API, ingestion workers, caches, profile services, leaderboard computation, transaction preparation, and server-sent event streams exposed to the client.
- Operator
- The entity responsible for maintaining data ingestion, resolving operational exceptions, initiating permitted lifecycle transitions, and executing settlement procedures.
A numeric fixture identifier maps to a canonical match-account PDA. Client routes and fixture-scoped API calls use that PDA, avoiding ambiguity between external provider identifiers and the on-chain competition account.
Open, live, resolved, settled.
Open
The competition account is available. Entry conditions are visible and eligible predictions may be submitted.
Live
The underlying fixture is in progress. Live score, minute, events, and rankings update as data is ingested.
Resolved
The football result is known and new prediction activity stops while final scoring and settlement are prepared.
Settled
Winner addresses and terminal state are recorded; the competition is presented as final and reward distribution completes.
The application distinguishes on-chain competition status from live fixture status. A match account can remain open while the external fixture is live, and a finished fixture can enter a resolved interval before on-chain settlement. Interfaces should expose these states rather than collapsing them into a single “live/not live” flag.
Finite claims evaluated under published rules.
Season 01 supports final-score and substitution predictions. Each record includes the fixture, prediction kind, encoded values, team side where applicable, and lock minute.
kind = 3; side = 0; outPlayerId = homeGoals; inPlayerId = awayGoalskind = 2; side = home | away; outPlayerId = starter; inPlayerId = substitute| Model | Evaluation | Points |
|---|---|---|
| Final score | Exact home and away totals | 5 |
| Final score | Correct win, draw, or loss only | 3 |
| Substitution | Correct outgoing and incoming players | 3 |
| Substitution | Correct outgoing player only | 1 |
| Substitution | Correct incoming player only | 1 |
rank(a, b) = points descending, then earliestScoringLockMinute ascendingThe tie-break rewards an earlier prediction only when that prediction contributes to scoring. This avoids granting priority merely for entering early without producing a correct football read.
Fixture-specific pools with explicit fee and reward shares.
Each match account exposes an entry fee and pool total denominated in the configured token’s base units. Under the current model, 20% of the accumulated pool is allocated as the platform fee and 80% is treated as the net prize pool.
P_net = P_gross × (1 − 0.20) = P_gross × 0.80R_1 = P_net × 0.50; R_2 = P_net × 0.30; R_3 = P_net × 0.20The client currently presents a winner-takes-all fallback when fewer than three ranked participants are available. Production settlement logic must apply the same published eligibility rule used by the interface; any future change to fee rate, rank shares, minimum participation, refund policy, or token denomination should be versioned and displayed before entry.
No native token is specified by this paper. Participation and rewards use the mint configured for the match account. The economic model is therefore a competition-pool design rather than a token issuance model.
Three layers, each with a distinct responsibility.
The transaction-preparation endpoint returns a serialized unsigned transaction and its relevant addresses and expiry context. The client deserializes it, requests the participant’s signature through the connected wallet, and submits the signed transaction to Solana. There is no server-side participant signing step.
Leaderboard and event streams use server-sent events. These streams improve responsiveness but do not redefine finality: clients should treat the on-chain competition account and confirmed settlement state as the durable competition record.
The system is non-custodial at signing, not trustless in every input.
Soccit’s wallet flow preserves participant authorization: a wallet can reject a prepared transaction, and the service cannot sign as the participant. This is a meaningful custody boundary, but it does not eliminate dependence on application code, RPC infrastructure, live-data ingestion, scoring logic, operator permissions, or the upstream sports-data provider.
Primary trust assumptions
- —The displayed transaction accurately represents the participant’s selected prediction and configured entry conditions.
- —The upstream football data and Soccit ingestion pipeline identify official events and terminal results correctly.
- —The scoring implementation applies the published rules consistently to all participants.
- —Authorized lifecycle and settlement operations are executed against the correct fixture and winner set.
- —The deployed Solana program and configured token accounts match the addresses presented by official Soccit interfaces.
Recommended controls include program audits before material value is placed at risk, multisignature or constrained authority for privileged operations, replay-resistant wallet messages, simulation and human-readable transaction review, monitored ingestion with reconciliation, idempotent settlement, public program and mint disclosure, incident procedures, and versioned rule publication.
Current boundaries are part of the specification.
- LIMITFinal-score and substitution predictions are active; goalscorer predictions remain planned.
- LIMITSports outcomes originate off-chain and require trusted ingestion before they can influence scoring and settlement.
- LIMITReal-time interfaces can temporarily diverge from confirmed on-chain state because of provider, network, cache, or RPC latency.
- LIMITThe current fee and payout policy is a Season 01 product rule and may require jurisdiction-specific review before broader availability.
- LIMITWallet authorization prevents unauthorized participant signing but does not by itself verify the fairness of upstream data or scoring software.
- LIMITThis paper does not constitute financial, legal, or investment advice and does not guarantee rewards or uninterrupted availability.
Advance from legibility to stronger verifiability.
Season 01 hardening
Align interface rules with settlement code, publish canonical addresses, improve reconciliation, and validate operational controls.
Prediction expansion
Introduce goalscorer and additional football knowledge models only after scoring inputs and eligibility rules are explicit.
Transparency
Expose richer transaction, match-account, scoring, and settlement evidence so participants can independently inspect outcomes.
Governance maturity
Constrain privileged actions, formalize upgrade and incident procedures, and evaluate independent audits and distributed data attestations.
Roadmap items describe intended direction rather than guaranteed delivery. A future paper revision should record material changes to prediction semantics, economic parameters, authorities, data providers, or settlement design.
Make the prediction specific. Make the outcome inspectable.
Soccit’s central proposition is simple: football judgment becomes more valuable as a competition when the claim is precise, its commitment is attributable, and its scoring rule is known in advance. The product combines an expressive match interface with wallet authorization, fixture-scoped accounts, live sports data, and explicit leaderboard and reward policies.
The long-term quality of the system depends less on spectacle than on alignment: the interface, transaction, on-chain state, official result, scoring engine, and settlement output must tell the same story. Season 01 establishes that structure and makes its present trust boundaries visible.