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

# Glossary

***EVM (Ethereum Virtual Machine)**: A virtual execution environment that supports a single scripting language, primarily used in Ethereum-based smart contracts.*

***Candidate**: A nominee for the role of Validator, responsible for participating in the election process to become a Validator.*

***Validator**: Selected from Candidates, Validators are responsible for signing messages in the Tendermint consensus process.*

***Delegator**: An individual who delegates their MTT tokens to a Validator (or Candidate) and shares in the associated rewards.*

***Unbonding period** : The buffer time from when a holder initiates unbonding to when they regain control over their MTT tokens.*

***Transaction fees** : Fees included in an MTT Network transaction, earned by Validators, and distributed among Validators and Delegators based on their bonded Atom amounts.*

***Commission fee**: A fee taken by Validators for the services they provide, deducted from the transaction fees.*

***Double Signing**: A serious malicious act where a Validator node signs blocks on two different chains simultaneously.*

***Verifiable Random Function (VRF)**: A function used to generate random numbers that can be verified for authenticity and integrity.*

***GAS**: Transaction fees on the MTT Network, used to pay for the computational resources required to process and validate transactions.*

***IBC (Inter-Blockchain Communication Protocol)**: A protocol enabling different blockchains to communicate and interact with each other.*

***Solidity**: A binary instruction format for a stack-based virtual machine, used for deploying smart contracts in a more efficient and secure manner on blockchains.*

***Cosmos SDK**: Modular components of the Cosmos SDK, which provide various functionalities for building blockchain applications.*

***Tendermint**: A consensus algorithm used in Cosmos-based blockchains, providing Byzantine Fault Tolerance (BFT) to ensure network security and consensus.*

***Validator Node**: A node in the blockchain network responsible for validating transactions and creating new blocks as part of the consensus mechanism.*

***RNG (Random Number Generator)**: A system or algorithm used to generate random numbers, often utilized in gaming and cryptographic applications.*

***MTT in Poker (Multi-Table Tournament)** : A poker tournament format where players are distributed across multiple tables, as opposed to single-table tournaments or sit-and-goes.*

***Vyper**: A high-level programming language designed for the Ethereum Virtual Machine (EVM), focusing on simplicity and security, making it particularly suited for developing smart contracts that prioritize code safety and auditability.*

***Yul**: An intermediate-level programming language used for optimizing smart contract execution on the Ethereum Virtual Machine (EVM), serving as a low-level language that compiles into EVM bytecode and is often used for optimization purposes.*


---

# 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://mtt-network.gitbook.io/mtt-network-1/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.