# Code Licensing aarnâ protocol operates across decentralized blockchain networks, utilizing smart contracts deployed on multiple chains. These contracts are self-executing, fully audited, and governed by specific licenses that define the terms of their usage and distribution. The underlying codebase spans several GitHub repositories. Below are the key licenses applicable to different components of the aarnâ ecosystem: * **âtv 802v2 Smart Contracts (Ethereum):** Business Source License 1.1 permits non-commercial use and modification, restricting competitive use for four years, with a transition to the GPL v2.0 License on February 5, 2029​. * **âtv 808 Smart Contracts (Ethereum):** Business Source License 1.1 permits non-commercial use and modification, restricting competitive use for four years, with a transition to the GPL v2.0 License on March 22, 2029​. * **âtv 111 Smart Contracts (Ethereum):** Business Source License 1.1 permits non-commercial use and modification, restricting competitive use for four years, with a transition to the GPL v2.0 License on May 24, 2029​. * **âtv 111 Smart Contracts (Sonic):** Business Source License 1.1 permits non-commercial use and modification, restricting competitive use for four years, with a transition to the GPL v2.0 License on May 17, 2029​. * **âtv 401 Smart Contracts (Arbitrum):** Business Source License 1.1 permits non-commercial use and modification, restricting competitive use for four years, with a transition to the GPL v2.0 License on May 22, 2029​. --- # 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.aarna.ai/resources/code-licensing.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.