# L1 Contracts

Cero provides settlement of transactions onto L1 by grouping them together into batches. These batches belonging to different Rollups are clubbed into sequences which is then pushed onto the specific L1 in intervals by the chosen sequencers. Submitted sequence of batches can be later referred by the Rollup contracts for the on-chain execution that needs to follow. Cero employs a number of L1 contracts for settlements of the batches of transactions in a verifiable manner. These contracts are as follows,

1. Ownership Contract: Used for declaring the owner account.&#x20;
2. AdminManager: To store and declare Admin and Manager accounts for ACL.&#x20;
3. CeroSharedSequence: To manage all the function used in the sequencing based function.&#x20;
4. ValidatorFacet: To manage validator based address. Have validator based CRUD operations.&#x20;
5. EmergencyManager: To manage an emergency state based on per unique rollup id. Has functions like Activate and Deactivate.&#x20;
6. RollupManagerFacet: Is used for rollup management based CRUD operations.
7. DiamondLoupeFacet: To manage the delete, update, add function for facets.&#x20;


---

# 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.cero.network/architecture/l1-contracts.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.
