Platform Schematic

Club App Flow

The complete system — from fan sign-up to live vote to club revenue — mapped step by step.

< 100msVote latency
1 TokenPer vote
70%Club revenue share
3+Sports supported
01

Fan Registration

Sign up · Choose club · Profile created

Fan Signs Up

Email + Password

Auth Layer

BetterAuth session

Choose Club

AFL · Soccer · Rugby

Fan Profile Created

MySQL · Drizzle ORM

02

Token Purchase

Buy Club Tokens via Stripe · Wallet credited

Fan Dashboard

Token Wallet

Buy Tokens

Select quantity

Stripe Checkout

Secure payment

Balance Updated

Tokens credited instantly

03

Live Voting

Coach posts poll · Fans vote · Results stream in real time

Coach Posts Poll

Coach Interface

Fan Notified

Push notification

Token-Gated Vote

1 token = 1 vote

Voting Engine

Aggregates in real time

Event Stream Bus

Broadcasts to all clients

Live Results

Coach dashboard updates

04

Revenue Distribution

Poll closes · Monetisation engine · Club earns

Poll Closes

Timer expires

Monetisation Engine

Calculates club share

Club Revenue

Up to 70% of token sales

Analytics Dashboard

Full engagement data

Patent Pending Technology

Real-Time Data Compression

How eFanVote turns a massive burst of fan votes into an instant, usable insight for coaches — within a 5-second countdown window.

eFanVote real-time data compression schematic — 5-second countdown voting window
1

The Incoming Burst

When a coach posts a live poll, thousands of fans on the mobile app cast votes simultaneously — each carrying a Fan ID, their chosen option (A/B/C), a timestamp, and their token balance. This creates a massive, near-simultaneous data burst that must be processed within the 5-second countdown window.

  • Fan Mobile App sends vote payloads
  • Each vote: Fan ID · Choice · Timestamp · Tokens
  • Thousands of votes per second at peak
  • 5-second countdown timer governs the window
2

Compression in Action

The 5-second window is sliced into 10 x 500ms intervals (Timeslicing). Each slice runs on-the-fly compression using LZ4 / Zstandard algorithms — producing a small, efficient incremental update. At 0.0s, Workflow B fires the final tally and stores the full raw and aggregated dataset to the Voting Database.

  • Workflow A: Real-Time Sync every 500ms
  • Timeslicing prevents server-side bottlenecks
  • LZ4 / Zstandard on-the-fly compression
  • Incremental updates pushed to Event Streaming Bus
  • Workflow B: Final tally + DB storage at 0.0s
  • Full raw & aggregated data stored compressed
3

Key Patentable Innovations

Three core innovations make this system novel and patentable — each solving a distinct engineering challenge in real-time fan voting at scale.

Timeslicing

Breaking the 5s window into 10 smaller slices ensures constant, fluid data transmission and prevents server-side bottlenecks under peak load.

Optimised Protocol

Custom algorithms compress simple text/numeric vote data (Fan ID, Choice, Timestamp, Tokens) to maximise speed and minimise payload size.

Multi-Tenant Sync

The exact same data view is replicated across many different coaches or clubs simultaneously in near real-time, regardless of connection quality.

Result

A massive data burst → an instant, usable insight for the coach — in 5 seconds flat.

Event Streaming Bus (Redis / Kafka) · Coach Dashboard · Instant, Lag-Free Visuals · Patent Pending

Full System View

Complete Architecture

All four phases combined — showing how every component connects from fan registration through to club revenue.

01REGISTRATION
Fan Signs Up
Auth Layer
Choose Club
Fan Profile Created
02TOKEN PURCHASE
Fan Dashboard
Buy Tokens
Stripe Checkout
Balance Updated
03LIVE VOTING
Coach Posts Poll
Fan Notified
Token-Gated Vote
Voting Engine
Event Stream Bus
Live Results
04REVENUE
Poll Closes
Monetisation Engine
Club Revenue
Analytics Dashboard
Fan Vote Online full platform architecture diagram

Uploaded architecture diagram — Event Streaming Bus · Voting Engine · Monetisation Engine · Coach Interface · Club Revenue Dashboard

Platform Rules

How Voting Is Protected

Token-Gated Only

You must hold at least 1 Club Token to cast a vote. No tokens = no vote. This eliminates bots and spam.

One Vote Per Fan

Each fan can vote once per poll. The Voting Engine enforces this at the database level — no duplicates.

Authenticated Session

BetterAuth validates every vote request. Anonymous or expired sessions are rejected before reaching the engine.

Real-Time Aggregation

The Event Streaming Bus broadcasts live percentage updates to all connected clients within milliseconds.

Countdown Timer

Every poll has a configurable timer. When it expires the poll locks automatically — no late votes accepted.

Immutable Results

Once a poll closes, results are locked and stored permanently. Coaches and clubs can review any past poll.

Fans

Join the Vote

Fan accounts are coming soon. Get notified when we launch.

Get Notified

Clubs

Apply for a Licence

Get on the platform and start earning from every fan vote on game day.

Apply for a Licence