> For the complete documentation index, see [llms.txt](https://docs.emc.network/emc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emc.network/emc/products/emc-mainnet/bridge/bridge-mechanism.md).

# Bridge Mechanism

The current threshold for cross-chain transaction execution is **3**, with **4 Relayers** participating in the voting process. To ensure user asset security, each chain’s **Erc20Handler** contract sets a vault address, which is a secure third-party MPC wallet.

When assets are bridged, they are transferred in real time to the vault wallet address; the contracts themselves do not hold large amounts of assets for extended periods. After a user initiates a deposit on the source chain, the Relayers scan the blocks across chains and cast validation votes. Once votes reach the threshold (**3 out of 4**), the target chain contract requests the corresponding token funds from the vault. Subsequently, an **MPC 3-of-5** automated risk control approval is performed in the vault before finalizing the asset release on the target chain.

***

### Arbitrum One Erc20Handler Vault Address

Vault Wallet Address: 0xd65951a9689193e7636549D49F911C70f1762842

<https://arbiscan.io/address/0xd65951a9689193e7636549D49F911C70f1762842>

### Edge Matrix Chain Erc20Handler Vault Address

Vault Wallet Address: 0xd65951a9689193e7636549D49F911C70f1762842

<https://emcscan.com/address/0xd65951a9689193e7636549D49F911C70f1762842>

### Base Erc20Handler Vault Address

Vault Wallet Address: 0xd65951a9689193e7636549D49F911C70f1762842

<https://basescan.org/address/0xd65951a9689193e7636549D49F911C70f1762842>

{% hint style="warning" %}
Both Arbitrum One and EMC Mainnet utilize the same vault address, managed via an MPC-based multi-chain wallet solution.
{% endhint %}


---

# 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.emc.network/emc/products/emc-mainnet/bridge/bridge-mechanism.md?ask=<question>&goal=<endgoal>
```

`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.