> For the complete documentation index, see [llms.txt](https://qualitax.gitbook.io/interop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qualitax.gitbook.io/interop/solutions-providers/ant-group.md).

# Ant Group

## 1. Problems/Challenges it aims to solve

***

## 2. Solutions

***

**ODATS (Open Data Access Trusted Service):** ODATS has been adapted and validated in various use cases including financial services and logistics.

**AntChain Bridge:**&#x20;

## 3. Target Customers

***

## 4. Key Points <a href="#id-4.-key-points" id="id-4.-key-points"></a>

***

***TO REVIEW - TRANSLATED FROM CHINESE***

AntChain Bridge interprets cross-chain interoperability on two levels: communication and trustworthiness, i.e., the goal of cross-chain is to achieve trustworthy communication between blockchain entities.

In the architecture of AntChain Bridge, the relay needs to interact with the blockchain, and the communication protocols of heterogeneous chains vary widely, unable to uniformly adapt, therefore AntChain Bridge abstracts out a blockchain bridge component (Blockchain Bridge Component, BBC) to solve the communication problems between the blockchain and the cross-chain network.

Every kind of heterogeneous chain that wants to connect to the AntChain Bridge cross-chain network needs to implement a set of standard blockchain bridge components, which can be divided into on-chain and off-chain parts, including off-chain plugins and system contracts. Off-chain plugins need to be developed based on the SDK, while the on-chain part is usually a smart contract that requires the implementation of specific interfaces and logic. To reduce development difficulty, we offer an implementation in the Solidity version.

AntChain Bridge provides developers with SDK, manuals, and system contract templates to help developers complete plugin and contract development. At the same time, AntChain Bridge offers plugin services (PluginServer) to run plugins. The plugin service is an independent service with plugin management and the function to respond to relay requests.

In the current engineering implementation, the BBC off-chain part is implemented in the form of plugins. AntChain Bridge has implemented a set of SDKs. By implementing the interfaces (SPI) stipulated in the SDK, a plugin package can be generated through simple compilation. Plugin service (PluginServer, PS) can load BBC off-chain plugins; details can be referred to in the plugin service introduction document.

## 5. People

***

Geoff Jiang, President of Digital Technologies Business Ant Group

Yan Ying, Technical Director of AntChain

Li Ming, Chairman of the IEEE Computer Society Blockchain and Distributed Ledger Technology Standards Committee.

## 6. Resources

***

<https://github.com/AntChainOpenLabs/AntChainBridgePluginSDK>

<https://jcupt.bupt.edu.cn/EN/article/downloadArticleFile.do?attachType=PDF&id=1443>


---

# 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://qualitax.gitbook.io/interop/solutions-providers/ant-group.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.
