# Features

The Orbit Bridge system has Governance groups composed of the roles: Operator and Validator. 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 are recorded on Orbit Chain, they are transparent and trustworthy.

### Operator

Relays the information needed by Governance for actual operation. Each piece of data signed by the Validators is assembled and executed by forming a transaction that runs on the chain. Collect signatures of validators gathered in OrbitChain MIG (MultisigWallet) and generate a transaction of withdrawal from Vault or mint from Minter.

### Validator

A group of Validators constituting Governance verify the TX generated by each chain and record verification in the chain to reach a consensus.

### Vault

The place where assets are deposited into when a bridging transaction occurred on Native Chain(Origin Chain).

### Minter  

Receive a request to withdraw from a chain that oToken(a token bridged via Orbit Bridge) was minted, or mint an oToken to another chain from a chain where the token is originally issued on.

<br>


---

# 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/features.md?ask=<question>
```

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.