> For the complete documentation index, see [llms.txt](https://whitepaper.venus.vip/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.venus.vip/venus-technology-principle.md). # Venus Technology Principle The Venus Foundation is solely responsible for the development of Venus. The Venus Foundation will carry out full-stack development based on multiple public chain smart contract modules according to the ecological needs of Venus. In the technical level Venus into both scalability, security, decentralization three characteristics, integrated with the current BSC chain throughput performance and processing performance advantages, can provide users with second-level interactive response, around the system architecture of Venus, mainly divided into three parts, respectively, the hub system, sub-ecosystem and DApp application integration architecture. The sub-ecosystem provides collaborative consensus for the operation of Venus, stabilizes the operation of the economic model, and assists developers in issuing exclusive passes; the DApp application integration architecture addresses NFT display, transaction visualization, and business process execution according to the user's usage scenarios. --- # 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://whitepaper.venus.vip/venus-technology-principle.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.