# Layer2 Chain As we have discussed in this paper, the current advertising value chain is riddled with fraudulent ad-impressions, bot traffic and other problems. A truly participatory approach of building a decentralized ad infrastructure that generates value for all participants (including creators & consumers) while being secure and tamper-proof demands first-principles thinking and composing the said infrastructure from the basic building blocks of blockchain & web3 technology. Such an approach also provides the required flexibility to make tradeoffs between security, scalability and decentralization for the problem in hand. For example, use case specific validation is required to avoid ad asset duplication, which can lead to significant bot activity towards fraudulent ad views & impressions. Similarly, most brands have an evolving set of requirements around brand identity and moderation of the associated content which will get more stringent over time. Furthermore, much of the history of ad-bidding could be viewed as IP (ex: participation history in ascending bids for a specific auction or publisher site). This includes providing an environment which allows for selecting the right balance between governance, confidentiality, compliance, and ad-impression validation and verification. As a result, Cros will be building a "L2 chain" those processes and executes ad-related transactions while also submitting an aggregation of its most recent blocks to the principal chain. Cros Network chain will be described and specified in depth in a white paper that will be released soon. --- # 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/side-chain.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.