> For the complete documentation index, see [llms.txt](https://docs.zk.link/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zk.link/architecture/settlement-layer.md).

# Settlement Layer

A classic ZK-Rollup network typically selects a single chain, i.e, Ethereum as the settlement layer to verify the proofs and settles the transactions. The settlement layer maintains the security and integrity of off-chain transactions.

In order to securely aggregate liquidity and native assets across L1s and L2s, zkLink introduces two new paradigms of settlement layer deployment solutions to its rollup infra framework - zkLink Nexus and zkLink Origin.

<table data-view="cards"><thead><tr><th></th><th data-hidden></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Working Principal of A Multi-Chain ZK-Rollup</td><td></td><td></td><td><a href="/architecture/settlement-layer/working-principal-of-a-multi-chain-zk-rollup.md">Working Principal of A Multi-Chain ZK-Rollup</a></td></tr><tr><td>Nexus: Settlement on ETH ZK-L2s</td><td></td><td></td><td><a href="/architecture/settlement-layer/nexus-settlement-on-eth-l2s.md">Nexus: Settlement on ETH L2s</a></td></tr><tr><td>Origin: Settlement on ETH and Alt-L1s</td><td></td><td></td><td><a href="/architecture/settlement-layer/origin-settlement-on-eth-and-alt-l1s.md">Origin: Settlement on ETH and Alt-L1s</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zk.link/architecture/settlement-layer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.