NATURE OF BUSINESS AND SIGNIFICANT ACCOUNTING POLICIES (Policies)

12 Months Ended

May 31, 2024

Wewards, Inc. (“Wewards” or “the Company”) was incorporated in the state of Nevada on September 10, 2013 as Betafox Corp., with the initial intent to manufacture and sell color candles. On April 26, 2015, Giorgos Kallides (the “Seller”), entered into an agreement with Future Continental Limited (“Purchaser”), pursuant to which, on May 11, 2015, the Seller sold to Purchaser six million (6,000,000) shares of common stock of the Company (the “Shares”) owned by the Seller, constituting approximately 73.8% of the Company’s 8,130,000 issued and outstanding common shares at such time, for $340,000. In October 2015, the Purchaser sold the 6,000,000 Shares to Mr. Lei Pei, an affiliate of the Purchaser, in consideration of Mr. Pei’s agreement to serve as our director and CEO. On January 8, 2018, by consent of Lei Pei as the Company’s principal shareholder, the Company changed its name to Wewards, Inc. The Company’s corporate office is located in Las Vegas, Nevada.

We have developed and are the owner of a web-based platform accessible by mobile apps (the “Platform”) that will enable consumers to purchase goods from merchants and earn rebates payable in the form of Bitcoin. The Platform provides an innovative Bitcoin rewards ecosystem. It is designed to transform traditional concepts of commerce into a cooperative society where both merchants and consumers are collaborating, utilizing Bitcoin to reward consumers. The ecosystem provides consumers with rewards each time they complete a challenge defined by a merchant. This is intended to make the ecommerce process beneficial to all market participants, and to help distribute commercial wealth among and between the merchants and consumers. We intend to generate revenue by licensing “white-label” versions of the Platform to third parties. However, to date, no such license agreement has been entered into, and we have not generated any revenues from the Platform.

On April 2, 2020, we purchased intellectual property rights (“IP”) from United Power, a Nevada corporation under common ownership with Lei Pei, our sole officer and director and majority shareholder, for cash consideration of $179,300, based on a price determined by an independent valuation.

The IP consists of technology and related rights associated with the game Megopoly, an MMO (Massively Multiplayer Online Game). Megopoly is an MMO board game where players are able to earn fractions of Bitcoins (satoshi) through buying, selling, and managing virtual real estate properties using in-game currency (Megopoly Coins). The game is similar in some respects to Monopoly.

The game allows players around the world to interact with each other online. Players travel (move) through different parts of a city, earning profit by investing in properties, charging rent, acquiring bonus assets, and selling their properties to other players for in-game currency. A player is able to progress to higher levels of “cities” at any time.

The player’s goal in Megopoly is to earn Megopoly Coins by investing in properties and collecting rent from other players. Players can keep playing the game using their Megopoly Coins for the opportunity to earn more coins, or they can exchange those coins for Bitcoins based on real-time market exchange rates.

Megopoly is playable at any time through a web browser on a PC, tablet or smart phone, in both Chinese and English. The game has been designed for players of all skill levels. To date, we have not generated any revenue from Megopoly other than pursuant to related party agreements as described below.

The Company entered into an agreement in January of 2021 with Sandbx Corp., a company owned by the Chief Operating Officer of United Power and FL Galaxy, related parties to the Company, as our Chief Executive Officer, Lei Pei, is also the Chief Executive Officer of United Power and FL Galaxy, to further develop the Megopoly game, under which the Company paid Sandbx Corp. monthly fees of $168,500, resulting in $1,622,500 of related party software development costs for the year ended May 31, 2022. The development agreement with Sandbx Corp. was terminated with the completion of Megopoly in December of 2021. The Company did not generate any revenue, or incur any software development costs, during our fiscal years ended May 31, 2024 or 2023, and is now actively seeking licensing arrangements to bring the game to market.

Basis of Accounting

The accompanying financial statements have been prepared in conformity with accounting principles generally accepted in the United States of America and the rules of the Securities and Exchange Commission (SEC). All references to Generally Accepted Accounting Principles (“GAAP”) are in accordance with The Financial Accounting Standards Board (“FASB”) Accounting Standards Codification (“ASC”) and the Hierarchy of Generally Accepted Accounting Principles.

