Page cover image

CryptoFights by FYX Gaming

PROJECT OVERVIEW

  • Product: CryptoFights turn based pvp fighting game

  • Company Name: FYX Gaming

  • Industry: Blockchain Gaming / Esports

  • Geographic Reach: Global, with development and user base primarily in the U.S. and Europe

  • BSV Integration Start Date: 2020

BUSINESS CHALLENGE

What inefficiencies or risks existed:

  • Existing blockchain platforms (e.g., Ethereum) lacked the scalability to handle high transaction volumes required by real-time gaming.

  • Congestion and high gas fees made gameplay costly and unreliable.

  • Most blockchain games used centralized storage for assets, undermining decentralization.

Why traditional systems were insufficient:

  • Traditional gaming platforms could not offer transparent, on-chain gameplay history.

  • True ownership of in-game assets was not possible with centralized data.

WHY BSV?

Ideal attributes of BSV:

  • Massively scalable infrastructure that can handle millions of transactions daily.

  • Extremely low fees make real-time game interaction feasible on-chain.

  • Data integrity and on-chain traceability of every action.

Comparison to other blockchains:

  • Ethereum was considered but failed under transaction load (e.g., CryptoKitties).

  • Layer 2 solutions introduced complexity and did not solve core scalability issues.

  • BSV was the only chain offering scalability, decentralization, and security simultaneously.

SOLUTION ARCHITECTURE

Overview:

  • A BSV-integrated backend that logs every move, item, and battle outcome directly on-chain.

Key components:

  • Data logging: All gameplay actions (e.g., turns, battles, item usage) are recorded immutably on BSV.

  • Smart contracts: Used to manage dynamic in-game NFTs and item crafting systems.

  • Tokenization: Fighters, weapons, and arenas are represented as smart NFTs with evolving properties.

Role of partners/vendors:

  • Internal development by FYX Gaming team with early support from BSV ecosystem advocates.

IMPLEMENTATION PROCESS

Phases:

  • Initial development on Ethereum (2018–2019) revealed limitations.

  • Transition to BSV began in 2020.

  • Open beta launched in 2021, generating over 10 million daily transactions at peak.

Integration with legacy systems:

  • Entirely new architecture built to leverage BSV’s capabilities.

Training/onboarding:

  • Players onboarded via simple web interfaces and tutorials to understand blockchain-backed gameplay.

OUTCOMES & BUSINESS IMPACT

Quantifiable improvements:

  • Up to 10.5 million daily transactions executed on-chain.

  • Lower costs allowed for fully on-chain gameplay.

  • Enhanced traceability enables features like battle replays, competitive integrity, and cross-game interactions.

Stakeholder feedback:

  • Developers benefit from transparent, replayable game data.

  • Players experience true ownership and provable history of characters/items.

CHALLENGES & MITIGATIONS

Challenges:

  • Initial backend struggled with traffic surge during influencer promotion.

Mitigations:

  • Paused operations temporarily to rework backend.

  • Improved internal (not blockchain) infrastructure to reliably handle millions of transactions.

FUTURE VISION

Expansion plans:

  • Launch of a fully immersive, reworked version of CryptoFights.

  • Development of open metaverse protocol with cross-game smart NFTs.

Additional BSV functionalities:

  • Programmable NFTs with logic and evolution (e.g., arenas that pay royalties or evolve with use).

  • Inter-game asset portability and dynamic metadata.

TESTIMONIAL HIGHLIGHTS

"Our product could not exist how it does without a blockchain that can scale—and scale massively." – David Case, CTO, FYX Gaming

"We’re trying to prove it can be done differently. We’re actually putting gameplay on-chain—not just NFTs." – Adam Kling, CEO, FYX Gaming

"(On BSV) we started doing several million transactions per day. Eventually, we reached 10.5 million per day. For context, Ethereum can maybe do 1.3 million a day, Bitcoin even less. Other chains might push higher numbers but often sacrifice decentralization or security to do so." – Adam Kling

Last updated