Revenue Recognition

The Company follows Accounting Standards Codification (“ASC”) Topic 606, Revenue from Contracts with Customers (“ASC 606”). This standard establishes a single comprehensive model for entities to use in accounting for revenue arising from contracts with customers. ASC 606 requires an entity to recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services and also requires certain additional disclosures.

In accordance with ASU Topic 606 - Revenue from Contracts with Customers, the Company recognizes revenue in accordance with that core principle by applying the following steps:

Step 1: Identify the contract(s) with a customer.

Step 2: Identify the performance obligations in the contract.

Step 3: Determine the transaction price.

Step 4: Allocate the transaction price to the performance obligations in the contract.

Step 5: Recognize revenue when (or as) the entity satisfies a performance obligation.

The Company plans to generate revenue from the following sources:

  The Company generates revenue from the sale of our in-game items to our customers. Revenue generated from such sales, primarily through the app stores, such as Google Play Store or Apple App Store, is recognized upon delivery of the in-game items to the customer, which is when the Company completes its sole performance obligation. Fees incurred by the Company, such as commissions to the app stores, are recognized in operating expenses.
     
  The Company plans to generate revenue from advertising fees paid by game advertisers, developers, hardware companies, or other strategic partners to the Company for promotion on our platform. Revenues from these fees will be recognized ratably over the agreed upon advertising service period and upon delivery of agreed upon advertising services, which constitutes satisfaction of the performance obligation.
  The Company plans to generate royalty revenues when a third party sells one of our NFTs on a third-party platform. We will recognize royalty revenue when it is probable that we will collect the royalty fee owed which is typically when we receive notification from the third-party platform that an NFT has been sold, which constitutes satisfaction of the performance obligation. In the instance where the Company will receive royalty payments when a customer disposes of an in-game NFT in the secondary market on a third-party platform or any other payment that is not in fiat currency, the Company will recognize the revenue in accordance with ASC 606-10-32-21, “Noncash Consideration”. The fair value of the non-cash consideration received shall be determined by using the quoted price for such non-cash consideration on the date of the transaction.

About Revenue Disclosures

Revenue disclosures under ASC 606 explain how a company identifies performance obligations, allocates transaction prices, and determines when revenue is recognized. This section is essential for understanding whether reported revenue reflects genuine economic activity or aggressive accounting choices. Analysts examine the mix of point-in-time versus over-time recognition, which directly affects revenue timing and comparability.

Key signals: rising contract liabilities (deferred revenue) suggest strong future revenue visibility, while declining contract assets may indicate slowing project milestones. Watch for variable consideration estimates — rebates, returns, and performance bonuses that require management judgment. Significant changes in disaggregated revenue by geography or product line can reveal shifting business mix before it appears in headline numbers. Compare revenue growth against contract liability growth to assess sustainability, and scrutinize any changes in the timing of recognition that coincide with earnings pressure.