VRF NFT Minting Callback Limitations
Our project relied on minting NFTs via a separate contract triggered through a VRF (Verifiable Random Function) callback. This separation caused issues with reliably notifying the front-end or user-facing contract about minting outcomes. Due to this, we had to engineer a custom infrastructure for listening to onchain events and routing responses accordingly. This ensured users received accurate feedback despite the complexity of the callback architecture.

Gas Costs from Complex NFTs
We initially designed NFTs with numerous onchain traits, however this significantly increased gas costs during minting and interactions. To address this, we combined our essential onchain traits with non-essential offchain traits. The visual and descriptive metadata is now managed offchain through a dedicated backend service. This maintains a rich user experience without compromising on onchain fairness for game mechanics.

Scalability and Contract Interoperability
Our loyalty system required player progress and activity to be tracked entirely onchain, necessitating interaction with over thirty external contracts. This added complexity in ensuring that our core contracts were scalable, modular, and interoperable. We invested time into creating a clean, extensible architecture that can communicate with future games or upgrades seamlessly while maintaining security and gas performance.

Unreliable Indexing Services
Real-time responsiveness was critical for ingame events, especially when ownership or state changes happened quickly. Unfortunately, third-party indexing services like Alchemy and Moralis frequently returned stale data, which was unacceptable for our use case. In response, we developed a bespoke contract event ingestion system, tailored for our game's real-time needs for accuracy.