Historical architecture
combined gameplay services, blockchain data, oracle integrations, and operational analytics to support the original game.
CryptoFights
Building on an on-chain RPG with a browser-based play experience and recoverable training battles.
My role
led the historical FYX platform and contributed recent browser migration and training-battle work.
The problem
A browser version needs to preserve the feel of the original game while keeping battle progress consistent through interrupted connections.
The approach
Connected browser animation and gameplay to server-managed battle progression, building on the earlier FYX platform architecture.
What it enables
Supports browser-port and battle-recovery capabilities. Separately, the historical FYX platform reached 100K+ peak daily active users and 2M+ daily transactions.
The work,
and its boundaries.
Browser experience
adapts the original animation timing and movement to a browser engine rather than treating the migration as a visual replacement.
Recoverable play
supports resuming training battles after uncertain or interrupted responses, with battle progress managed by the server.
Architecture
separates presentation from authoritative progression so the browser shows the game while the backend remains responsible for the battle record.
Scope
recent work covers training battles without economic rewards; the historical audience and transaction figures are not results of the browser migration.
Technology
- Unity
- Three.js
- JavaScript
- Node.js
- Blockchain
Let’s make your next project workable.
Talk with me about the product, the engineering and the decisions that need to stay with people.