> For the complete documentation index, see [llms.txt](https://doc.mprolab.io/mprolab/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.mprolab.io/mprolab/appendices/glossary-of-terms.md). # Glossary of Terms 1. **MPRO Lab**: A web-based platform centered around MPRO, designed for iNODE providers and the DAGO community. It facilitates the acquisition and management of iNODE software licenses and allows for the monitoring and management of iNODE operations and MPRO tokens. 2. **iNODE**: A software application that forms part of the Metapro Protocol, serving as a decentralized database for storing fragments of game files and assets. iNODEs also act as validators within the Metapro Protocol's decentralized side chain network. 3. **iNODE Provider**: An individual or entity that maintains and operates an iNODE, contributing to the Metapro Protocol's decentralized network. They are rewarded with MPRO tokens for their service. 4. **MPRO**: A multichain, ERC20 governance token using LayerZero technology, native to the Ethereum network. It is distributed as a reward to iNODE providers and is a governance token for the DAGO (Decentralized Autonomous Gaming Organization). 5. **REWARD** in MPRO Lab refers to token distribution via smart contracts based on NODE uptime and performance.It follows standard DeFi usage (as in staking, autostaking, yield farming, minting) and is not a financial return or ROI. 6. **DAGO (Decentralized Autonomous Gaming Organization)**: An autonomous organization created by the Metapro team, focusing on the Web3 gaming and esports market. Governance in DAGO is exercised by MPRO token holders. 7. **Smart Contract**: A self-executing contract with the terms of the agreement directly written into lines of code, deployed on a blockchain network. 8. **Blockchain Network**: A digital ledger technology that records transactions across many computers so that any involved record cannot be altered retroactively, without the alteration of all subsequent blocks. 9. **ERC20 Token**: A standard for fungible tokens created on the Ethereum blockchain, allowing for the implementation of a standard API for tokens within smart contracts. 10. **Web3**: The third generation of internet services for websites and applications, focusing on utilizing a machine-based understanding of data to provide a data-driven and decentralized Web. 11. **Decentralized Application (DApp)**: A digital application or program that runs on a blockchain or peer-to-peer network of computers, outside the purview and control of a single authority. 12. **Governance Token**: A token that gives its holders the right to participate in the governance decisions of a decentralized organization or protocol. 13. **LayerZero Technology**: An underlying technology used in blockchain for creating cross-chain communication and interoperability. 14. **Ethereum Network**: A decentralized, open-source blockchain system that features smart contract functionality. 15. **Voting (in the context of DAO)**: A mechanism that allows token holders to participate in the decision-making process of the organization, often proportional to the number of tokens held. 16. **Blockchain Interoperability**: The ability of different blockchain systems to connect and communicate with each other, allowing for the exchange of information and value. 17. **Smart Contract Deployment**: The process of publishing a smart contract on the blockchain so that it can be executed and interacted with. 18. **Licensing (in the context of iNODE)**: The process through which a user acquires the right to operate an iNODE within the Metapro Protocol. --- # 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: ``` GET https://doc.mprolab.io/mprolab/appendices/glossary-of-terms.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.