> For the complete documentation index, see [llms.txt](https://docs.meter.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meter.io/passport/meter-passport-architecture.md).
# Meter Passport Architecture
***NOTE:** The current version of Meter Passport is V2.0, its security audit is available* [*here*](https://github.com/meterio/Passportv2Contracts/tree/main/audit)*.*
One of Meter's goals is maximizing interoperability with other public blockchains. Meter Passport is a multi-chain router that enables smart contracts to both transfer assets and communicate across blockchains.
It can transfer native tokens, and tokens in various token standards like ERC20, ERC721, ERC1155 in addition to passing arbitrary generic messages between blockchains.
The overall Architecture is as follows;
A user transferring tokens from ChainA to ChainB, first deposits the tokens into the bridge contract of ChainA. The contract locks the tokens on ChainA, emitting an event once deposit is successful.
The relayers, off-chain operators of the system, will listen to these events and create a relay transaction to the relay chain. The Relayers will sign the data of the deposit and submit their signatures on the relay chain. Once the threshold is met, one of the relayers or any user can collect all the signatures and send them to Chain B. The smart contract on ChainB will validate again all the signatures and the deposit data and then release the fund on ChainB.
The initial implementation of Meter Passport was further developed on top of Chainsafe's multisig based v2 bridge contract. Operational wise it is secured by five relayers including **Protofire, Harshquark, Wetez, InfinityStones, and Meter Foundation.**
---
# 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.meter.io/passport/meter-passport-architecture.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.
