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

# Glossary

**Omnichain** - Omnichain tokens are available on multiple chains, with no bridging fees. Omnichain tokens also have the same price data on different chains for the same token. \
\ <mark style="color:yellow;">Example:</mark> BTC on different networks.

**Reflections** - Reflections are when a token has fees, and a portion of those fees is 'reflected' back to holders. \
\ <mark style="color:yellow;">Example:</mark> Say a token has 10% selling fees. Half of those fees go back to holders either in the token itself, or potentially another token like native gas tokens. \
\
**LayerZero** - LayerZero is a cross-chain messaging protocol designed to facilitate interactions between smart contracts across different blockchain networks.


---

# 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://scalex.gitbook.io/scalex/glossary.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.