> For the complete documentation index, see [llms.txt](https://docs.seda.xyz/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seda.xyz/home/archvie/seda-primer/fast-settlement-and-horizontally-scalable.md).

# Fast Settlement & Horizontally Scalable

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfBsjIiV3h8vPJp0lcFlu0fzH-n7bpP2c4gQEYoDA6WVQdibi53fwHV_5Zty3LXl5JNLtNw7FGIOByMo3dUi04J41j1b1NUyAySmrU_q7pX0tO4cofwPLJ-PbrELe6NSsbX6iLv?key=h0ufnoXm9WpA6FLzGDL0I2bS" alt=""><figcaption></figcaption></figure>

SEDA’s efficiency is determined by its Time To Finality (TTF), which indicates when a data request’s outcome is irreversible. TTF measures the interval between the data request initiation and the definitive network response in the oracle realm. Cross-chain solver verification on launch is estimated to be <15 seconds, whereas current estimates for existing solutions are several minutes to 2 hours.

Efficient workload distribution drives SEDA's scalability. SEDA minimizes on-chain operations without compromising security by executing data requests off-chain and in parallel. Specific factors, like data source response time, destination network block time and originating network congestion, will influence TTF for platforms like SEDA.


---

# 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://docs.seda.xyz/home/archvie/seda-primer/fast-settlement-and-horizontally-scalable.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.