> For the complete documentation index, see [llms.txt](https://docs.trueopen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trueopen.ai/reference/resources/faq.md). # FAQ Frequently asked questions about TrueOpen. ## Is TrueOpen a general-purpose EVM chain? No. TrueOpen V1 is a purpose-built Cosmos SDK application chain for AI inference tasks. ## Is AI inference performed on-chain? No. Inference and verification compute run on Cortex Nodes. The chain coordinates selection, deadlines, commitments, accountability, funds, settlement, and finality. ## Are Worker and Verifier different node types? No. They are responsibilities assigned to Cortex Nodes for a particular task. A node may take different responsibilities on different tasks, but cannot be both Worker and Verifier for the same task. ## Does a Builder decide whether a result is valid? No. Builders coordinate proposals and data delivery. Protocol state and accepted on-chain actions determine selection, verdict processing, and settlement. ## Are V1 payments and Task contents private? V1 uses public business-asset accounting and account-bound Sessions. Task inputs, outputs, and evidence travel in plaintext over authenticated TLS, so assigned Builders can read the data they store. The [whitepaper](/whitepaper.md) also discusses private payments and content encryption as broader design goals; those features are outside [V1](/protocol/v1.md). ## Where are API endpoints and network parameters? They will be added to the developer and reference sections after the corresponding public network and interfaces are released. Internal defaults are not treated as public configuration. --- # 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.trueopen.ai/reference/resources/faq.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.