# Terminology / Glossary

### NFTs and Digital Assets

* **NFT (Non-Fungible Token)**: A unique digital asset verified using blockchain technology. Unlike cryptocurrencies like Bitcoin, each NFT has distinct information or attributes that make it unique.
* **Digital Asset**: Any text, image, or multimedia that exists in a digital format. In the context of eesee, these are the items being tokenized into NFTs.
* **Metadata**: Additional information that describes various attributes of the NFT, such as the creator, creation date, and any other relevant data.
* **Raffle**: A type of lottery where users purchase tickets for a chance to win an NFT.
* **Ticket Sales**: The process where sellers can opt for ticket-based NFT sales, setting ticket prices to maximize sales and total revenue.
* **Ticket Purchase**: The act of buying a ticket for a chance to win an NFT.
* **Winner Selection Model**: The method used to determine which ticket holder wins the NFT, often using Chainlink VRF for randomness.
* **NFT Ticketing**: The concept of buying a fraction of an NFT through a ticket-based system.
* **NFT Collections**: A set of NFTs grouped together, usually by the same creator or theme.
* **NFT Liquidity**: The ease with which NFTs can be bought or sold in the market without affecting their price.

### Blockchain and Smart Contracts

* **Blockchain**: A decentralized digital ledger that records transactions across multiple computers.
* **Smart Contracts**: Self-executing contracts with the terms directly written into code, often on the Ethereum blockchain.
* **ERC-721**: A standard for creating non-fungible tokens on the Ethereum blockchain.
* **ERC-20**: A standard for creating fungible tokens, often used for cryptocurrencies, on the Ethereum blockchain.
* **Gelato VRF**: Gelato's Verifiable Random Function, used for generating a random number in a secure and provable way.
* **Cryptographic Proof**: A mathematical way to prove the authenticity of a transaction or process.
* **Gas Fees**: Transaction fees on the Ethereum, Blast or Polygon networks, paid in their native tokens.
* **Transaction Authorization**: The process of giving approval for a transaction to proceed.
* **Test-net**: A testing environment for blockchain development, separate from the main network.

<details>

<summary>Platform-Specific Features and Policies</summary>

* **Eesee**: The platform in question, which offers a unique ticket-based system for buying and selling Digital assets.
* **$ESE Tokens**: The native token of the eesee platform.
* **Tier-based Model**: A model that categorizes users based on their activity level, offering different rewards for each tier.
* **Target Contribution Policy**: A policy that requires users to maintain a certain level of activity to keep their rewards.
* **Company Treasury**: A reserve of funds held by the company for various purposes.
* **Marketplace Commissions**: Fees taken by the marketplace for facilitating transactions.
* **Trading Protocol**: The set of rules governing how

</details>

<details>

<summary>Fundraising and Investment Rounds</summary>

* **Seed Round**: The initial round of fundraising for a new cryptocurrency project.
* **Strategic Round**: A fundraising round focused on strategic partners.
* **Private Round**: A fundraising round that is not open to the public.
* **Public Round**: The final round of fundraising before a token becomes publicly tradable.

</details>

### Staking & Rewards

### Platform Specific Features and Policies

### Fundraising and Investment Rounds

* **Seed Round**: The initial round of fundraising for a new cryptocurrency project.
* **Strategic Round**: A fundraising round focused on strategic partners.


---

# Agent Instructions: 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://docs.eesee.io/documentation/additional/terminology-glossary.md?ask=<question>
```

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.