> For the complete documentation index, see [llms.txt](https://docs.vdex.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdex.trade/introduction/core-features/sub-millisecond-finality.md).

# Sub-Millisecond Finality

VDEX transactions execute directly between market participants, not via a central hub. The elimination of middlemen accelerates trading speeds to the theoretical limit. The removal of wallet pop-ups and VPN requirements further hasten settlement time.

The finality benchmark assumes that participants are engaging in co-geographically located clients. Distance to counterparty will proportionally increase settlement latency. As network participation increases, VDEX's intelligent routing will match participants to minimize individual and overall execution time.

Compared against this benchmark, VDEX transactions settle 200x faster than Hyperliquid, 400x faster than Solana, and 12,000 faster than Ethereum. As compared to peer-to-peer direct settlement, excessive blockchain latencies persist in spite of efforts to centralize validator sets.


---

# 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.vdex.trade/introduction/core-features/sub-millisecond-finality.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.