# 5.2 Relayer

## Introduction

The Inter-Blockchain Communication (IBC) protocol is an end-to-end, connection-oriented, stateful protocol that enables reliable, ordered, and authenticated communication between heterogeneous blockchains with an unknown and dynamic topology. \
\
IBC allows blockchains to interact with each other and supports a wide range of cross-chain applications, including token transfers, atomic swaps, multi-chain smart contracts, and data and code sharding.

IBC applications are written as self-contained modules that don't need to be concerned with the low-level details of clients, connections, and proof verification. Key components of IBC include:

1. Clients: On-chain light clients that track the consensus states of other blockchains, along with the proof spec necessary to properly verify proofs against the client's consensus state.
2. Connections: Encapsulate two ConnectionEnd objects on separate blockchains, responsible for facilitating cross-chain verifications of IBC state and can be associated with any number of channels.
3. Proofs and Paths: IBC uses proofs and paths to communicate between blockchains, with relayers monitoring updates to paths and relaying messages by submitting data and proofs to the counterparty chain.
4. Capabilities: IBC uses a dynamic capability store for module authentication on ports and channels, ensuring that only modules with appropriate permissions can use them.
5. Ports and Channels: IBC applications communicate with other modules on different blockchains by sending, receiving, and acknowledging packets through channels identified by the (channelID, portID) tuple.

IBC protocol allows for secure and efficient communication between different blockchain networks, paving the way for interoperability and collaboration in the decentralized ecosystem.

### Official IBC Channels for the MEME Network

| source chain-id | source channel | destination chain | destination chain-id | destination channel | IBC                                                                  |
| --------------- | -------------- | ----------------- | -------------------- | ------------------- | -------------------------------------------------------------------- |
| meme-1          | channel-1      | Osmosis           | osmosis-1            | channel-238         | ibc/67C89B8B0A70C08F093C909A4DD996DD10E0494C87E28FD9A551697BF173D4CA |
| meme-1          | channel-8      | Acrechain         | acre\_9052-1         | channel-22          | ibc/CEEC70673977A3DA18BAAC51BDDEF82886CCAF2C4DB7C4B4A43799C63C8D1706 |
| meme-1          | channel-9      | Gravity Bridge    | gravity-bridge-3     | channel-149         | ibc/0EB6D5E44D1587D12E222C1155181884098202F56263795259C53536D07C2E65 |


---

# 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://docs.memenetwork.io/meme-network-whitepaper-v1.0/5.-technology/5.2-relayer.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.