> For the complete documentation index, see [llms.txt](https://docs.ston.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ston.fi/developer-section/omniston/glossary.md). # Glossary Definitions of Omniston terms and roles. This glossary defines the key terms used throughout the Omniston protocol, including its documentation, SDKs, and resolver integrations. ## Actors * **Trader**: protocol participant that requests quotes, creates swaps or orders, and provides the **Input asset**. * **Resolver**: protocol participant that provides quotes and settles trades by delivering the **Output asset**. * **Protocol**: the Omniston system, including its API, routing logic, and settlement contracts. * **Integrator**: external application or partner that brings flow into the protocol and receives the configured integrator fee. ## Assets * **Input asset**: asset provided by the **Trader** to start a trade. * **Input amount**: amount of the **Input asset** involved in a quote and a trade. * **Output asset**: asset the **Trader** expects to receive as the result of a trade. * **Output amount**: amount of the **Output asset** involved in a quote and a trade. * **Source blockchain**: blockchain on which the **Input asset** is provided and the trade is initiated. * **Destination blockchain**: blockchain on which the **Output asset** is delivered to the **Trader**. ## RFQ Protocol * **RFQ**: request for quote sent by the **Trader** to ask resolvers for trade terms. * **Quote**: resolver-specific offer that defines trade amounts, fees, and settlement data for a given **RFQ**. * **Swap settlement**: settlement mode in which the trade is executed immediately through one or more swap routes. * **Order settlement**: settlement mode in which the trade is represented as an order or position that can be filled by a **Resolver**. ## Swap settlement * **Swap route**: complete path used to convert the **Input asset** into the **Output asset**. * **Swap step**: one asset-to-asset conversion inside a **Swap route**. * **Swap chunk**: the smallest executable part of a **Swap step**, typically bound to a specific liquidity source or protocol. ## Order settlement * **Order**: trade object created from a quote and exposed for filling, fully or partially, by one or more resolvers. * **Signed Order**: blockchain-specific signed payload that authorizes settlement without first depositing funds into an escrow position. * **Order details**: off-chain structure whose hash is embedded into settlement transactions to verify the trade intent. * **Execution**: individual fill attempt or fill fragment within an **Order**. * **Input position**: position on the **Source blockchain** that holds or represents the **Input asset** for an **Execution**. * **Output position**: position on the **Destination blockchain** that holds or represents the **Output asset** for an **Execution**. ## Contracts * **Protocol contract**: smart contract used by the protocol to enforce settlement rules on a blockchain. * **Escrow factory contract**: contract that creates or manages escrow positions for **Order settlement**. * **Escrow position contract**: contract instance that stores the assets and state of a particular escrow-backed position. * **Vault contract**: a contract holding funds in a settlement flow. This is distinct from a [DEX integrator-fee Vault](/developer-section/dex/fees.md); check the contract and payout context. ## Operations * **Order cancellation**: operation by which the **Trader** cancels the unfilled remainder of an **Order**. For escrow-backed orders, cancellation also returns the remaining escrowed funds. * **Execution completion**: successful finalization of an **Execution**, in which the exchange is completed according to protocol rules. * **Execution rollback**: unsuccessful finalization of an **Execution**, in which assets are returned according to protocol rules. ## Identities and fee units * **AssetId**: chain-specific identity of an asset, including its native or token type. * **ChainAddress**: chain-specific wallet, contract, or position address. The asset and address on each side must use the same chain. * **Chain identity**: the chain selected by the named field in `AssetId` or `ChainAddress`. See [Supported chains and assets](/developer-section/omniston/chains.md) for SDK fields. * **Integrator fee**: fee requested by an application bringing flow to Omniston. Configure the destination-side integrator address and rate; see [Integrator fees](/developer-section/omniston/referral-fees.md). * **Pip**: one millionth of a whole: `0.0001%`. One basis point is 100 pips. API v1beta8 uses pips; Widget fee configuration uses basis points. For the relationship between quote, order, execution, and positions, see [Settlement lifecycle](/developer-section/omniston/how-omniston-works.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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ston.fi/developer-section/omniston/glossary.md?ask=&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.