> For the complete documentation index, see [llms.txt](https://docs-core.allbridge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-core.allbridge.io/product/how-does-allbridge-core-work/messaging-protocols.md).

# Messaging protocols

Messaging is the middle step in the Allbridge Core transfer flow. Every pool-based transfer follows the same sequence:

1. Swap on the source chain: the user’s stablecoins are deposited into the source pool and swapped into vUsd.
2. Message sent to the destination chain: this message carries the information needed to complete the transfer.
3. Swap on the destination chain: the destination pool swaps vUsd into the local stablecoin and sends it to the recipient.

Messaging does not move tokens across chains—it only provides the instructions that allow the destination chain to finalize the transfer.

## Messaging Options

Depending on the route, the UI may allow users to choose between different messaging providers. These include:

* Allbridge Messaging — a proprietary messaging layer optimized to be cost-effective.
* Wormhole Messaging — uses the Wormhole network to pass the transfer message between chains. It is more expensive and not available on all blockchains supported by Allbridge.

The UI shows which options are available for the selected route. Take note on the relayer fee and expected transfer time difference when you select a particular messaging protocol.

## CCTP and OFT

Although CCTP, CCTP V2, and OFT appear in the same UI area as messaging options, they are not messaging choices for pool-based transfers.

They represent separate transfer mechanisms that bypass Allbridge liquidity pools entirely:

* CCTP / CCTP V2 use Circle’s official USDC burn-and-mint flow.
* OFT (Omnichain Fungible Token) uses [LayerZero](https://layerzero.network/)’s OFT standard

These routes do not use the swap–message–swap process and do not involve Allbridge Core pool mechanics.


---

# 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:

```
GET https://docs-core.allbridge.io/product/how-does-allbridge-core-work/messaging-protocols.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.