> For the complete documentation index, see [llms.txt](https://docs.yarchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yarchain.org/whitepaper/yar-architecture.md). # YAR architecture YAR consists of three decentralized solutions - YAR chain, YAR protocol, and YAR vault: * The **YAR chain** ensures the operation of smart contracts; * The **YAR protocol** stores a set of connectors that ensure the interaction of smart contracts deployed in the YAR chain with external sources, objects, and subjects of those sources; * The **YAR vault** creates and stores private TSS keys YAR protocol. YAR allows the developer to create smart contracts by connecting any number of available blockchains to them, and work with coins, tokens, smart contracts, and any other objects and entities as if all this was directly available in the ecosystem. At the same time, the requirements of reciprocity, consistency, and decentralization are observed. An important aspect, by creating a smart contract in YAR, the results of its work can be used in any other connected blockchain, which will lead to an increase in the interoperability of all blockchain networks in the future. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.yarchain.org/whitepaper/yar-architecture.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.