> For the complete documentation index, see [llms.txt](https://docs.t-rex.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.t-rex.network/resources/glossary.md). # Glossary The terms these docs use, each with one definition. Names in code font are names of the code. | Term | Definition | | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Access manager** | The contract that decides who can call each restricted function. Each suite has one, a `TREXAccessManager`, and the network has one for its shared contracts | | **Agent** | An account that holds an agent role on an asset. A Token Agent acts on positions: mint, burn, freeze, forced transfer, recovery, pause. A Registry Agent maintains registrations | | **Asset** | A financial instrument recorded on the register by a token suite | | **Available balance** | For a satellite wallet: its bridged position less what open validations reserve. `Token.availableOf` | | **Beacon** | The contract a proxy reads its implementation from. Moving a beacon upgrades every proxy that points at it | | **Bridged position** | The part of a holder's position that is active on a satellite. The register records it per satellite wallet | | **Burn proof** | The message a satellite sends when it burned tokens for a recall | | **Chain key** | The `bytes32` identifier of a chain: the hash of its ERC-7930 address with an empty account | | **Claim** | A statement about an identity, signed by a Claim Issuer and stored on the identity | | **Claim Issuer** | A party that verifies participants off-chain and attests the result as claims. It has an ONCHAINID of type `CLAIM_ISSUER` | | **Claim topic** | A number that names the fact a claim attests. An asset lists the topics it requires | | **Compliance** | The second gate of a movement: whether this movement is allowed now, under the rules of the asset. Answered by `ModularCompliance` | | **Compliance module** | A contract that implements one rule of an asset. Its type is `RULE`, `SPENDER` or `TRACKER` | | **Compliance Owner** | The holder of the `OWNER` role on an asset: it binds modules and sets their parameters | | **Delegation-out** | The movement that makes part of a position active on a satellite | | **Domain** | A number that scopes the roles of one asset inside an access manager | | **Eligibility** | The first gate of a movement: whether an identity may hold the asset. Answered by `TREXRegistry.isVerified` | | **Forced transfer** | A transfer ordered by a Token Agent without the holder's signature | | **Free balance** | The balance of an address less its frozen tokens: what it can send. `Token.freeBalanceOf` | | **Frozen** | An address that can neither send nor receive, or an amount that cannot be sent | | **Gateway** | A contract that carries messages between chains behind the ERC-7786 interface | | **Golden copy** | The authoritative record of an asset and of every identity, held on the reference chain | | **Guardian** | A signer that an Identity Owner names to recover its identity | | **Identity** | An ONCHAINID | | **Identity Owner** | The party that controls an ONCHAINID through its `MANAGEMENT` keys | | **Identity type** | The category of an ONCHAINID, recorded once by the factory: `ASSET`, `INDIVIDUAL`, `CORPORATE`, `IOT`, `CLAIM_ISSUER`, `SMART_CONTRACT`, `PUBLIC_AUTHORITY`, `AI_AGENT` | | **In transit** | An amount burned on one satellite whose mint on another satellite is not reported | | **Interoperable address** | An address with its chain, in the ERC-7930 format. The protocol uses the canonical binary form | | **Investor** | A holder or prospective holder of an asset | | **Issuer** | The legal entity that brings an asset onto the register and governs its token suite | | **Key** | A signer registered on an ONCHAINID, with one or more purposes: `MANAGEMENT`, `ACTION`, `CLAIM_SIGNER`, `ENCRYPTION`, `CLAIM_ADDER`, `PROPOSER` | | **Late reconciliation** | A settlement that arrives after its validation was discarded. It is applied and flagged | | **Network governance** | The body that holds the platform roles: versions, trusted gateways, identity types, reputation | | **ONCHAINID** | The identity of a participant or of an asset: a smart account that holds keys and claims, can hold tokens, and has wallets linked to it | | **Peer** | The contract that represents an asset on another chain: T-REX Lite on a satellite, the token on the reference chain | | **Platform** | The service that prepares, checks and relays operations for an Issuer, an Investor or another actor | | **Position** | What an identity owns of an asset, over all its addresses and all chains. `ModularCompliance.positionOf` | | **Recall** | The movement that brings a position back from a satellite to the reference chain | | **Reconciliation window** | The time after the expiry of a validation during which its settlement is still expected | | **Reference chain** | The chain that holds the golden copy and runs the full protocol. Also called the T-REX Ledger | | **Register** | The record of who owns an asset, by identity. The token and its compliance on the reference chain | | **Registration** | The binding of an address to an identity for one asset, written by a Registry Agent | | **Reputation** | A score per Claim Issuer, set by Network governance, that gates adding claims without a key grant | | **Reservation** | The amount of a satellite wallet promised to an open validation | | **Route** | The gateway an asset uses for one satellite | | **Satellite chain** | Any chain other than the reference chain on which an asset is made available | | **Settlement notification** | The message a satellite sends after it executed a validation | | **Spender policy** | The rules of an asset about which third parties may execute `transferFrom` for holders | | **Standing** | A Claim Issuer has standing when its identity is of type `CLAIM_ISSUER` and its reputation reaches the claim-add threshold | | **T-REX AppStore** | The directory of the applications built on the protocol | | **T-REX Ledger** | The reference chain | | **T-REX Lite** | The token that represents an asset on a satellite. It executes only what the reference chain authorized | | **T-REX Network** | The protocol, its reference chain, the satellites connected to it and the AppStore | | **Token suite** | The contracts of one asset: token, registry, identity storage, compliance and access manager | | **Trusted issuer** | A Claim Issuer that an asset accepts for given claim topics | | **Validation** | The authorization, issued on the reference chain, of one transfer on a satellite: parties, range of amounts, expiry | | **Validation Keeper** | The role that discards expired validations and resolves stuck ones, run by the T-REX Network | | **Validity window** | The time a validation can be executed on a satellite | | **Venue or application** | A contract through which an asset is traded or used. It takes part under its own ONCHAINID | | **Wallet** | An address linked to an ONCHAINID: an externally owned account, a smart-contract wallet, or an address on another chain | --- # 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.t-rex.network/resources/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.