# CryptoFights by FYX Gaming
### Project Overview
* **Product:** CryptoFights turn based pvp fighting game
* **Company Name:** FYX Gaming
* **Industry:** Blockchain Gaming / Esports
* **Website URL:**
* **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.
{% embed url="" %}
### 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
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://bsv-case-studies.bsvblockchain.org/esports-and-gaming/cryptofights-by-fyx-gaming.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.