# How it works ![Orbit Bridge system structure diagram](https://516479309-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJyg-Bbo5X7MHxbgayB%2F-MLg8nnpWef2o2Dl0FdB%2F-MLg97rOaNp5Zcosnc8j%2Fphoto_2020-11-09%2017.38.41.jpeg?alt=media\&token=8dc2f7fe-6ef5-4cf0-b5e7-fcb44d99ef8d) The Orbit Bridge system has Governance groups comprised of the roles: Operator and Validator. Bridging protocols either use a MPC-based transaction consensus method or a Multi-sig based transaction consensus method. Orbit Bridge uses Multi-sig based transaction consensus. Through this, the Operator, who sends data, and the Validator work together to efficiently and quickly process transactions. Additionally, as the consensus and validation processes happen through transactions on Orbit Chain, they are transparent and trustless. The validators use a separate private channel and a blockchain without central authority to complete their tasks. * Operator * Relays the information needed by Governance for actual operation. * Each piece data signed by the Validators is assembled and executed by forming a transaction that runs on the chain. * Validator * A group of Validators constituting Governance verify the TX generated by each chain and records verification in the chain to reach an consensus. --- # 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://bridge-docs.orbitchain.io/how-it-works.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.