# Token Utility Cros Chain is a cutting-edge Ethereum Layer 2 and AI platform for in-game advertising; connecting advertisers, developers, and 3 billion players (#DePIN). The $CROS token has four distinct utility functions: Staking, Validation, Governance, and Payments.\ \ Cros revenue is generated from in-game ad impressions like Google, Meta, TikTok, etc. Ad revenues are then shared between Cros, game developers, and billions of players. $CROS token has to be staked: * By game players and developers to earn ad revenues. * By advertisers paying for ads with $CROS token to get discounts and cashback. * By community, investors, and partners to participate in Cros governance. * By validators to validate ad impressions on Cros L2 chain. The digital cryptographically secured utility token ($CROS Token) is a major component of the ecosystem on the Cros Network. $CROS Token will be issued on the Ethereum blockchain as ERC-20-compliant digital tokens. Its primary function is to facilitate smooth operations within the network, and it is intended solely for use as a utility token. It will allow token holders to stake the token and earn rewards during the initial network bootstrapping phase. The token holders will play a critical part in the governance and evolution of the network and the overall ecosystem. They will be able to propose and vote on changes to the network’s development including parameters such as Payments, Staking, Liquidity, and ad-revenue distribution between Cros, Game Developers, and Gamers. --- # 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://docs.cros.world/usdcrs-tokenomics/token-utility.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.