# Background and Exploratory Notes We introduce a pioneering new system architecture that is **the new standard for blockchain-powered artificial intelligence**. Around this standardization, we have three primary parties: * **AI models** that are available on the Nesa system by the model developers * **Users of Nesa** who need affordable, private inference * **Node runners** who execute the decentralized jobs on the Nesa system, including validation, inference, and more At its foundation, the Nesa system is designed to streamline the AI computation process by providing a consistent set of rules and execution protocols, which every participating parties must follow. This not only guarantees that all nodes produce identical results given the same model parameters and input data, but also relieves node operators from the complexity involved in setting up execution environments, facilitating easier adoption and participation in our network. In this section, we detail how [users who need private inference](/nesa/background-and-exploratory-notes/users-why-do-we-need-private-inference.md) can leverage Nesa to get inference results by [leading AI models](/nesa/background-and-exploratory-notes/ai-models-repository-standardization-uniformity.md), which are powered by our [node runners](/nesa/background-and-exploratory-notes/node-runners-doing-inference-and-earning-usdnes.md). We will soon provide a flow chart of the system interaction here. --- # 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.nesa.ai/nesa/background-and-exploratory-notes.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.