Use of Estimates

The preparation of financial statements in conformity with accounting principles generally accepted in the United States of America requires management to make estimates and assumptions that may affect the reported amounts of assets and liabilities and disclosure of contingent assets and liabilities at the date of the financial statements and the reported amounts of revenues and expenses during the reporting period. Actual results could differ from these estimates.

Concentrations of Credit Risk

The Company maintains cash in bank deposit accounts, the balances of which at times may exceed federally insured limits. Accounts are guaranteed by the Federal Deposit Insurance Corporation (FDIC) up to $250,000 under current regulations. The Company had approximately $514,205 and $640,755 in excess of FDIC insured limits at May 31, 2024 and 2023, respectively. The Company has not experienced any losses in such accounts.

Fair Value of Financial Instruments

The Company adopted ASC 820, Fair Value Measurements and Disclosures (ASC 820). ASC 820 defines fair value, establishes a three-level valuation hierarchy for disclosures of fair value measurement and enhances disclosure requirements for fair value measures. The three levels are defined as follows:

-	Level 1 inputs to the valuation methodology are quoted prices (unadjusted) for identical assets or liabilities in active markets.
-	Level 2 inputs to the valuation methodology include quoted prices for similar assets and liabilities in active markets, and inputs that are observable for the asset or liability, either directly or indirectly, for substantially the full term of the financial instrument.
-	Level 3 inputs to valuation methodology are unobservable and significant to the fair measurement.

The carrying value of cash, accounts payables and accrued expenses are estimated by management to approximate fair value primarily due to the short-term nature of the instruments.

Impairment of Long-Lived Assets

Long-lived assets held and used by the Company are reviewed for possible impairment whenever events or circumstances indicate the carrying amount of an asset may not be recoverable or is impaired. Recoverability is assessed using undiscounted cash flows based upon historical results and current projections of earnings before interest and taxes. Impairment is measured using discounted cash flows of future operating results based upon a rate that corresponds to the cost of capital. Impairments are recognized in operating results to the extent that carrying value exceeds discounted cash flows of future operations.

Convertible Instruments

The Company evaluates its convertible instruments, options, warrants or other contracts to determine if those contracts or embedded components of those contracts qualify as derivatives to be separately accounted for under ASC Topic 815, “Derivatives and Hedging.” The result of this accounting treatment is that the fair value of the derivative is marked-to-market each balance sheet date and recorded as a liability. In the event that the fair value is recorded as a liability, the change in fair value is recorded in the statement of operations as other income (expense). Upon conversion or exercise of a derivative instrument, the instrument is marked to fair value at the conversion date and then that fair value is reclassified to equity. Equity instruments that are initially classified as equity that become subject to reclassification under ASC Topic 815 are reclassified to liabilities at the fair value of the instrument on the reclassification date. We analyzed the derivative financial instruments (the Convertible Notes), in accordance with ASC 815. The objective is to provide guidance for determining whether an equity-linked financial instrument is indexed to an entity’s own stock. This determination is needed for a scope exception which would enable a derivative instrument to be accounted for under the accrual method. The classification of a non-derivative instrument that falls within the scope of ASC 815-40-05 “Accounting for Derivative Financial Instruments Indexed to, and Potentially Settled in, a Company’s Own Stock” also hinges on whether the instrument is indexed to an entity’s own stock. A non-derivative instrument that is not indexed to an entity’s own stock cannot be classified as equity and must be accounted for as a liability. There is a two-step approach in determining whether an instrument or embedded feature is indexed to an entity’s own stock. First, the instrument's contingent exercise provisions, if any, must be evaluated, followed by an evaluation of the instrument's settlement provisions. The Company utilized multinomial lattice models that value the derivative liability within the notes based on a probability weighted discounted cash flow model. The Company utilized the fair value standard set forth by the Financial Accounting Standards Board, defined as the amount at which the assets (or liability) could be bought (or incurred) or sold (or settled) in a current transaction between willing parties, that is, other than in a forced or liquidation sale.

Revenue Recognition

