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

# Spot

Trade supported tokenized stock assets against tUSDG through Elvo Exchange’s live internal Spot market.

## Spot

Trade supported tokenized stock assets against tUSDG through Elvo Exchange’s live internal Spot market.

### What Is Elvo Spot?

Elvo Spot is the currently executable trading product on Elvo Exchange.

Spot trading allows you to buy and sell supported tokenized stock assets using balances held in your Elvo account.

[**Explore Spot Markets →**](https://elvo.exchange/markets)

Unlike the Perpetual and Earn products, which are currently preview experiences, **Spot trading is live and supports real order execution within Elvo Exchange**.

***

### Supported Spot Markets

Elvo currently supports the following Spot markets:

| Asset     | Market        |
| --------- | ------------- |
| **NVDA**  | NVDA / tUSDG  |
| **TSLA**  | TSLA / tUSDG  |
| **AAPL**  | AAPL / tUSDG  |
| **MSFT**  | MSFT / tUSDG  |
| **META**  | META / tUSDG  |
| **GOOGL** | GOOGL / tUSDG |
| **AMZN**  | AMZN / tUSDG  |
| **COIN**  | COIN / tUSDG  |
| **SPY**   | SPY / tUSDG   |
| **QQQ**   | QQQ / tUSDG   |

All currently supported Elvo Spot markets use **tUSDG** as the quote asset.

***

### How Spot Trading Works

Elvo operates its own internal Spot order book and matching system.

The execution flow is:

**User Order → Elvo Order Book → Elvo Matching Engine → Elvo Account Settlement**

When you place an order, Elvo matches it against executable liquidity available within the Elvo Spot market.

Your order is not forwarded to another exchange for execution.

***

### Internal Elvo Liquidity

The Elvo Spot order book contains executable orders available within Elvo Exchange.

Liquidity can include:

* User Limit orders
* Internal Elvo liquidity orders

Market orders and crossing Limit orders can execute against this liquidity.

If the requested quantity is larger than the liquidity available at one price level, the order may execute across multiple levels.

***

### External Market Data

Elvo uses external market data to provide additional market context.

This can include:

* Reference prices
* Charts
* Market statistics
* 24-hour market information
* Reference price protection
* Historical market context

External reference data is separate from Elvo execution.

> External market liquidity is not treated as Elvo liquidity, and customer orders are not routed to the external reference provider.

***

### The Spot Trading Terminal

Select a supported market to open its trading terminal.

The terminal can display:

* Current market information
* Price chart
* Elvo order book
* Recent Elvo trades
* Buy and Sell controls
* Available balances
* Order type selection
* Estimated trading fees
* Open Orders
* Order History
* Trade History
* TP / SL activity

Start from:

[**Markets →**](https://elvo.exchange/markets)

***

### Buy and Sell

#### Buy

A Buy order uses your available tUSDG balance to purchase the selected Spot asset.

#### Sell

A Sell order uses your available balance of the selected asset.

Elvo checks your available balance before accepting an order.

Funds already reserved for another active order may not be available for a new trade.

***

### Market Orders

A **Market order** attempts to execute immediately against available Elvo order-book liquidity.

Market orders use **Immediate or Cancel (IOC)** behavior.

This means:

* Available quantity may execute immediately
* The order can consume multiple price levels
* Any unexecuted remainder does not remain resting on the order book
* The final average execution price may differ from the current reference price

Market orders prioritize immediate execution over selecting an exact execution price.

***

### Limit Orders

A **Limit order** allows you to specify the price at which you are willing to buy or sell.

If the order does not immediately cross existing liquidity, it can remain on the Elvo order book.

A working Limit order may remain active until it is:

* Filled
* Canceled
* Replaced or amended
* Otherwise completed according to its order conditions

A Limit order that immediately crosses available liquidity may execute as a taker.

***

### Take Profit and Stop Loss

Elvo Spot also supports conditional orders.

#### Take Profit

A Take Profit order waits for its configured trigger condition before progressing to execution.

#### Stop Loss

A Stop Loss order waits for its configured stop condition before progressing to execution.

These conditions are monitored by Elvo rather than requiring the user to remain on the trading page.

***

### OCO

Elvo supports **OCO — One Cancels the Other** conditional protection.

An OCO setup combines two opposite conditional outcomes, typically:

**Take Profit + Stop Loss**

When one eligible leg triggers, the paired sibling is prevented from independently progressing as another active triggered order.

***

### Order Book

The Elvo Spot order book represents actual executable Elvo liquidity.

#### Bids

Orders to buy the asset.

#### Asks

Orders to sell the asset.

Price levels and quantities can change as orders are:

* Submitted
* Filled
* Partially filled
* Canceled
* Replaced

The order book updates as trading activity changes.

***

### Recent Trades

The Recent Trades section represents completed executions within the Elvo Spot market.

These are Elvo internal fills.

They should not be confused with external reference-market trades used for broader market information.

***

### Partial Fills

An order may execute through more than one fill.

For example, a 10-unit order could execute as:

**2 units at Price A**\
**3 units at Price B**\
**5 units at Price C**

Elvo records these individual executions while also maintaining the overall order status.

This is why an order can temporarily show as **Partially Filled**.

***

### Spot Trading Fees

Current Elvo Spot trading fees are:

| Role      | Fee       |
| --------- | --------- |
| **Maker** | **0.05%** |
| **Taker** | **0.10%** |

The fee is determined by the actual liquidity role of each fill.

A Limit order is not automatically a maker order. If it immediately consumes existing liquidity, the resulting execution can be treated as taker activity.

See:

[**Fees →**](https://elvo.exchange/orders)

***

### Trading Balances

Elvo Spot trading uses your exchange account balances.

Your asset balance can include:

#### Available

Funds currently available for new trades or other supported account actions.

#### Locked

Funds reserved for active trading orders.

When an order is completed or canceled, unused reserved funds are released according to the final order result.

View balances from:

[**Assets →**](https://elvo.exchange/assets)

***

### Trading Activity

Your Spot trading activity can be reviewed through:

[**Orders →**](https://elvo.exchange/orders)

Available views include:

#### Open Orders

Orders that are currently active.

#### Order History

Orders that have reached a final state.

#### Fills

Individual completed trade executions.

#### TP / SL

Conditional order activity.

***

### Completed Spot Orders

Successfully filled orders can have a dedicated Elvo order record.

The record may include:

* Order ID
* Market
* Side
* Order type
* Time in force
* Filled quantity
* Original quantity
* Average execution price
* Limit price, when applicable
* Creation time
* Completion time

***

### No Blockchain Transaction for Each Trade

Elvo Spot orders are executed internally.

A normal Spot trade does not require:

* A blockchain transaction
* Gas payment for each trade
* A wallet confirmation for each Buy or Sell
* A blockchain transaction hash for the completed order

Blockchain transactions are used separately for account funding operations such as deposits and withdrawals.

For Spot trading, the **Order ID and Elvo execution records** are the relevant transaction references.

***

### Spot vs. Perpetual

Elvo Spot and Perpetual currently have different product states.

| Feature         | Spot                     | Perpetual           |
| --------------- | ------------------------ | ------------------- |
| Market data     | Live                     | Live reference data |
| Order execution | **Enabled**              | **Coming Soon**     |
| Buy / Sell      | **Enabled**              | Preview only        |
| Positions       | Spot balances            | Not enabled         |
| Margin          | Not applicable           | Preview only        |
| Liquidation     | Not applicable           | Not enabled         |
| Settlement      | **Elvo Spot settlement** | Not enabled         |

If you want to execute a trade today, use **Spot**.

[**Open Spot Markets →**](https://elvo.exchange/markets)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://elvo-exchange.gitbook.io/elvo-exchange-docs/spot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
