> For the complete documentation index, see [llms.txt](https://spire-docs.gitbook.io/spire/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spire-docs.gitbook.io/spire/da-builder/getting-started/overview.md).

# Overview

DA Builder is designed to work with L2 chains and entities that consistently post transactions. It provides:

* **Transaction Aggregation**: Combines multiple transactions into a single on-chain transaction
* **Cost Optimization**: Reduces gas costs by sharing execution costs across multiple users
* **Seamless Integration**: Near drop-in replacement for existing transaction submission
* **Real-time Tracking**: Monitor transaction status through our RPC endpoints

Here's how DA Builder works at a high level:

1. **Transaction Submission**: Users submit transactions to DA Builder's RPC endpoint using `eth_sendRawTransaction`
2. **Request ID Generation**: DA Builder returns a **DA Builder Request ID** for tracking (not an immediate blockchain hash)
3. **Aggregation**: DA Builder collects multiple transactions and combines them into a single transaction
4. **On-chain Submission**: The aggregated transaction is submitted to the blockchain, including any contract calls made by the original transactions to rollup inboxes, etc.
5. **Status Tracking**: Users track their transaction status using the DA Builder Request ID with `eth_getTransactionReceipt` until they receive the actual blockchain transaction receipt which contains the onchain transaction hash


---

# 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://spire-docs.gitbook.io/spire/da-builder/getting-started/overview.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.