# L1

The NodeKit L1 is a purpose built L1 that acts as a shared common ledger between all of the chains within the Composium. The L1 helps facilitate fee distribution to chains and stakers on the network. We are able to prove cases of fraud through ZK proofs and slash builders on the L1, enabling greater security for the chains within the network.

To be scalable and directly attribute revenue to each chain, blocks are composed of many chunks: one for each chain plus a top-of-block chunk for facilitating atomic transactions. If there are n chains using NodeKit, there will be n+1 chunks in a block.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXekQgHicQeIl5-n2m1dYEcSH3icu4ddqnbmdjSLC5w6-9GiTD6x_CiWwBXIe24W6JR4E4AiB2FbaqMi__UnuYIwvlXXDX21aUQYskTPESc7ID4UNlylBt0311avmxvXn_G2yB6Jaw?key=mcWQm1Amijc8vua1uSfrnrz1" alt=""><figcaption></figcaption></figure>

A crucial element of the chunk based approach is the top-of-block chunk. This chunk is always the first chunk in the block, and is where atomic cross-chain transactions are handled. In this chunk, atomic bundles are included, and the Javelin builder guarantees the atomic execution of all bundles before including it in the chunk.\
There is one rest-of-block (RoB) chunk for each chain on the network. This is filled with the transactions for each chain that are not involved in a cross-chain bundle. The chains have sovereignty over how these blocks are built. This can allow for FCFS ordering, privacy, or any other custom feature to be added to a chain’s blocks with ease.

<br>


---

# 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://nodekit.gitbook.io/nodekit-documentation/architecture/l1.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.
