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

# TradFi (stocks, oil, indices)

VoltArb is not only crypto-vs-crypto. The same opportunity engine also watches **traditional-finance underlyings** that trade as tokenized stocks, commodity/oil contracts, metals, and equity indices on crypto venues — and labels them **TradFi**.

> Still market intelligence — not investment advice. Tokenized TradFi on crypto exchanges is **not** the same as trading the NYSE/CME directly. Hours, funding, custody, and basis vs the “real” market can all differ.

## What “TradFi” means here

| Bucket                   | Examples (canonical)                                    |
| ------------------------ | ------------------------------------------------------- |
| **Commodities / energy** | WTI, Brent, nat gas, copper                             |
| **Metals**               | XAU, XAG, XPT, XPD (and related tickers)                |
| **Equity indices**       | NAS100, SPX500, US30, DE40, UK100, JP225, …             |
| **Tokenized equities**   | TSLA, AAPL, NVDA, META, COIN, MSTR, … (venue-dependent) |

Tickers are **normalized** across messy venue names (e.g. `TSLAX` → `TSLA`, BingX `NC…` symbols → canonical base) so spreads compare the same underlying.

## Why this exists

Crypto traders already hold accounts on BingX, Gate, Kraken, etc. Those venues list synthetic / tokenized TradFi. Price gaps appear between:

* two crypto venues on the same underlying
* related listings (perp vs spot-style naming)
* occasionally crypto-native metals (e.g. XAUT) vs other gold tickers

Without a TradFi class, those rows drown in meme-coin noise — or get filtered out by crypto-only habits.

## How to use it in the Web Terminal

1. Open [voltarb.com/app](https://voltarb.com/app).
2. Enable the **TradFi** chip in filters (dedicated toggle — easy to miss inside the type scroll).
3. Optionally clear crypto-only arb types if you want a TradFi-focused desk.
4. Read **spread + lifetime + volume** as usual.
5. Open [Opportunity Tracker](/voltarb-docs/english/opportunity-tracker.md) before sizing — books and fees still decide net.

Rows may show a **TradFi** badge in the table/cards.

## Filters & defaults (engine)

TradFi is a **separate route class** from crypto arb types:

* Crypto type chips do not silently include TradFi (and vice versa when you filter carefully).
* Engine defaults lean toward meaningful TradFi edges (order of **\~0.5%** min spread and thousands of USD volume — exact floors can differ for scanner vs alerts).
* Some legs may be marked **indicative** (e.g. certain Orderly-related routes) — treat as signal quality context, not “free money.”

## Telegram alerts

On the **personal bot**, TradFi alerts are **not** the same menu as crypto spreads:

* Separate toggle: TradFi alerts on/off
* Own min spread % and min volume for TradFi
* Defaults are tuned softer than “2% meme filters” — TradFi gaps are often smaller but still tradeable after costs

Configure via bot filter UI (TradFi tab / settings — same place as funding-style dedicated filters).

## Fear checklist (TradFi-specific)

* [ ] Am I trading a **tokenized / synthetic** listing, not the cash equity on a stock broker?
* [ ] Session hours / weekend gaps — TradFi underlyings can behave differently than 24/7 alts.
* [ ] Funding on perps of stocks/indices can dominate a thin spread.
* [ ] Venue naming is ugly — trust VoltArb’s canonical base, then verify on the exchange UI.
* [ ] Tracker net after fees > headline %.

## Related

[Strategies](/voltarb-docs/english/strategies.md) · [Web Terminal](/voltarb-docs/english/web-terminal.md) · [Telegram](/voltarb-docs/english/telegram-bot.md) · [Exchanges](/voltarb-docs/english/exchanges.md) · [FAQ](/voltarb-docs/english/faq.md)


---

# 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://voltarb.gitbook.io/voltarb-docs/english/tradfi.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.