# Bridge Operator * Operators act automonously from Governance to make all bridging tasks possible by continously managing the tasks of each chain. **Operating Process** * Transaction information relay for a Vault * Transfers to Orbit Chain's Orbit Hub the transaction information (transaction hash, method, event, memo, etc.) that each chain has for Vault so that Validators can reach consensus quickly. * Transaction information relay for Minters * Transfers to Orbit Chain's Orbit Hub the transaction information (transaction hash, method, event, memo, etc.) that each chain has for Vault so that Validators can reach consensus quickly. * Process information relay for building a multiple signature wallet transaction in each bridge contract * Suggest transaction object for each chain specification (sequence format , transaction fee situation etc) and support to successful consensus * Executes the agreed transactions on each chain * Through Orbit chain, the Validator signs the transaction based on the completed transaction information so that it can run on each chain. --- # 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/bridge-operator.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.