§1
Introduction
Why operators are trusted today, why on-chain action games haven't worked, and the separation we propose.
Whitepaper
Warfront Legends: A Hybrid Web2/Web3 Side-Scrolling Action Game
A technical paper describing the network model, replay attestation protocol, settlement, token mechanics, and failure modes. Styled after Nakamoto (2008).
A purely server-authoritative game would still require players to trust a central operator with custody of their cosmetic identity, earned achievements, and tradable items. We propose a design in which the gameplay loop remains entirely off-chain — low-latency, free-to-play, and indistinguishable from a conventional Web2 action title — while a separate, optional settlement layer on Base records ownership of cosmetic assets, soldier identities, and verifiable competitive results.
Players need not interact with the chain to play, progress, or compete. Players who do interact with the chain receive custody of their items as ERC-721 and ERC-1155 tokens, and competitive rewards are distributed through Merkle-attested snapshots signed by the game server, verified on-chain at claim time.
The system separates gameplay state, which must be fast and authoritative, from ownership state, which must be permissionless and persistent.
Contents
Thirteen sections.
§2
System Overview
Four components: client, simulation server, attestation service, settlement contracts on Base.
§3
Identity
Soldiers as cosmetic identity. ERC-721 mint is opt-in and revocable; gameplay is unaffected.
§4
Gameplay State
Server-authoritative simulation, fixed tick, local prediction, and ephemeral state retention.
§5
Replay Attestation
(seed, inputs, result) tuples signed by the operator and independently re-simulable by any auditor.
§6
Settlement
Per-season Merkle distribution: only the root goes on-chain, claims are constant-cost per player.
§7
Tradable Items
ERC-1155 cosmetic gear on a permissionless exchange. Strictly cosmetic, no gameplay tokenization.
§8
The Token
$WARF: ERC-20 utility token, 10^9 fixed supply, allocation across rewards, ecosystem, team, treasury, liquidity, and public sale.
§9
Token Sinks
Four sinks (mint fees, callsigns, marketplace fees, cosmetic upgrades) calibrated to bound emissions.
§10
Anti-Cheat
Input validation, statistical detection, re-simulation of high-stakes matches, and bug bounties.
§11
Privacy
Minimum identifying data. Wallet linking opt-in. Replays not public by default.
§12
Failure Modes
Operator key compromise, operator shutdown, smart contract bugs — and what survives each.
§13
Conclusion
Off-chain gameplay, on-chain ownership, signed attestations as the only bridge between them.