> For the complete documentation index, see [llms.txt](https://docs.vialabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vialabs.io/security/network-validator-intro.md). # Network Validator Intro VIA Labs' network validators are off-chain components that ensure secure and efficient cross-chain communication. They play a key role in verifying and relaying transactions between different blockchains. ### **What do they do?** * **Relay Transactions**: VIA Labs validators verify transactions on one blockchain and relay them to another, acting as intermediaries. * **Security**: They ensure the accuracy and authenticity of transactions, maintaining the integrity of cross-chain operations. * **Consensus Mechanism**: Validators follow specific rules to agree on transactions and resolve disputes, typically using Proof of Liquidity (PoL) or Proof of Authority (PoA). In this case, both instances are used. * **Decentralization**: Multiple validators enhance network resilience by preventing any single party from controlling the system. --- # 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.vialabs.io/security/network-validator-intro.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.