The Company recognizes revenue in accordance with ASC 606 — Revenue from Contracts with Customers. Under ASC 606, the Company recognizes revenue from the licensing of our software by applying the following steps: (1) identify the contract with a customer; (2) identify the performance obligations in the contract; (3) determine the transaction price; (4) allocate the transaction price to each performance obligation in the contract; and (5) recognize revenue when each performance obligation is satisfied. All revenues to date have been recognized from licensing Megopoly and related IP to Sandbx Corp., a separate company owned by the Chief Operating Officer of United Power and FL Galaxy, related parties of the Company, as our Chief Executive Officer, Lei Pei, is also the Chief Executive Officer of United Power and FL Galaxy.

We derive revenue principally from licensing our intellectual property, including our game, and related extra content and services that can be utilized by players of our game. Our product and service offerings include, but are not limited to, licensing to third parties (“software license”) to distribute and host our games and content (“Online-Hosted Service Games”).

We evaluate and recognize revenue by:

•

identifying the contract(s) with the customer;

•

identifying the performance obligations in the contract;

•

determining the transaction price;

•

allocating the transaction price to performance obligations in the contract; and

•

recognizing revenue as each performance obligation is satisfied through the transfer of a promised good or service to a customer (i.e., “transfer of control”).

Online-Hosted Service Games. Sales of our Online-Hosted Service Games are determined to have one distinct performance obligation: the online hosting. We recognize revenue from these arrangements as the service is provided through our licensing agreement(s).

Licensing Revenue

We utilize third-party licensees to distribute and host our games and content in accordance with license agreements, for which the licensees typically pay us a fixed minimum guarantee and/or sales-based royalties. These arrangements typically include multiple performance obligations, such as a time-based license of software and future update rights. We recognize as revenue a portion of the minimum guarantee when we transfer control of the license of software (generally upon commercial launch) and the remaining portion ratably over the contractual term in which we provide the licensee with future update rights. Any sales-based royalties are generally recognized as the related sales occur by the licensee.

Significant Judgments around Revenue Arrangements

Identifying performance obligations. Performance obligations promised in a contract are identified based on the goods and services that will be transferred to the customer that are both capable of being distinct, (i.e., the customer can benefit from the goods or services either on its own or together with other resources that are readily available), and are distinct in the context of the contract (i.e., it is separately identifiable from other goods or services in the contract). To the extent a contract includes multiple promises, we must apply judgment to determine whether those promises are separate and distinct performance obligations. If these criteria are not met, the promises are accounted for as a combined performance obligation.

Determining the transaction price. The transaction price is determined based on the consideration that we will be entitled to receive in exchange for transferring our goods and services to the customer. Determining the transaction price often requires judgment, based on an assessment of contractual terms and business practices. It further includes review of variable consideration such as discounts, sales returns, price protection, and rebates, which is estimated at the time of the transaction. In addition, the transaction price does not include an estimate of the variable consideration related to sales-based royalties. Sales-based royalties are recognized as the sales occur.

Allocating the transaction price. Allocating the transaction price requires that we determine an estimate of the relative stand-alone selling price for each distinct performance obligation. Determining the relative stand-alone selling price is inherently subjective, especially in situations where we do not sell the performance obligation on a stand-alone basis (which occurs in the majority of our transactions). In those situations, we determine the relative stand-alone selling price based on various observable inputs using all information that is reasonably available. Examples of observable inputs and information include: historical internal pricing data, cost plus margin analyses, third-party external pricing of similar or same products and services such as software licenses and maintenance support within the enterprise software industry. The results of our analysis resulted in a specific percentage of the transaction price being allocated to each performance obligation.

Determining the Estimated Offering Period. The offering period is the period in which we offer to provide the future update rights and/or online hosting for the game. Because the offering period is not an explicitly defined period, we must make an estimate of the offering period for the service-related performance obligations (i.e., future update rights and online hosting). Determining the Estimated Offering Period is inherently subjective and is subject to regular revision. Generally, we consider the specified contract period of our software licenses and therefore, the offering period is estimated to be over the term of the license. We recognize revenue for future update rights and online hosting performance obligations ratably on a straight-line basis over this period as there is a consistent pattern of delivery for these performance obligations.

