> For the complete documentation index, see [llms.txt](https://docs.clore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clore.ai/help/glossary.md). # Glossary
**1. Blockchain** A decentralized digital ledger that records transactions across many computers. In the Clore.ai ecosystem, blockchain technology ensures the transparency, security, and immutability of all transactions, fostering trust among users. **2. Clore Coin (CLORE)** The native cryptocurrency of the Clore.ai platform. CLORE is used to facilitate transactions, reward participants, and support the platform's overall economy. **3. Decentralization** A system where control and decision-making are distributed among multiple participants rather than centralized in a single entity. Clore.ai leverages decentralization to create a more equitable and resilient platform for GPU leasing and cryptocurrency transactions. **4. GPU (Graphics Processing Unit)** A specialized electronic circuit designed to accelerate the processing of images and videos. In Clore.ai, GPUs are leased through a decentralized marketplace, allowing users to access high-performance computing power for various tasks like AI development and cryptocurrency mining. **5. GPU Leasing** The process of renting out GPU resources to others who need computing power. Clore.ai provides a platform where GPU owners can lease their idle hardware to users needing temporary access to powerful GPUs. **6. Proof of Holding (PoH)** A system within Clore.ai that rewards users for holding CLORE coins in their wallets. Unlike traditional staking, PoH offers rewards immediately, providing incentives for long-term holding and contributing to the platform's stability. **7. Marketplace** In the context of Clore.ai, the marketplace is a decentralized platform where users can lease or rent GPUs and CLORE coins. It operates on a peer-to-peer model, ensuring transparent and direct transactions between users. **8. Emission Schedule** The planned release of CLORE token rewards into circulation over time. Clore.ai's emission schedule follows a decay model (-30% per year) for PoH and marketplace rewards, ensuring controlled distribution and long-term value.
**9. Staking** In Clore.ai, staking refers to holding CLORE tokens in the Proof of Holding (PoH) system to earn rewards and reduce marketplace fees. Unlike traditional blockchain staking, PoH does not require transaction validation - simply holding tokens qualifies you for benefits. **10. Spot Rental** An interruptible rental option on the Clore.ai platform where GPU resources are allocated at a lower cost. Other users can overbid your offer at any time, making this option best suited for fault-tolerant workloads like cryptocurrency mining or batch processing. Base fee: 2.5%, reducible by up to 50% with Proof of Holding. **11. On-Demand Rental** A flexible rental option where users can lease GPUs from the Clore.ai marketplace on an as-needed basis. This option is ideal for users with varying computational needs. Base fee: 10%, reducible by up to 50% with Proof of Holding. **12. MFP Lock (Maximum Fair Price Lock)** A system allowing GPU hosts to lock CLORE tokens against their servers across three tiers. Tier 1 and Tier 2 earn emission rewards, while all three tiers contribute to reducing extra hoster fees on non-CLORE currency orders. Maximum lock: MFP × 7,000 CLORE. **13. Extra Fees** Additional platform fees applied to non-CLORE currency payments (e.g., Bitcoin). Extra hoster fees can be reduced to 0% through MFP Lock tiers. CLORE payments have no extra fees. **14. USD Stablecoins (USDT/USDC)** Stablecoins pegged to the US Dollar, supported on Clore.ai for deposits, withdrawals, and rental payments on two networks: Ethereum (ERC-20) and BNB Chain (BEP-20). Both tokens credit to a unified USD balance on the platform. **15. Airdrop** A distribution of cryptocurrency tokens to a specific group of users, often used as a marketing strategy or as a reward for platform participation. Clore.ai periodically conducts airdrops to reward users, particularly those participating in the Proof of Holding system. **16. Compliance** Adherence to legal and regulatory requirements in the jurisdictions where Clore.ai operates. The platform is committed to maintaining full compliance with relevant laws, ensuring a secure and trustworthy environment for all users. **17. Tokenomics** The economic structure of a cryptocurrency, including its supply, distribution, and reward mechanisms. Clore.ai’s tokenomics are designed to ensure long-term sustainability and value growth for the CLORE coin. **18. Scalability** The ability of the Clore.ai platform to handle increasing demand without compromising performance. Scalability is a key focus for Clore.ai, ensuring that the platform can grow and serve a larger user base effectively. **19. Bare Metal** Dedicated physical GPU servers and clusters rented for fixed terms (from two weeks up to five years) instead of per-minute container rentals. Configurations of up to 1,000 GPUs across multiple regions, priced in USD per GPU per hour. **20. Partial GPU Rental** Renting only a subset of the GPUs on a multi-GPU server and paying a proportional price. Available on-demand on homogeneous rigs whose hosts run up-to-date hosting software; each order gets an isolated container with dedicated GPUs. --- # 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://docs.clore.ai/help/glossary.md?ask=&goal= ``` `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.