> 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/bridging-approaches/third-party-bridge.md).

# Third Party bridge

## In the context of permissioned L1s ?

## In the context of Rollups

##

**When needed:** 

Rollups that do not share a DA layer or those that share a DA layer but have different execution layers (virtual machines) will still need to be connected via third-party messaging bridges.

Celestia rollups will need a messaging bridge to be connected to rollups built on EigenDA OR Rollup A using EVM for execution, and Rollup B using the SVM for execution, where both use Celestia for DA will still need a third-party bridge for message passing.

**When not needed:**

Trust-minimized cross-chain communication is possible across rollups with a common consensus and data availability (DA) layer, removing the need for third-party bridges for inter-rollup connectivity.

These rollups will maintain a native bridge with the DA layer, which will serve as a central hub linking all these chains together.

 Source: @ayyyeandy from The Rollup


---

# 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/bridging-approaches/third-party-bridge.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.