# Real-Time On-Chain Execution

## Instant finality with near-zero latency

Liqui executes all trades, orders, and contract interactions natively on-chain - with no centralized order matching or off-chain intermediaries.

{% hint style="info" %}
Powered by the high-speed MegaETH infrastructure, transactions reach instant finality, enabling sub-second DeFi performance with full transparency and verifiability.
{% endhint %}

## How It Works

### Native Execution Layer

All core logic - including spot trading, margin, Launchpad participation, and staking - is encoded directly into smart contracts on MegaETH and executed in real time.

* No delays from centralized relayers
* Every order = 1 on-chain transaction
* MegaETH finalizes blocks in milliseconds

### Instant Finality within Network

* Once a trade is submitted, it is confirmed, settled, and irreversible in under 1 second.
* Protected from pre-trade exploitation
* Transactions are final and cannot be reverted post-confirmation
* Execution with deterministic, predictable results

### Minimal Latency

**Average transaction latency remains under 10ms, achieved through:**

* L2-native execution
* Local node-level optimization
* Offloaded computation via the MegaETH VM

{% hint style="info" %}
Multi-step orders - such as margin trades, liquidity routing, and LP updates - are composed into a single atomic transaction, executed and finalized as one.
{% endhint %}


---

# 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.liqui.io/real-time-on-chain-execution.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.