Software Development Costs

The Company expenses software development costs, including costs to develop software products or the software component of products to be sold, leased, or marketed to external users, before technological feasibility is reached. Technological feasibility is typically reached shortly before the release of such products. Software development costs also include costs to develop software to be used solely to meet internal needs and cloud-based applications used to deliver our services. The Company capitalizes development costs related to these software applications once the preliminary project stage is complete and it is probable that the project will be completed, and the software will be used to perform the function intended. Capitalization ends, and amortization begins when the product is available for general release to customers.

Stock-Based Compensation

The Company accounts for equity instruments issued to employees in accordance with the provisions of ASC 718 Stock Compensation (ASC 718) and Equity-Based Payments to Non-employees pursuant to ASC 2018-07 (ASC 2018-07). All transactions in which goods or services are the consideration received for the issuance of equity instruments are accounted for based on the fair value of the consideration received or the fair value of the equity instrument issued, whichever is more reliably measurable. The measurement date of the fair value of the equity instrument issued is the earlier of the date on which the counterparty's performance is complete or the date at which a commitment for performance by the counterparty to earn the equity instruments is reached because of sufficiently large disincentives for nonperformance.

Basic and Diluted Loss Per Share

Basic earnings per share (“EPS”) are computed by dividing net income (the numerator) by the weighted average number of common shares outstanding for the period (the denominator). Diluted EPS is computed by dividing net income by the weighted average number of common shares and potential common shares outstanding (if dilutive) during each period. Potential common shares include stock options, warrants and restricted stock. The number of potential common shares outstanding relating to stock options, warrants and restricted stock is computed using the treasury stock method. For the periods presented, potential dilutive securities had an anti-dilutive effect and were not included in the calculation of diluted net loss per common share.

Income Taxes

Deferred tax assets and liabilities are recognized for the future tax consequences attributable to differences between the financial statement carrying amounts of existing assets and liabilities and their respective tax bases. Deferred tax assets and liabilities are measured using enacted tax rates expected to apply to taxable income in the years in which those temporary differences are expected to be recovered or settled. A valuation allowance is provided for significant deferred tax assets when it is more likely than not, that such asset will not be recovered through future operations.

Uncertain Tax Positions

In accordance with ASC 740, “Income Taxes” (“ASC 740”), the Company recognizes the tax benefit from an uncertain tax position only if it is more likely than not that the tax position will be capable of withstanding examination by the taxing authorities based on the technical merits of the position. These standards prescribe a recognition threshold and measurement attribute for the financial statement recognition and measurement of a tax position taken or expected to be taken in a tax return. These standards also provide guidance on de-recognition, classification, interest and penalties, accounting in interim periods, disclosure, and transition.

Various taxing authorities may periodically audit the Company’s income tax returns. These audits include questions regarding the Company’s tax filing positions, including the timing and amount of deductions and the allocation of income to various tax jurisdictions. In evaluating the exposures connected with various tax filing positions, including state and local taxes, the Company records allowances for probable exposures. A number of years may elapse before a particular matter, for which an allowance has been established, is audited and fully resolved. The Company has not yet undergone an examination by any taxing authorities.

The assessment of the Company’s tax position relies on the judgment of management to estimate the exposures associated with the Company’s various filing positions.

Recently Adopted Accounting Standards

In December 2023, the FASB issued Accounting Standards Update (“ASU”) 2023-09, “Income Taxes (Topic 740): Improvements to Income Tax Disclosures.” ASU 2023-09 requires entities to further enhance their income tax disclosures, primarily through the standardization and disaggregation of information within an entity’s effective tax rate reconciliation categories and income taxes paid by jurisdiction. The guidance will be effective for fiscal years beginning after December 15, 2024 with early adoption permitted. The guidance is required to be applied on a prospective basis with the option to apply the guidance retrospectively. The Company is currently evaluating whether it will adopt the guidance prospectively or retroactively and the impact the guidance will have on its financial statement disclosures.

There are no other recently issued accounting pronouncements that the Company has yet to adopt that are expected to have a material effect on its financial position, results of operations, or cash flows.

WEWARDS, INC. 10-K/A