> For the complete documentation index, see [llms.txt](https://kerneldao.gitbook.io/kernel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kerneldao.gitbook.io/kernel/getting-started/kelp/security/cross-chain-architecture.md).

# Cross Chain Architecture

#### Supported Chains:

* Ethereum
* Arbitrum
* Base
* Linea
* Ink
* Mantle

Any rsETH movement from L2 --> L2 is routed through Ethereum. So the actual movement is L2<sub>a</sub> --> Ethereum --> L2<sub>b</sub>

#### Bridge:

* LayerZero (Arbitrum, Base, Ink and Mantle)
* Chainlink's CCIP (Linea)

#### Configuration

Every rsETH LayerZero route enforces 4-of-4 independent DVNs (Canary, Horizen, LayerZero Labs, Nethermind), with 64 confirmations, in a hub-and-spoke topology<br>

* Live on-chain read: EndpointV2.getConfig(oapp, lib, eid, 2) on the OFT Adapter 0x85d456B2DfF1fd8245387C0BfB64Dfb700e98Ef3 returns requiredDVNcount = 4, optionalDVNcount = 0, confirmations = 64 on every route (both directions, including the L2 mint path).<br>
* Independently audit: BailSec conducted a dedicated review of the on-chain DVN-configuration verification script (full report is [available here](https://kerneldao.com/kelp/audits/smartcontracts/Bailsec_rsETH_May_2026.pdf)).

#### Bridge Libraries

Send/receive libraries and executors are explicitly pinned per route in our LayerZero OFT configuration, and are read back live in the getConfig calls above (the lib parameter is the pinned ULN302 send/receive library per route)\
\
Audited by Bailsec as part of the same review as above.<br>

#### Bridge & Mint rate limits

On-chain daily mint caps:

| Chain    | Contract                                             | Getter                | Value           |
| -------- | ---------------------------------------------------- | --------------------- | --------------- |
| Ethereum | rsETH 0xA1290d69c65A6Fe4DF752f95823fae25cB99e5A7     | maxMintAmountPerDay() | 5,000 rsETH/day |
| Base     | RSETHPool 0x291088312150482826b3A37d5A69a4c54DAa9118 | dailyMintLimit()      | 500 rsETH/day   |
| Linea    | RSETHPool 0x057297e44A3364139EDCF3e1594d6917eD7688c2 | dailyMintLimit()      | 500 rsETH/day   |
| Ink      | RSETHPool 0xcD464f47Cb8AEd70F7e85dd5eca20Db021B5246B | dailyMintLimit()      | 500 rsETH/day   |
| Mantle   | RSETHPool 0xb6EF312b80fAcBbECa42dDF8b47934a762557048 | dailyMintLimit()      | 500 rsETH/day   |

Note: Arbitrum uses the same LayerZero OFT as every other route (item 1). Its RSETHPool behaves more like a swap pool than a mint pool — it dispenses rsETH from its held OFT balance in exchange for deposits rather than minting new supply — so the effective daily throughput is bounded by the rsETH OFT supply within the pool.


---

# 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://kerneldao.gitbook.io/kernel/getting-started/kelp/security/cross-chain-architecture.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.