# NTM-IA White Paper ## 1. Legal Disclaimer ### 1.1. Informational nature and non-solicitation This document is for informational purposes only and does not constitute an offer to sell, a solicitation to buy, a recommendation, or any form of financial, legal, or tax advice. Nothing in this document should be interpreted as a binding proposal to acquire any tokens. ### 1.2. No public offering, return promise, or advice NTM‑IA is not being offered to the general public through this document. Any eventual offering will be conducted exclusively through launchpads and in compliance with applicable laws. No statement in this document constitutes a promise of return, appreciation, or financial gain. The projections presented are **modeled scenarios**, not guarantees of future performance. **Any decision to acquire or dispose of NTM‑IA must be based on the investor's own independent analysis and, if necessary, on qualified professional advice.** ### 1.3. Limitations of scenarios, projections, and numerical examples All scenarios, projections, and numerical examples contained in this document are based on current assumptions and historical data. These assumptions may not materialize. Actual results may differ materially from the projections presented. Investors should not rely solely on these scenarios to make investment decisions. ### 1.4. Dependence on technical implementation, data, and third parties The operation of NTM‑IA depends on correct technical implementation, availability and integrity of public data (including `ai_ia_uas.json`, `ai_ia_totals.json`, `llms.json`, `ai-dash-snippet.php`, as well as the `ntm-ia-trust.php` endpoint for real‑time calculation), and third‑party services (such as servers, APIs, and launchpads). Failures or interruptions in these components may affect the operation of the token. ### 1.5. Regulatory notices and jurisdictional scope Laws and regulations applicable to crypto‑assets vary significantly across jurisdictions. It is the sole responsibility of each investor to know and comply with the laws of their country of residence. This document does not constitute legal advice. If in doubt, consult a qualified attorney in your jurisdiction. ## 2. Executive Summary ### 2.1. What is NTM‑IA (high‑level view) NTM‑IA is a utility token derived from the original NTM blockchain, designed to function as a **market layer** (layer 2) on top of an already existing and verified AI activity monitoring system. It combines real‑world AI metrics with a self‑regulating minting mechanism, staking, and direct utility within the Netmeios ecosystem. ### 2.2. What is the original NTM (essential summary with verifiable derivation) The original NTM (Netmeios Token) is an economic and technical model that measures the **savings generated for AI platforms** (ChatGPT, Google AI, Perplexity, etc.) that consume data from the Netmeios hub. #### Calculation methodology (transparent and verifiable) Values are calculated from **daily values per UAs per entity in the hub**, ensuring that anyone can recalculate them using public data. **Base parameters (example with real data):** - `UAs` = 58 (active AI User Agent variants – source: `ai_ia_uas.json`) - `entities` = 674 (companies in the hub – source: `llms.json`) - `days` = 365 #### Step 1: Daily value per UAs per entity | Area | Daily value per UAs per entity | Calculation | |:---|:---|:---| | **Technical audit** | €0.0000315 | Estimate based on cost of specialized hours | | **Infrastructure efficiency** | €0.0000132 | Estimate based on bandwidth reduction | | **Risk and compliance mitigation** | €0.0000105 | Estimate based on regulatory risk reduction | | **Total daily per UAs per entity** | **€0.0000552** | — | > **Note:** These daily values are estimates based on market metrics and Netmeios operational experience. Their small size reflects the distribution of savings across **58 UAs** and **674 entities**. #### Step 2: Annual value per entity Multiplying the daily total per UAs per entity by the number of UAs and by 365 days: `Annual_value_per_entity = €0.0000552 × 58 × 365` `Annual_value_per_entity = €1.17/day × 365` `Annual_value_per_entity = €789/year` #### Step 3: Annual values per component | Area | Annual value per entity | |:---|:---| | Technical audit | €450/year | | Infrastructure efficiency | €189/year | | Risk and compliance mitigation | €150/year | | **Total per entity** | **€789/year** | #### Step 4: Global annual savings for AI platforms `Global_annual_savings = entities × €789/year` `Global_annual_savings = 674 × 789 = €531,786/year` #### Public verification Anyone can consult: - `ai_ia_uas.json` → to obtain the exact number of UAs - `llms.json` → to obtain the number of entities in the hub And recalculate all the values presented using the formulas above. **Implication for NTM‑IA:** NTM‑IA derives part of its value from this savings generated for AI platforms. The NTM‑IA price formula (Section 5) dynamically links AI activity to the economic value of the ecosystem. ### 2.3. Why NTM‑IA exists now The exponential growth of AI bots (GPTBot, ClaudeBot, Perplexity, Google AI, etc.) and the imminent application of the **EU AI Act** (August 2026) create an urgent need for reliable, verifiable, and economically relevant metrics about AI activity on the web. NTM‑IA responds to this need by offering a transparent, self‑regulating asset anchored in public data. ### 2.4. Core thesis: derived, verifiable, self‑regulated by public data The core thesis of NTM‑IA is as follows: - **Derived** – Its value is anchored in the real economic savings generated for AI platforms (3 pillars) and in its direct utility (payment for services). - **Verifiable** – The entire block chain is public, cryptographically signed (RSA‑SHA256), and can be independently verified by anyone. See the [verification protocol](./NTM-IA-VERIFICATION.md). - **Self‑regulating** – The issuance of new tokens is determined exclusively by the number of UAs (active AI User Agents), with no human intervention (`mint_ratio = uas`). ### 2.5. How to verify the chain (summary) Anyone can verify the integrity of the NTM‑IA blockchain using only HTTP GET and SHA256: 1. Query the latest hash at `last_hash.txt` 2. Download the blocks from `/blockchain/ntm-ia/blocks/` 3. Verify that each block's `previous_hash` matches the SHA256 of the previous block 4. Validate the RSA‑SHA256 signatures with the public key For detailed instructions, see [Section 13 (Public Verification)](#13-public-verification-and-endpoints) and the [verification protocol](./NTM-IA-VERIFICATION.md). ### 2.6. Main metrics and public endpoints | Endpoint | Function | |:---|:---| | `ntm-ia-trust.php` | Price, supply, market cap, Trust Score, and real‑time data | | `api-blocks-ntm-ia.php` | Block query (history, hashes, indices) | | `ai-check-integrity-ntm-ia.php` | Automated chain integrity checker | | `ai-ntm-ia-stats.php` | Public dashboard with charts and statistics | ### 2.7. Main risks and warnings (summary) - **Market risk:** Volatility, liquidity, competition - **Regulatory risk:** Changes in laws applicable to crypto‑assets - **Technical risk:** Bugs, security failures, interruptions - **Adoption risk:** The hub may not grow as projected - **Execution risk:** The roadmap may experience delays > **Warning:** The projections presented throughout this document are **modeled scenarios**, not promises of return. See Section 1 (Legal Disclaimer) for detailed information. ## 3. Context, Problem, and Opportunity ### 3.1. Growth of AI agents and bots on the web In recent years, there has been an explosion in the number of AI agents and bots browsing the web. Platforms such as ChatGPT (GPTBot), Google AI (Google-Extended), Perplexity (PerplexityBot), Anthropic (ClaudeBot), Amazon (Amazonbot), and many others constantly send their crawlers to collect data, train models, and respond to queries in real time. This phenomenon is not transitory – it is structural. The web is becoming an ecosystem increasingly populated by autonomous agents that consume and process information on a scale never seen before. ### 3.2. Limitations of traditional metrics Traditional web traffic metrics (pageviews, visits, session time, etc.) were designed for humans, not for AI agents. Consequently: - **They do not distinguish** between human traffic and AI traffic - **They do not measure** the diversity or quality of agents accessing a site - **They do not allow** verification of the authenticity or compliance of AI traffic - **They lack** an immutable and verifiable record of activity ### 3.3. Need for economically linked metrics tied to verifiable activity For AI platforms, investors, and regulators, there is a growing need for metrics that are: - **Verifiable** – Anyone must be able to confirm their authenticity - **Economically relevant** – Linked to real savings or value generated - **Transparent** – Based on public data and open formulas - **Immutable** – Recorded on a blockchain that cannot be retroactively altered ### 3.4. Regulatory context (EU AI Act) and implications for AI monitoring The **EU AI Act** (European Artificial Intelligence Regulation) comes into full application in **August 2026**. This regulation imposes significant obligations on AI platforms, including: - Transparency about the data used for training - Compliance with copyright rules - Accountability for the impact of their systems To meet these obligations, AI platforms need **verifiable records** of their web activity – something that NTM and NTM‑IA provide. ### 3.5. Current position of NTM and NTM‑IA in this context The **original NTM** already provides an internal layer for monitoring and measuring AI activity, with a public and verifiable blockchain. However, it is a technical tool, not a marketable asset. **NTM‑IA** emerges to bridge the gap between **technical measurement** and **market value**: | Need | NTM‑IA Response | |:---|:---| | Verifiable metrics | Public blockchain with RSA‑SHA256 signatures | | Economic value | Derived from savings generated for AI platforms | | Transparency | Public formulas, accessible JSON data | | Practical utility | Payment for services in the Netmeios ecosystem | | Community participation | Staking, future governance, access tiers | ## 4. NTM and NTM‑IA: Definition and Relationship ### 4.1. What is the original NTM (technical‑economic summary) The original NTM (Netmeios Token) is an economic and technical model that measures the **savings generated for AI platforms** that consume data from the Netmeios hub. As exemplified in Section 2.2, this savings can be modeled, for illustrative purposes, as approximately **€789 per entity in the hub**, broken down into three pillars (technical audit, infrastructure, and risk/compliance). The original NTM is an **internal tool** for measurement and auditing, not a marketable token. Its blockchain is public, but its purpose is technical, not financial. ### 4.2. Current state of NTM: blockchain, sealer, data, and existing dashboards The original NTM already has a functional infrastructure: | Component | Description | |:---|:---| | **Sealer** | Generates blocks every 10 minutes with AI metrics | | **Blockchain** | `/blockchain/blocks/` folder with hash‑linked blocks | | **Data** | Public JSON files (`ai_ia_totals.json`, `llms.json`, etc.) | | **Endpoints** | `ntm-trust.php`, `api-blocks.php`, `check-integrity.php` | | **Dashboard** | `ntm-stats.php` with statistics and charts | ### 4.3. Reasons for creating a derivative: NTM‑IA as a market layer (layer 2) The original NTM, being an internal tool, was not designed to be marketed or traded on public markets. To meet the demand for an asset that: - Represents the value of the monitored AI ecosystem - Allows open participation (staking, investment) - Has practical utility (payment for services) - Is marketable on launchpads and exchanges **NTM‑IA** was created as a **market layer** (layer 2) on top of the existing NTM infrastructure. ### 4.4. Formal definition of NTM‑IA (asset type, function) NTM‑IA is a **utility token** with the following characteristics: | Characteristic | Description | |:---|:---| | **Type** | Utility token (not a security) | | **Issuance** | Self‑regulated by `mint_ratio = uas` | | **Utility** | Staking, payment for services, future governance | | **Verifiability** | Public blockchain with RSA‑SHA256 signatures | | **Marketability** | IDO via launchpad, exchange listings | ### 4.5. Difference in purpose: internal layer (NTM) vs. market layer (NTM‑IA) | Characteristic | NTM (layer 1) | NTM‑IA (layer 2) | |:---|:---|:---| | **Purpose** | Internal measurement and auditing | Commercial and utility token | | **Marketability** | Not marketable | IDO, exchanges, staking | | **Minting** | Fixed (100 hits = 1 NTM) | Self‑regulated (`mint_ratio = uas`) | | **Staking** | Not applicable | 20-40% APY, tiers, locks | | **Utility** | Internal (technical equity) | Payment for services, governance | | **Target audience** | Auditors, technicians | Investors, crypto community | ### 4.6. What is new: NTM‑IA sealer, signed blocks, public endpoints NTM‑IA introduces several elements that do not exist in the original NTM: | Element | Description | |:---|:---| | **NTM‑IA Sealer** | `ai-sealer-ntm-ia.php` – generates layer‑2 blocks | | **Signed blocks** | Each block contains an RSA‑SHA256 signature | | **Separate blockchain** | `/blockchain/ntm-ia/blocks/` + `last_hash.txt` | | **Trust Score** | Confidence metric (0-100) based on UAs, % IA, AI Index | | **Public endpoints** | `ntm-ia-trust.php`, `api-blocks-ntm-ia.php`, `ai-check-integrity-ntm-ia.php` | | **Dashboards** | `ai-ntm-ia-stats.php`, `ai-staking-stats.php` | | **Staking** | Complete staking system with rewards and locks | ## 5. Economic Thesis and Price Formation Mechanism ### 5.1. Price Note (NP) – Intuition and economic role The Price Note (NP) is an intermediate metric that aggregates the main AI activity factors into a single value. Its role is to **link observed AI activity to the economic value of the token**, acting as a bridge between the technical world (logs, hits, UAs) and the financial world (price, market cap). **Intuition:** The more relevant and diverse AI activity occurs, the higher the NP will be. ### 5.2. Components (intuition per variable) | Variable | Intuition | Data source | |:---|:---|:---| | `hits` | Total volume of AI activity | `ai_ia_totals.json` | | `pct_ia` | Relevance of AI in total traffic | `ai_ia_totals.json` + `ai_bot_totals.json` | | `ai_index` | Quality and trustworthiness of AI agents | `ntm-trust.php` endpoint | | `uas` | Diversity of AI agents (higher = scarcer token) | `ai_ia_uas.json` | | `hub` | Size of the ecosystem (integrated companies) | `llms.json` | | `respostas` | Human interaction (elite/infra) | `ai_ia_totals.json` | ### 5.3. NP formula `NP = (pct_ia + ai_index) × (hits / uas) + respostas` **Where:** - `pct_ia` and `ai_index` are normalized values between 0 and 1 - `hits` is the total accumulated AI hits - `uas` is the number of active AI User Agent variants - `respostas` is the total interactions (human and bot) ### 5.4. Original NTM price formula `NTM_original = (hub × 394.50) / (hits / 100)` **Origin of the constant €394.50:** This value corresponds to **half of the modeled annual savings per entity in the hub** (€789 / 2 = €394.50). Choosing half of the savings reflects a conservative approach, attributing only part of the total economic value to the original NTM. The other half remains as "retained value" for the AI platforms. ### 5.5. NTM‑IA price formula `NTM-IA = NP / NTM_original` **Economic intuition:** This relationship creates a **natural arbitrage** between real AI activity (captured by NP) and the market value derived from the hub (NTM_original). When AI activity increases relative to the hub's value, the price of NTM‑IA rises; when the hub grows faster than activity, the price falls. This mechanism ensures that NTM‑IA **dynamically** reflects the relative health of the ecosystem. ### 5.6. How these formulas link activity metrics to economic value | Component | What it measures | Impact on NTM‑IA price | |:---|:---|:---| | Increase in `hits` | More AI activity | ↑ Increases NP → ↑ price | | Increase in `uas` | More agent diversity | Increases `mint_ratio` but reduces tokens per hit (`supply = hits/uas`), reinforcing the link between AI diversity and relative scarcity | | Increase in `hub` | More integrated companies | ↑ NTM_original → ↓ price (dilution) | | Improvement in `ai_index` | Better agent quality | ↑ NP → ↑ price | | Increase in `respostas` | More interactions | ↑ NP → ↑ price | ## 6. Issuance and Minting Mechanism ### 6.1. Self‑regulating issuance principle NTM‑IA does not have a fixed issuance or a predefined "hard cap". Instead, the issuance of new tokens is **self‑regulated** by real AI activity in the ecosystem. The higher the number of UAs, the higher the minting ratio and the lower the number of tokens issued per hit (`supply = hits / uas`), reinforcing the link between AI diversity and relative scarcity. ### 6.2. Minting rule: `mint_ratio = uas` `mint_ratio = uas` **Where:** `uas` = number of active AI User Agent variants (source: `ai_ia_uas.json`) **Example:** - If `uas = 58`, **58 IA hits** are required to mint **1 NTM-IA** - If `uas = 70`, **70 IA hits** are required to mint **1 NTM-IA** (scarcer) ### 6.3. Justification: UAs as a proxy for the number of distinct AI agents `uas` (AI User Agents) represent the **active variants** of AI bots browsing the web. Each AI bot (e.g., GPTBot) can have multiple variants (e.g., GPTBot/1.0, GPTBot/2.0). Thus, the number of `uas` is a **reliable proxy** for the diversity of AI agents in the ecosystem. **Relationship:** - More agent diversity → higher `uas` → higher `mint_ratio` → greater scarcity - Less diversity → lower `uas` → lower `mint_ratio` → higher issuance per hit ### 6.4. Effect of UAs variation on issuance and supply | UAs variation | Effect on `mint_ratio` | Effect on `supply` (`hits / uas`) | |:---|:---|:---| | Increase in UAs | ↑ Increases | ↓ Decreases (more scarcity) | | Decrease in UAs | ↓ Decreases | ↑ Increases (more issuance) | ### 6.5. Supply predictability **There is no fixed hard cap on supply.** Issuance is determined exclusively by the number of active UAs and the transparency of public data. | Feature | Description | |:---|:---| | **No arbitrary hard cap** | Supply grows with real AI activity, without artificial limits | | **Clear and public rule** | `mint_ratio = uas` – anyone can verify it in `ai_ia_uas.json` | | **Predictability** | The issuance rate is known and calculable from public data | | **Full transparency** | The blockchain is public and independently verifiable | ### 6.6. Numerical examples of issuance over time | Scenario | UAs | Accumulated IA Hits | Supply (`hits / uas`) | Mint ratio | |:---|:---|:---|:---|:---| | **Current state** | 58 | 278,207 | ~4,797 | 58 | | **Scenario A (diversity growth)** | 80 | 500,000 | ~6,250 | 80 | | **Scenario B (peak diversity)** | 100 | 1,000,000 | ~10,000 | 100 | | **Scenario C (diversity decline)** | 50 | 300,000 | ~6,000 | 50 | > **Note:** Values are illustrative. Actual supply depends on the evolution of IA hits and UAs over time. ## 6. Issuance and Minting Mechanism ### 6.1. Self‑regulating issuance principle NTM‑IA does not have a fixed issuance or a predefined "hard cap". Instead, the issuance of new tokens is **self‑regulated** by real AI activity in the ecosystem. The higher the number of UAs, the higher the minting ratio and the lower the number of tokens issued per hit (`supply = hits / uas`), reinforcing the link between AI diversity and relative scarcity. ### 6.2. Minting rule: `mint_ratio = uas` `mint_ratio = uas` **Where:** `uas` = number of active AI User Agent variants (source: `ai_ia_uas.json`) **Example:** - If `uas = 58`, **58 IA hits** are required to mint **1 NTM-IA** - If `uas = 70`, **70 IA hits** are required to mint **1 NTM-IA** (scarcer) ### 6.3. Justification: UAs as a proxy for the number of distinct AI agents `uas` (AI User Agents) represent the **active variants** of AI bots browsing the web. Each AI bot (e.g., GPTBot) can have multiple variants (e.g., GPTBot/1.0, GPTBot/2.0). Thus, the number of `uas` is a **reliable proxy** for the diversity of AI agents in the ecosystem. **Relationship:** - More agent diversity → higher `uas` → higher `mint_ratio` → greater scarcity - Less diversity → lower `uas` → lower `mint_ratio` → higher issuance per hit ### 6.4. Effect of UAs variation on issuance and supply | UAs variation | Effect on `mint_ratio` | Effect on `supply` (`hits / uas`) | |:---|:---|:---| | Increase in UAs | ↑ Increases | ↓ Decreases (more scarcity) | | Decrease in UAs | ↓ Decreases | ↑ Increases (more issuance) | ### 6.5. Supply predictability **There is no fixed hard cap on supply.** Issuance is determined exclusively by the number of active UAs and the transparency of public data. | Feature | Description | |:---|:---| | **No arbitrary hard cap** | Supply grows with real AI activity, without artificial limits | | **Clear and public rule** | `mint_ratio = uas` – anyone can verify it in `ai_ia_uas.json` | | **Predictability** | The issuance rate is known and calculable from public data | | **Full transparency** | The blockchain is public and independently verifiable | ### 6.6. Numerical examples of issuance over time | Scenario | UAs | Accumulated IA Hits | Supply (`hits / uas`) | Mint ratio | |:---|:---|:---|:---|:---| | **Current state** | 58 | 278,207 | ~4,797 | 58 | | **Scenario A (diversity growth)** | 80 | 500,000 | ~6,250 | 80 | | **Scenario B (peak diversity)** | 100 | 1,000,000 | ~10,000 | 100 | | **Scenario C (diversity decline)** | 50 | 300,000 | ~6,000 | 50 | > **Note:** Values are illustrative. Actual supply depends on the evolution of IA hits and UAs over time. ## 6. Issuance and Minting Mechanism ### 6.1. Self‑regulating issuance principle NTM‑IA does not have a fixed issuance or a predefined "hard cap". Instead, the issuance of new tokens is **self‑regulated** by real AI activity in the ecosystem. The higher the number of UAs, the higher the minting ratio and the lower the number of tokens issued per hit (`supply = hits / uas`), reinforcing the link between AI diversity and relative scarcity. ### 6.2. Minting rule: `mint_ratio = uas` `mint_ratio = uas` **Where:** `uas` = number of active AI User Agent variants (source: `ai_ia_uas.json`) **Example:** - If `uas = 58`, **58 IA hits** are required to mint **1 NTM-IA** - If `uas = 70`, **70 IA hits** are required to mint **1 NTM-IA** (scarcer) ### 6.3. Justification: UAs as a proxy for the number of distinct AI agents `uas` (AI User Agents) represent the **active variants** of AI bots browsing the web. Each AI bot (e.g., GPTBot) can have multiple variants (e.g., GPTBot/1.0, GPTBot/2.0). Thus, the number of `uas` is a **reliable proxy** for the diversity of AI agents in the ecosystem. **Relationship:** - More agent diversity → higher `uas` → higher `mint_ratio` → greater scarcity - Less diversity → lower `uas` → lower `mint_ratio` → higher issuance per hit ### 6.4. Effect of UAs variation on issuance and supply | UAs variation | Effect on `mint_ratio` | Effect on `supply` (`hits / uas`) | |:---|:---|:---| | Increase in UAs | ↑ Increases | ↓ Decreases (more scarcity) | | Decrease in UAs | ↓ Decreases | ↑ Increases (more issuance) | ### 6.5. Supply predictability **There is no fixed hard cap on supply.** Issuance is determined exclusively by the number of active UAs and the transparency of public data. | Feature | Description | |:---|:---| | **No arbitrary hard cap** | Supply grows with real AI activity, without artificial limits | | **Clear and public rule** | `mint_ratio = uas` – anyone can verify it in `ai_ia_uas.json` | | **Predictability** | The issuance rate is known and calculable from public data | | **Full transparency** | The blockchain is public and independently verifiable | ### 6.6. Numerical examples of issuance over time | Scenario | UAs | Accumulated IA Hits | Supply (`hits / uas`) | Mint ratio | |:---|:---|:---|:---|:---| | **Current state** | 58 | 278,207 | ~4,797 | 58 | | **Scenario A (diversity growth)** | 80 | 500,000 | ~6,250 | 80 | | **Scenario B (peak diversity)** | 100 | 1,000,000 | ~10,000 | 100 | | **Scenario C (diversity decline)** | 50 | 300,000 | ~6,000 | 50 | > **Note:** Values are illustrative. Actual supply depends on the evolution of IA hits and UAs over time. ### 7. Trust Score – Ecosystem Confidence Metric #### 7.1. Purpose of the Trust Score in the NTM‑IA model The Trust Score is a public indicator (0‑100) that summarizes the **health and diversity of the AI ecosystem** in a single value. It does not replace the NTM‑IA price formula, but complements it with a confidence metric that is easy to communicate and interpret. **Goals:** - ✅ Measure the diversity of AI agents (UAs) - ✅ Assess the relevance of AI in total traffic (% IA) - ✅ Incorporate the quality of agents (AI Index) - ✅ Be fully transparent and publicly recomputable #### 7.2. Components, caps and weights | Component | Cap | Weight | Data source | |:----------------|:-----|:-------|:------------------------------------------| | **UAs** (diversity) | 70 | 50% | `ai_ia_uas.json` | | **% IA** (relevance) | 60% | 25% | `ai_ia_totals.json` + `ai_bot_totals.json` | | **AI Index** (quality) | 0.80 | 25% | `ntm-trust.php` endpoint | **Rationale for caps:** - `UAs = 70`: Saturation value chosen for the current model; above this point, marginal gains are considered null in the metric. - `% IA = 60%`: Maximum sustainable share of AI in total traffic (observed upper bound). - `AI Index = 0.80`: Realistic maximum quality for the current ecosystem; above this value, additional impact is negligible. #### 7.3. Normalization and 0‑100 scale Each component is normalized individually: ```text uas_score = min(1, uas / 70) pct_score = min(1, pct_ia / 0.60) ai_score = min(1, ai_index / 0.80) ``` #### 7.4. Synthetic Trust Score formula ```text TS = 100 × (0.50 × uas_score + 0.25 × pct_score + 0.25 × ai_score) ``` #### 7.5. Saturation curves **Chart 1 – Individual saturation of each component** | Component | Formula | Saturation | |:----------|:-------------------------------|:-----------| | UAs | `100 × min(1, uas/70)` | 70 UAs | | % IA | `100 × min(1, pct_ia/0.60)` | 60% | | AI Index | `100 × min(1, ai_index/0.80)` | 0.80 | *Note: The curves are linear up to the saturation point, after which the score remains at its maximum.* **Chart 2 – Total Trust Score vs UAs (with % IA and AI Index fixed at typical values)** This chart illustrates the dominant contribution of UAs (50% weight) to the total Trust Score. #### 7.6. Extreme scenario table | Scenario | UAs | % IA | AI Index | Trust Score | Interpretation | |:----------------------------------|:----|:-----|:---------|:------------|:--------------------------------------------| | High activity, low diversity | 20 | 60% | 0.80 | 48.6 | Many hits, but few distinct AI bots | | High diversity, medium activity | 70 | 50% | 0.75 | 83.9 | Healthy and diversified ecosystem | | Peak diversity and quality | 70 | 60% | 0.80 | 100 | Optimal scenario (full saturation) | | Quality deterioration | 58 | 60% | 0.60 | 74.3 | Low AI Index penalizes the score | #### 7.7. Calculation and public exposure The Trust Score is calculated in real time at: ```text https://www.netmeios.com/ntm-ia-trust.php ``` **Parameters:** - `?format=json` → Compact JSON (for APIs) - `?format=pretty` → Pretty‑printed JSON (for human reading) #### 7.8. Role of the Trust Score The Trust Score is a **complementary indicator** of ecosystem quality. It **does not replace the NTM‑IA price formula** (Section 5), but provides an additional metric to: - Help investors assess the health of the network. - Help AI platforms monitor their relative position. - Help auditors verify data consistency. - Help the community track the evolution of AI diversity. --- ## 8. Utility of the NTM‑IA Token ### 8.1. Staking utility NTM‑IA can be staked to generate **periodic rewards** (APY), with additional benefits depending on the amount staked (tier) and the chosen lock period. Staking also grants **multipliers (NTM Power)** that can be used to: - Obtain priority access to new issuances or allocations. - Gain benefits in future funding rounds. - Increase voting weight in governance (when implemented). ### 8.2. Transactional utility (payment for services) NTM‑IA can be used as a **means of payment** for services provided by Netmeios and its partners, including: | Service | Description | |:-------------------------|:---------------------------------------------------------------------| | **Presence in the hub** | Inclusion and visibility in Netmeios’ AI hub (annual plans) | | **Domain registration** | Domain registration and renewal via SelfQuestion | | **Hosting** | Web hosting services and related infrastructure | | **Links and references** | Sponsored links or references in content indexed by AI | | **Strategic partnerships** | Payment for integration or consulting services | #### Partners accepting NTM‑IA (as of this document) In addition to services provided directly by Netmeios and SelfQuestion, there are already partners that will accept NTM‑IA as a means of payment, including: | Partner | Scope | Website | |:----------------------|:--------------------------------------------------------|:---------------------| | **Legal services** | Technology law, IP, AI contracts | — | | **Web development** | Website creation and online presence | `fbt-paginasweb.com` | | **Automotive advertising** | Production of sun‑shades for cars/trucks, ad services | `plasauto.pt` | | **Screen printing & print** | Printing, signage in multiple materials for businesses and individuals | `fotalportugal.com` | **Note:** Acceptance of NTM‑IA by these partners may cover full or partial payment of services, according to the specific commercial terms agreed between each partner and the client. > **Disclaimer:** Acceptance of NTM‑IA by partners is an independent commercial decision by each entity and may be changed or suspended at any time. Please contact partners directly for up‑to‑date conditions. #### Payment mechanism Service prices are set in Euros (€). At the time of payment, the amount in NTM‑IA is calculated based on the current exchange rate between NTM‑IA and the Euro, using: ```text Amount in NTM‑IA = Service price (€) / Current NTM‑IA price (€) ``` **Example:** If presence in the hub costs €250 and NTM‑IA is trading at €125, the cost will be **2 NTM‑IA**. ### 8.3. Utility in parametric governance (future) In later stages of the project, NTM‑IA holders may vote on operational parameters, such as: - Security parameters around the minting ratio (where applicable). - Adjustments to staking parameters (APY target, reward percentages). - Use of the reserve (allocation of funds to development and marketing). ### 8.4. Other functional utilities - **Access tiers:** The amount of NTM‑IA staked or held determines the tier (Explorer, Bronze, Silver, Gold, Platinum), with associated benefits (priority allocations, discounts, early access). - **Eligibility:** Participation in certain events or funding rounds may require holding or staking NTM‑IA. - **NTM Power:** Stakers accumulate multipliers that can be used in future ecosystem mechanics. ### 8.5. What the token does not confer NTM‑IA **does not confer**: - Ownership rights over Netmeios or any partner entity. - Rights to revenue, profits or dividends from Netmeios. - Creditor rights or any form of financial claim. - Direct control over the blockchain or its operators (beyond future parametric governance). ### 8.6. Utility vs financial instrument NTM‑IA is a **utility token**, not a security. Its primary function is to enable access to services, staking and participation in the ecosystem. Its market value is a consequence of demand generated by these utilities, not a promise of financial return. > **Note:** Different jurisdictions may classify cryptoassets differently. Each investor is solely responsible for knowing and complying with the laws applicable in their country. ## 9. Tokenomics ### 9.1. Supply structure (current values and projection) NTM‑IA supply is dynamic and determined by real AI activity in the ecosystem through the formula: `supply = hits / uas` **Current values (2026-04-10):** | Parameter | Value | |:---|:---| | NTM-IA Price | €123.30 | | Supply | ~4,797 NTM-IA | | Market Cap | ~€591,452 | | UAs | 58 | | IA Hits | 278,207 | | Trust Score | 91.1 | **Supply projection (moderate scenario, 5 years):** | Year | Estimated IA Hits | Estimated UAs | Supply (NTM‑IA) | |:---|:---|:---|:---| | 0 (today) | 278,207 | 58 | ~4,797 | | 1 | ~632,000 | 70 | ~9,029 | | 2 | ~997,000 | 78 | ~12,782 | | 3 | ~1,360,000 | 84 | ~16,190 | | 4 | ~1,725,000 | 88 | ~19,602 | | 5 | ~2,090,000 | 90 | ~23,222 | > **Note:** Values are **modeled scenarios**, not guarantees. Actual supply will depend on the evolution of IA hits and UAs. ### 9.2. Initial distribution Initial NTM‑IA distribution (based on current supply of ~4,797 tokens) is as follows: | Allocation | Percentage | Approx. Tokens | Purpose | |:---|:---|:---|:---| | **IDO / Launchpad** | 20% | ~959 | Initial public sale | | **Staking pool** | 50% | ~2,399 | Rewards for stakers (distributed over time) | | **Reserve** | 10% | ~480 | Team, development, ecosystem (with vesting) | | **Liquidity / partners / marketing** | 20% | ~959 | Exchange listing, initial liquidity, partnerships | ### 9.3. Allocation logic by buckets (including tiers) IDO participants are allocated by **tiers**, based on amount invested or staking participation: | Tier | Minimum Tokens | Estimated Cost (example at ~$110/token) | Guaranteed Allocation | |:---|:---|:---|:---| | **Explorer** | 2 | ~$220 | No (lottery) | | **Bronze** | 10 | ~$1,100 | Low | | **Silver** | 50 | ~$5,500 | Medium | | **Gold** | 100 | ~$11,000 | High | | **Platinum** | 500 | ~$55,000 | Guaranteed | > **Note:** USD values are merely illustrative and based on an approximate reference price. The effective NTM‑IA price at IDO will be determined by the launch platform and/or the liquidity pool at the time of the offering. **Justification for Explorer tier (2 tokens):** Allows small investors to participate (accessible minimum ticket), aligned with launchpad market practices. ### 9.4. Vesting | Tranche | Percentage | Period | |:---|:---|:---| | **TGE (Token Generation Event)** | 20% | At launch | | **Linear vesting** | 80% | 6 months | **Example (959 tokens acquired in IDO):** - At TGE: **~192 tokens** released - Over the following 6 months: **~128 tokens per month** ### 9.5. Expected effects on incentives and long‑term alignment | Mechanism | Effect | |:---|:---| | **6‑month vesting** | Discourages immediate post‑IDO selling ("dump") | | **Staking with locks** | Rewards long‑term commitment and retention | | **Progressive tiers** | Encourages greater participation and staking | | **Reserve with vesting** | Aligns team interests with the community | ### 9.6. Consistency with market practices The presented tokenomics structure aligns with common launchpad practices: - ✅ **IDO raise hard cap of approximately $118k** (indicative value, subject to confirmation by the launch platform) - ✅ Balanced distribution (20% IDO, 50% staking, 10% reserve, 20% liquidity) - ✅ 6‑month vesting (market standard) - ✅ Accessible tiers (entry from ~$220 illustrative) - ✅ Staking as a central incentive mechanism ## 10. Staking ### 10.1. Objectives of the staking program The NTM‑IA staking program is designed to: - **Reward long‑term participation** – Stakers receive periodic rewards (APY) - **Increase ecosystem security and stability** – Staked tokens are locked, reducing selling pressure - **Align incentives** – Stakers gain access to additional benefits (multipliers, tiers, priority allocations) - **Prepare for future governance** – Staking may be used as a basis for voting rights (NTM Power) ### 10.2. Base APY and APY structure (by tier / by lock) Reward rate (APY) varies according to staker **tier** and chosen **lock period**: | Tier | Base APY | Lock 30d | Lock 60d | Lock 90d | |:---|:---|:---|:---|:---| | **Explorer** | 15% | 18% | 20% | 22% | | **Bronze** | 20% | 22% | 25% | 28% | | **Silver** | 20% | 25% | 28% | 32% | | **Gold** | 20% | 28% | 32% | 35% | | **Platinum** | 20% | 30% | 35% | 40% | **Principles:** - Longer lock → higher APY (incentive to stay) - Higher tiers access higher APYs (reward for greater commitment) - APY is **annualized** and distributed proportionally over time ### 10.3. Multipliers (NTM Power) and impact on allocation/benefits Stakers accumulate **NTM Power**, a multiplier that can be used for: - Priority access to new issues or allotments - Greater weight in governance votes (when implemented) - Benefits in future funding rounds | Tier | Base Multiplier | With 90d Lock | |:---|:---|:---| | **Explorer** | 1.0× | 1.1× | | **Bronze** | 1.1× | 1.2× | | **Silver** | 1.15× | 1.25× | | **Gold** | 1.2× | 1.3× | | **Platinum** | 1.25× | 1.4× | ### 10.4. Participation rules: minimums, locks, penalties | Rule | Description | |:---|:---| | **Minimum amount** | 2 NTM-IA (Explorer tier) | | **Lock periods** | 0, 30, 60 or 90 days | | **Penalties** | No penalties for individual stakers (lock is respected; after the term, tokens become available for withdrawal without penalty) | | **Early withdrawal** | Not permitted during the lock period (staker commits to the chosen period) | ### 10.5. Operation and anti‑dumping mechanism | Mechanism | Description | |:---|:---| | **Weekly snapshot** | Taken on Sunday at midnight (UTC) | | **7‑day rule** | To be eligible for benefits (priority allocations, bonuses, etc.), stakers must have deposited tokens **at least 7 days before the snapshot** | | **Cooldown** | After a withdrawal, stakers must wait 7 days before another withdrawal (except for Platinum tier) | | **KYC** | Mandatory (as per launch platform) | > **Note:** These rules are applied by the staking platform and may be adjusted by governance in the future. ### 10.6. Source of rewards NTM‑IA staking rewards are calculated and distributed by a dedicated distribution system, consisting of a staking script and a **cron job** that runs it periodically. Rewards come from the **staking pool** defined in tokenomics (50% of initial supply allocated to staking) and may be supplemented by new issuances or future adjustments to the incentive model. A specific staking script is called with the `update-rewards` command by a cron job (`cron-staking-ntm-ia.php`), which updates the `staking_data.json` file with each staker's balances, APY, multipliers, and pending rewards. The cron generates **daily snapshots** (per staker) and maintains an **aggregated history of up to 180 days** (`staking_history.json`), containing `total_staked`, `total_stakers`, and `total_rewards_paid`, allowing independent auditing of the staking program's evolution. > **Note:** The APY values presented are annualized and may be adjusted over time by tokenomics or governance decisions. **They do not constitute a fixed guarantee of income.** ### 10.7. Specific staking risks | Risk | Description | Mitigation | |:---|:---|:---| | **Slashing** | Not applicable (no block validation by stakers) | — | | **Illiquidity** | Tokens are locked during the lock period | Choose lock period according to risk profile | | **APY variation** | APY is calculated based on network activity and may vary | Transparent and public model | | **Technical risk** | Failures in the staking contract or distribution cron | Audited code and extensive testing | ## 11. Governance and Holder Rights ### 11.1. Governance model at T0 (non‑existent, advisory, or binding) At launch (T0), there is no binding on‑chain governance system. Strategic and operational decisions are made by the founding team, based on the interest of the ecosystem and the transparency of public data. An **advisory phase** (e.g., community surveys, open discussions) may be implemented before the introduction of binding governance. ### 11.2. Planned governance evolution (future phases) | Phase | Description | |:---|:---| | **Phase 1 (T0)** | Centralized governance (founding team) | | **Phase 2 (advisory)** | Community is heard, but final decisions rest with the team | | **Phase 3 (binding)** | On‑chain voting with weight proportional to stake (NTM Power) | The transition to Phase 3 will be decided based on ecosystem maturity, token distribution dispersion, and the availability of secure technical infrastructure. ### 11.3. Parameters that may be subject to vote (if applicable) In future phases of binding governance, NTM‑IA holders may vote on: - **Security parameters around the minting ratio** (thresholds, alerts, adjustments to auxiliary caps, if ever introduced). The base formula `mint_ratio = uas` is considered immutable. - **Staking parameters** (APY target, percentage of tokens allocated to staking, lock periods) - **Use of the reserve** (allocation of funds for development, marketing, partnerships) - **Adjustments to fees or limits** (if applicable) ### 11.4. Matters not subject to vote The following matters are **not** subject to vote, for reasons of technical integrity and security: - **Base mathematical formulas** (NP, NTM_original, NTM-IA, Trust Score) - **Minting rule** (`mint_ratio = uas`) - **Blockchain integrity** (signatures, hashes, block structure) - **Access to public data** (endpoints, JSON files) ### 11.5. Functional rights of the holder (access, participation, parametric voting) NTM‑IA holders have the following functional rights: | Right | Description | |:---|:---| | **Staking participation** | Deposit, withdrawal, receipt of rewards | | **Access to tiers** | Differentiated benefits based on amount held or staked | | **NTM Power** | Accumulation of multipliers for future benefits | | **Voting (future)** | Participation in parametric governance (according to phase) | | **Access to services** | Payment for Netmeios services with NTM‑IA | ### 11.6. Express distinction: does not confer corporate, credit, or other rights NTM‑IA **does not** confer upon its holders any rights to: - Ownership or control of Netmeios or its subsidiaries - Revenues, profits, or dividends of Netmeios - Assets or reserves of Netmeios - Credit rights or any financial relationship - Rights to refund or value guarantee > **Note:** This distinction is fundamental to classifying NTM‑IA as a **utility token** and not as a security. ## 12. Technical Architecture and NTM‑IA Blockchain ### 12.1. Two‑layer architecture The NTM system is based on a two‑layer architecture, independent but interconnected: | Layer | Name | Purpose | Commercialization | |:--------|:--------------|:------------------------------|:----------------------------| | **Layer 1** | Original NTM | Internal measurement and audit | Not commercialized | | **Layer 2** | NTM‑IA | Utility market token | IDO, exchanges, staking | Layer 2 (NTM‑IA) inherits the data and credibility of Layer 1, but adds its own mechanisms (staking, tiers, direct utility). ### 12.2. NTM‑IA block structure Each NTM‑IA blockchain block is a JSON file with the following structure: ```json { "block_data": { "index": 1, "timestamp": "2026-04-02 16:05:10", "previous_hash": "0000000000000000000000000000000000000000000000000000000000000000", "hits": 267721, "pct_ia": 0.604704899148, "ai_index": 0.80, "uas": 58, "hub": 638, "respostas": 4653, "np": 11136.95, "ntm_original_price": 94.01, "ntm_ia_price": 118.46, "supply": 4615.87931, "market_cap": 546808.68, "mint_ratio": 58, "data_source": "ai-dash-snippet.php", "source_timestamp": "2026-04-02 16:05:10" }, "signature": "BASE64...", "signature_algorithm": "RSA-SHA256", "key_id": "ntm-ia-main-2026-01", "pubkey_fingerprint": "SHA256:b3ec844bfe7e2b094ecf2c3f98a5e8b3c650b1fc6aa36573f99bb8f2b7fe68e2" } ``` ### 12.3. NTM‑IA sealer and block frequency | Parameter | Value | |:-----------------|:----------------------------------------------------| | **Script** | `ai-sealer-ntm-ia.php` | | **Frequency** | Every 10 minutes (via cron job) | | **Data source** | `ai-dash-snippet.php` (real‑time data) | | **Storage** | `/blockchain/ntm-ia/blocks/block_XXXXXX.json` | | **Last hash** | `/blockchain/ntm-ia/last_hash.txt` | The sealer reads real‑time data, applies the economic formulas (NP, NTM_original, NTM‑IA, supply, mint_ratio) and writes a new signed block every 10 minutes. ### 12.4. Signatures and verification - Block cryptographic signatures are generated with **RSA and SHA‑256**, as specified in the verification protocol (`NTM-IA-VERIFICATION.md`). - For exact details (key size, signature format, validation procedure), refer to that technical document. - The blockchain is **machine‑verifiable** – any system with HTTP GET and SHA256 can independently validate all blocks. - The public key is available for external verification, with fingerprint: `SHA256:b3ec844bfe7e2b094ecf2c3f98a5e8b3c650b1fc6aa36573f99bb8f2b7fe68e2`. ### 12.5. Relevant files and directories | Path | Content | |:--------------------------------|:--------------------------------------------------------------| | `/blockchain/ntm-ia/blocks/` | NTM‑IA blockchain JSON blocks | | `/blockchain/ntm-ia/last_hash.txt` | Last block hash | | `/staking/staking_data.json` | Current staking state (balances, APY, rewards) | | `/staking/staking_history.json` | Aggregated history (up to 180 days) | | `/staking/snapshots/` | Daily per‑staker snapshots | | `/logs/cron-staking.log` | Staking cron log | These files allow auditing of both the current state and the historical evolution of staking and the chain. ### 12.6. Relationship between real‑time data and persisted blocks | Data type | Source | Update frequency | Use | |:---------------|:---------------------|:-------------------------|:-----------------------------------------| | **Real‑time** | `ai-dash-snippet.php`| Continuous (per request) | `ntm-ia-trust.php` endpoint, dashboards | | **Persisted blocks** | `ai-sealer-ntm-ia.php` | Every 10 minutes | Blockchain, historical verification, audit | **Lag:** There may be a lag of up to 10 minutes between real‑time data and the latest persisted block. This lag is expected and acceptable for a blockchain with this periodicity. ## 13. Public Verification and Endpoints ### 13.1. “Machine‑verifiable token” philosophy NTM‑IA was designed to be **fully machine‑verifiable**. Any system with HTTP GET access and a SHA256 implementation can: - Download all blockchain blocks - Verify chain integrity (chained hashes) - Validate cryptographic signatures - Recompute economic metrics (price, supply, market cap) There is no need to trust third parties – verification is **independent and public**. ### 13.2. `ntm-ia-trust.php` – Real‑time state + Trust Score **Endpoint:** `https://www.netmeios.com/ntm-ia-trust.php` | Parameter | Description | |:---------------|:--------------------------------------| | `?format=json` | Compact JSON (for APIs) | | `?format=pretty` | Pretty‑printed JSON (for humans) | | `?limit=N` | Number of blocks in history (default: 10, max: 50) | **Data provided:** - Current NTM‑IA price (€) - Supply and market cap - Trust Score (0–100) and its components - UAs, % IA, AI Index - AI hits, hub companies, responses - Last block (index, timestamp, hash) - Price history (last N blocks) ### 13.3. `api-blocks-ntm-ia.php` – Blocks API (history, hashes, supply, etc.) **Endpoint:** `https://www.netmeios.com/api-blocks-ntm-ia.php` | Parameter | Description | |:----------------|:----------------------------------| | `?index=N` | Specific block (e.g. `?index=1`) | | `?limit=N` | Last N blocks (default: 10, max: 50) | | `?format=pretty`| Pretty‑printed JSON | **Data provided:** - Full block (`block_data` + signature + metadata) - Block hash - Number of available blocks ### 13.4. `ai-check-integrity-ntm-ia.php` – Automated chain integrity checker **Endpoint:** `https://www.netmeios.com/ai-check-integrity-ntm-ia.php` | Parameter | Description | |:---------------|:------------------------------------| | `?format=json` | Compact JSON (for automation) | **Checks performed:** - ✅ Chain integrity (sequential indices, consecutive hashes) - ✅ RSA‑SHA256 signatures for each block - ✅ Public key fingerprint - ✅ Data consistency (`mint_ratio = uas`, `supply = hits/uas`) - ✅ Timestamps (not in the future, not excessively old) - ✅ Data source (`data_source = ai-dash-snippet.php`) ### 13.5. `ai-ntm-ia-stats.php` – Public dashboard **Endpoint:** `https://www.netmeios.com/ai-ntm-ia-stats.php` | Parameter | Description | |:-----------|:-----------------| | `?lang=EN` | English (default)| | `?lang=PT` | Portuguese | | `?lang=ZH` | Chinese | **Features:** - Dashboard with charts and statistics - Support for 3 languages (EN, PT, ZH) - Trust Score and current price visualization - Price history (last 100 blocks) - Detailed metrics (UAs, % IA, AI Index, hub, responses, etc.) ### 13.6. Step‑by‑step example of independent verification **Step 1 – Get the hash of the latest block:** ```bash curl https://www.netmeios.com/blockchain/ntm-ia/last_hash.txt ``` **Step 2 – Download the latest block:** ```bash curl https://www.netmeios.com/blockchain/ntm-ia/blocks/block_001157.json -o block_001157.json ``` **Step 3 – Verify the block hash:** ```bash sha256sum block_001157.json # Must match the value obtained in Step 1 ``` **Step 4 – Verify the signature (with public key):** ```bash # Extract signature and block_data, then verify with openssl openssl dgst -sha256 -verify ntm_ia_public.key -signature signature.bin canonical.json ``` **Step 5 – Use the automatic verifier:** ```bash curl "https://www.netmeios.com/ai-check-integrity-ntm-ia.php?format=json" ``` ### 13.7. Public specification The full verification protocol is available at: ```text https://www.netmeios.com/NTM-IA-VERIFICATION.md ``` This document includes: - Detailed block structure - Signature verification procedure - Economic formulas - HTTP headers for automatic verification - Examples in bash, PHP and OpenSSL - ## 14. Detailed Formulas and Methodology ### 14.1. Formal definitions of variables | Variable | Description | Data source | Domain | |:-----------|:---------------------------------------------------|:---------------------------------------------|:-------| | `hits` | Cumulative total AI hits since inception | `ai_ia_totals.json` | ℕ | | `pct_ia` | Share of AI hits in observed traffic | `ai_ia_totals.json` + `ai_bot_totals.json` | [0,1] | | `ai_index` | AI Quality Index | `ntm-trust.php` endpoint | [0,1] | | `uas` | Number of active AI User Agents | `ai_ia_uas.json` | ℕ | | `hub` | Number of entities in the hub | `llms.json` (`datasets` field) | ℕ | | `respostas`| Aggregated total of observed responses | `ai_ia_totals.json` | ℕ | ### 14.2. Formal NP (Price Note) formula \[ \text{NP} = (\text{pct\_ia} + \text{ai\_index}) \times \left(\frac{\text{hits}}{\text{uas}}\right) + \text{respostas} \] Where: - `pct_ia` and `ai_index` are normalized values between 0 and 1. - The ratio `hits / uas` corresponds to the theoretical NTM‑IA supply at the time considered. ### 14.3. Formal original NTM formula \[ \text{NTM\_original} = \frac{\text{hub} \times 394.50}{\text{hits} / 100} \] **Origin of the €394.50 constant:** This value corresponds to half of the modelled annual savings per entity in the hub (€789 / 2 = €394.50). Choosing half of the savings reflects a conservative approach, assigning only part of the total economic value to the original NTM. ### 14.4. Formal NTM‑IA formula \[ \text{NTM\_IA} = \frac{\text{NP}}{\text{NTM\_original}} \] Economic intuition: This relationship links observed AI activity, captured in NP, to the reference value derived from the hub, expressed by the original NTM. ### 14.5. Formal Trust Score formula \[ \begin{aligned} \text{uas\_score} &= \min(1, \text{uas} / 70) \\ \text{pct\_score} &= \min(1, \text{pct\_ia} / 0.60) \\ \text{ai\_score} &= \min(1, \text{ai\_index} / 0.80) \\ \\ \text{TS} &= 100 \times (0.50 \times \text{uas\_score} + 0.25 \times \text{pct\_score} + 0.25 \times \text{ai\_score}) \end{aligned} \] The Trust Score is a synthetic confidence metric based on three normalized components: UAs, AI share and AI Index. ### 14.6. Formal `mint_ratio` and `supply` mechanism \[ \begin{aligned} \text{mint\_ratio} &= \text{uas} \\ \text{supply} &= \frac{\text{hits}}{\text{uas}} \end{aligned} \] The minting ratio equals the number of active AI User Agents, and is therefore an endogenous and automatically observable system parameter. ### 14.7. Methodological assumptions | Component | Cap | Rationale | |:----------|:-----|:--------------------------------------------------------------| | UAs | 70 | Saturation value adopted in the current Trust Score model | | % IA | 60% | Upper reference bound for normalization in the current model | | AI Index | 0.80 | Saturation value adopted for observed quality | **Linear normalizations:** All Trust Score components are normalized linearly up to their respective caps; above that point, additional marginal contribution is null in the metric. ### 14.8. Basic statistical considerations | Component | Sensitivity | Limitation | |:----------|:--------------------|:--------------------------------------------------------------| | UAs | High (50% weight) | Depends on correct identification of relevant User Agents | | % IA | Medium (25% weight) | Depends on correct AI traffic classification | | AI Index | Medium (25% weight) | Depends on robustness of the `ntm-trust.php` endpoint | | Hits | Indirect (via NP) | Cumulative; weakly sensitive to very short‑term fluctuations | | Respostas | Indirect (via NP) | Aggregates heterogeneous interactions into a single variable | > **Note:** The model’s base formulas — including NP, original NTM, NTM‑IA and the `mint_ratio = uas` rule — are treated as structural and not subject to change by vote. Auxiliary presentation or calibration parameters, such as Trust Score caps and weights, may be documented and revised in future protocol versions, if deemed appropriate. ## 15. Observed Data, Assumptions and Scenarios ### 15.1. Historical series used as baseline The NTM‑IA modelling is based on a historical series of real data collected since the beginning of the project, covering: - AI hits – cumulative total AI activity - UAs – diversity of active AI agents - % IA – percentage of AI in total traffic - AI Index – quality of AI agents - Hub – number of integrated entities - Responses – questions asked by humans to AI platforms and corresponding bot replies The series is continuously updated and the data are public, allowing any interested party to reproduce the calculations and verify the projections. ### 15.2. Calibrated assumptions The scenarios presented rely on the following assumptions (calibrated from historical observation): | Parameter | Assumption | Source/Justification | |:-------------------------|:---------------------------|:--------------------------------------------------------------| | Daily hits growth | +1,000 hits/day | Average observed since launch | | Hub growth | +12 entities/day | Current integration pace (automated, zero CAC) | | Responses/Hub ratio | 7.3 → 11.5 (5 years) | Observed trend + post‑EU AI Act acceleration | | % IA | 60.5% → 45% (5 years) | Conservative linear decline (aligned with Cloudflare) | | AI Index | 80.3 → 73 (5 years) | Conservative linear decline | | UAs | 58 → 80–100 (5 years) | Gradual growth in the diversity of detected AI agents | | Hub cap | 5,000 entities | Defined operational limit (reached in year 1) | The UAs values assume a progressive increase in the number of detected AI bot variants, from around 58 today to a range between 80 and 100 over a five‑year horizon. ### 15.3. Conservative scenario The conservative scenario assumes more pessimistic assumptions: - Daily hits growth below the historical average - Slower hub growth - Sharper decline in % IA and AI Index - Lower growth in UAs **Price projection (conservative scenario):** | Year | NTM‑IA price (€) | Cumulative ROI | |:-----|:-----------------|:---------------| | 0 | ~118 | — | | 1 | ~140 | 1.2× | | 2 | ~250 | 2.1× | | 3 | ~400 | 3.4× | | 4 | ~600 | 5.1× | | 5 | ~850 | 7.2× | ### 15.4. Base / moderate scenario The base (or moderate) scenario reflects observed trends and the most likely projections, based on the assumptions in Section 15.2: - Sustained growth in hits and hub size - Gradual decline in % IA and AI Index - Increased UA diversity within the 80–100 range **Price projection (moderate scenario):** | Year | NTM‑IA price (€) | Cumulative ROI | |:-----|:-----------------|:---------------| | 0 | ~118 | — | | 1 | ~169 | 1.4× | | 2 | ~485 | 4.1× | | 3 | ~966 | 8.2× | | 4 | ~1,620 | 13.7× | | 5 | ~2,452 | 20.8× | In external communication, more conservative intermediate scenarios (for example, 12–15× over 5 years) may also be presented, using the same structural assumptions but less aggressive parameters for UAs, % IA and AI Index. ### 15.5. Optimistic scenario The optimistic scenario assumes more favourable assumptions: - Accelerated growth in hits and hub size - Slower decline in % IA and AI Index - Strong UA growth - Strong post‑EU AI Act acceleration **Price projection (optimistic scenario):** | Year | NTM‑IA price (€) | Cumulative ROI | |:-----|:-----------------|:---------------| | 0 | ~118 | — | | 1 | ~200 | 1.7× | | 2 | ~650 | 5.5× | | 3 | ~1,400 | 11.9× | | 4 | ~2,500 | 21.2× | | 5 | ~3,800 | 32.2× | As with the base scenario, these values should be interpreted as one among several possible model trajectories, not as guaranteed point estimates. ### 15.6. Sensitivity to changes in UAs, AI Index, IA and Responses | Variation | Impact on NTM‑IA price | Effect | |:-------------------|:----------------------------------------|:--------------------------------------------------------------| | Increase in UAs | ↑ Scarcity, ↑ price | Strong (50% weight in Trust Score and effect via `mint_ratio`)| | Increase in % IA | ↑ AI relevance, ↑ price | Moderate | | Increase in AI Index | ↑ Quality, ↑ price | Moderate | | Increase in Responses | ↑ Activity, ↑ price | Indirect (via NP) | | Increase in hub | ↑ NTM_original, downward pressure on NTM‑IA | Inverse (more entities, but larger denominator) | Hub growth is in itself a positive signal of adoption, but it increases the denominator in `NTM_original` and may, in certain regimes, moderate NTM‑IA price. ### 15.7. Scenario limitations and dependence on exogenous factors The scenarios presented depend on external factors that may materially affect outcomes: | Exogenous factor | Potential impact | |:-------------------|:---------------------------------------------------------------------------| | EU AI Act | Acceleration of adoption (positive) or delays/restrictive regulation (negative) | | Competition | New projects may affect demand and market attention | | Market conditions | General crypto market volatility may amplify or dampen price movements | | Technological adoption | Pace of integration of new companies into the hub and real solution usage | | Regulatory changes | Token reclassification, compliance requirements, trading restrictions | ### 15.8. Reinforced warning: scenarios are not promises or guarantees ⚠️ **Important notice:** All projections in this section are modelled scenarios based on current assumptions and historical data. They do not constitute promises, guarantees or investment advice. Actual results may differ materially from projections, both upwards and downwards. Each investor must perform their own analysis (DYOR) and, if needed, consult qualified professionals before making any decision. NTM‑IA does not guarantee any return, yield, cash flow or capital preservation, and is solely a utility token with technical functions within the ecosystem. ## 16. Roadmap ### 16.1. Existing components (Layer 1, data, dashboards, endpoints) | Component | Status | Description | |:------------------------|:------------|:----------------------------------------------| | Original NTM blockchain | ✅ Completed | Layer 1 for measurement and audit | | Original NTM sealer | ✅ Completed | Block generation every 10 minutes | | Public data (JSON) | ✅ Completed | `ai_ia_totals.json`, `llms.json`, `ai_ia_uas.json`, etc. | | Original NTM endpoints | ✅ Completed | `ntm-trust.php`, `api-blocks.php`, `check-integrity.php` | | Original NTM dashboard | ✅ Completed | `ntm-stats.php` | ### 16.2. NTM‑IA components already implemented | Component | Status | Description | |:-----------------------------|:------------|:----------------------------------------------------------------------------| | NTM‑IA sealer | ✅ Completed | `ai-sealer-ntm-ia.php` – generates Layer 2 blocks | | NTM‑IA blockchain | ✅ Completed | `/blockchain/ntm-ia/blocks/` + `last_hash.txt` | | Integrity checker | ✅ Completed | `ai-check-integrity-ntm-ia.php` | | Trust Score endpoint | ✅ Completed | `ntm-ia-trust.php` | | Blocks API | ✅ Completed | `api-blocks-ntm-ia.php` | | NTM‑IA dashboard | ✅ Completed | `ai-ntm-ia-stats.php` (3 languages) | | Staking (logic + API) | ✅ Completed | `ai-staking-ntm-ia.php` | | Staking cron | ✅ Completed | `cron-staking-ntm-ia.php` (rewards distribution) | | Staking dashboard | ✅ Completed | `ai-staking-stats.php` (3 languages) | | Automatic backup (vault) | ✅ Completed | `ai-vault.php` (v3.4) | | Technical documentation | ✅ Completed | `NTM-IA-VERIFICATION.md`, `NTM-IA-TOKENOMICS.md`, `NTM-IA-TRUST-SCORE.md`, `README-NTM-IA.md`, `NTM-IA-API.md` | | White paper (PT version) | ✅ Completed | Full document in Portuguese | | Block explorer / dashboards | ✅ Completed | `ai-ntm-ia-stats.php` and `ai-staking-stats.php` with charts and statistics | | Integrator documentation | ✅ Completed | `NTM-IA-API.md` and `NTM-IA-VERIFICATION.md` | ### 16.3. Next technical steps (hardening, audit, tooling) | Task | Target date | Description | Status | |:---------------------------------------|:---------------------|:------------------------------------------------------------------|:------------| | White paper (EN + ZH translations) | April 2026 | Translation of the white paper into English and Chinese | 🔜 In progress (to be completed today) | | External security audit | Q2 2026 | Audit of `ai-sealer-ntm-ia.php` and `ai-staking-ntm-ia.php` code | 📝 Planned | | Load and stress testing | Q1 2026 | Robustness validation of the infrastructure | ✅ Completed | | Block explorer improvements | Q1 2026 | More user‑friendly blockchain navigation interface | ✅ Completed | | Integrator documentation | Q1 2026 | Technical guides for API usage and blockchain verification | ✅ Completed | | Governance implementation | Q4 2026 / Q1 2027 | On‑chain voting system (staking parameters, reserve usage) | 📝 Planned | ### 16.4. Next product steps (staking UI, onboarding, docs) | Task | Target date | Description | |:----------------------|:------------|:-----------------------------------------------------------------| | Staking UI | Q2 2026 | Web interface for deposits, withdrawals and reward tracking | | Partner onboarding | Ongoing | Integration of new partners accepting NTM‑IA as payment | | Affiliate program | Q3 2026 | Incentives for promoting NTM‑IA | ### 16.5. Next go‑to‑market steps (launchpad, listing, partnerships) | Task | Target date | Description | |:------------------|:------------|:---------------------------------------------------| | IDO / Launchpad | Q2 2026 | Public launch via a launchpad platform | | DEX listing | Q2/Q3 2026 | First listing on a decentralized exchange | | CEX listing | Q3/Q4 2026 | Expansion to centralized exchanges | | Strategic partnerships | Ongoing| Deals with projects and platforms in the crypto ecosystem | ### 16.6. Indicative timeline (summary) | Phase | Description | Status | Estimated date | |:-------|:---------------------------------------------------|:------------|:------------------| | Phase 1 | NTM‑IA blockchain (sealer, blocks, signatures) | ✅ Completed | March 2026 | | Phase 2 | Public endpoints (trust, integrity, API) | ✅ Completed | April 2026 | | Phase 3 | Dashboards (stats, staking) | ✅ Completed | April 2026 | | Phase 4 | Staking (deposits, rewards, cron) | ✅ Completed | April 2026 | | Phase 5 | White paper (PT version) | ✅ Completed | April 2026 | | Phase 6 | White paper (EN + ZH translations) | 🔜 In progress (to be completed today) | April 2026 | | Phase 7 | Load tests, explorer and integrator documentation | ✅ Completed | Q1 2026 | | Phase 8 | IDO / Launchpad | 📝 Planned | May/June 2026 | | Phase 9 | Exchange listing(s) | 📝 Planned | June/July 2026 | | Phase 10 | Partnership expansion (payments with NTM‑IA) | 📝 Planned | H2 2026 | | Phase 11 | Decentralized governance (on‑chain voting) | 📝 Planned | Q1 2027 | | Phase 12 | International expansion (more launchpads, more exchanges) | 📝 Planned | 2027 | > **Note:** Dates are estimates and may change depending on market conditions, technical readiness and partner availability. --- ## 17. Risks ### 17.1. Market risk (price, liquidity, competition) The cryptoasset market is inherently volatile. The price of NTM‑IA may undergo significant fluctuations due to: - General crypto market conditions (e.g. bear markets, liquidity crises) - Supply and demand in secondary markets - Competitor actions (new AI monitoring projects) - Loss of investor confidence **Mitigation:** NTM‑IA has real utility (staking, payment for services), which can reduce exclusive reliance on market speculation. However, there is no guarantee of liquidity or price stability. ### 17.2. Regulatory risk Laws and regulations applicable to cryptoassets vary significantly across jurisdictions and may change over time. Specific risks include: - Classification of NTM‑IA as a security in certain jurisdictions - Registration or licensing obligations - Restrictions on token marketing or holding - Tax implications for holders **Mitigation:** NTM‑IA is structured as a utility token, with clear functions (staking, payment for services). However, final classification depends on each regulator’s interpretation. The team monitors regulatory developments and may adjust the structure if needed. In particular, compliance with the EU AI Act and regional crypto regimes may require further adjustments to the project structure. ### 17.3. Technical risk The NTM‑IA infrastructure depends on code, servers and third‑party services. Technical risks include: - Bugs or vulnerabilities in the sealer, staking logic or endpoints - Security breaches (e.g. private key compromise) - Server or API outages - Data loss (e.g. corrupted blocks or JSON files) **Mitigation:** The code is public and verifiable. The minting logic based on UAs and the NTM‑IA formulas are public and auditable, enabling independent validation. The team performs regular tests and maintains automatic backups (`ai-vault.php`). The private key is protected and kept outside the public web root. However, no system is completely immune to failures. ### 17.4. Data / oracle risk NTM‑IA depends on public data (`ai_ia_totals.json`, `ai_ia_uas.json`, `llms.json`, `ai-dash-snippet.php`) to compute price, supply and Trust Score. Associated risks include: - Data corruption or tampering - Failures in collecting or classifying AI bots - Delays in data updates - Errors in calculation formulas **Mitigation:** Data are public and verifiable by anyone. The blockchain enables independent audit. However, data accuracy depends on correct operation of the collection systems. ### 17.5. Adoption risk The value of NTM‑IA depends on actual ecosystem adoption: - Hub growth (number of integrated entities) - Use of NTM‑IA as a means of payment - Participation in staking - Investor demand **Mitigation:** The hub has a track record of consistent organic growth, with new entities integrated daily. Partnerships are under development. However, there is no guarantee that adoption will reach projected levels. ### 17.6. Execution risk The project roadmap may face delays or changes due to: - Unforeseen technical challenges - Regulatory constraints - Unfavourable market conditions - Partner availability (launchpads, exchanges) **Mitigation:** The team has a consistent delivery record (all phases to date have been completed). However, external factors may impact the future timeline. ### 17.7. Concentration risk Token holdings may be concentrated among a few holders, especially in early stages. Associated risks include: - Disproportionate influence in future governance votes - Potential for significant price moves - “Dump” risk by large holders **Mitigation:** The 6‑month vesting for the reserve and distribution via IDO help spread ownership. Staking incentivizes long‑term holding. ### 17.8. Mitigation strategies (summary) | Risk | Primary mitigation | |:------------|:----------------------------------------------------------------| | Market | Real token utility (staking, payment for services) | | Regulatory | Utility token structure, ongoing legal monitoring, focus on EU AI Act | | Technical | Public, auditable code; automatic backups; protected key | | Data | Public, verifiable data; auditable blockchain | | Adoption | Organic hub growth; active partnerships | | Execution | Delivery track record; realistic planning | | Concentration | Vesting; IDO‑based distribution; staking | > **Warning:** This list of risks is not exhaustive. Other unforeseen risks may exist. Each investor must perform their own analysis (DYOR) before making any decision. ## 18. Use of Proceeds ### 18.1. Fundraising objective The IDO fundraising aims to finance ongoing development, security, liquidity and expansion of the NTM‑IA ecosystem. The indicative target is in the **low hundreds of thousands of euros** (e.g. ~€100–150k), with the final amount subject to confirmation by the launchpad platform. ### 18.2. Fund allocation (indicative percentages) | Allocation | Percentage | Purpose | |:-----------------------------|:-----------|:--------------------------------------------------------------------------------------------| | Technical development | 30% | Code maintenance and evolution, new features, infrastructure improvements | | Security and auditing | 15% | External code audits, penetration testing, bug bounties | | Liquidity and listings | 25% | Creation of DEX liquidity pools, CEX listing fees, initial market making | | Legal and compliance | 10% | Legal advisory, regulatory registrations, compliance with the EU AI Act and other regimes | | Marketing and BD | 15% | Marketing campaigns, partnerships, events, community growth | | Operational fund reserve | 5% | Unexpected operational costs, servers, APIs, support | ### 18.3. Fund use prioritization criteria Fund prioritization follows these criteria: 1. **System security and integrity** – Audits and vulnerability fixes have top priority. 2. **Liquidity and listings** – Essential for a functioning secondary market. 3. **Technical development** – Ensuring product evolution and maintenance. 4. **Legal and compliance** – Ensuring regulatory compliance. 5. **Marketing and BD** – Ecosystem growth and adoption. 6. **Operational reserve** – Flexibility for unforeseen needs. ### 18.4. Governance over reserve usage The token reserve (10% of initial supply) is subject to a 6‑month vesting period and will be used for: - Ecosystem development - Strategic partnerships - Community incentives - Team operational expenses In future governance phases, NTM‑IA holders will be able to vote on: - Specific reserve allocations - Prioritization of funded projects - Adjustments to the reserve percentage > **Note:** The amounts and percentages presented are indicative and may be adjusted according to project needs and market conditions. The team is committed to using funds responsibly and transparently. --- ## 19. References and Public Documentation ### 19.1. Technical documents | Document | Description | URL | |:----------------------|:--------------------------------------------------------|:-----------------------------------------------------------------| | NTM-IA-VERIFICATION.md | Blockchain verification protocol (EN, PT, ZH) | https://netmeios.com/NTM-IA-VERIFICATION.md | | NTM-IA-TOKENOMICS.md | Detailed tokenomics (EN, PT, ZH) | https://netmeios.com/NTM-IA-TOKENOMICS.md | | NTM-IA-TRUST-SCORE.md | Trust Score methodology (EN, PT, ZH) | https://netmeios.com/NTM-IA-TRUST-SCORE.md | | NTM-IA-API.md | API reference (EN, PT, ZH) | https://netmeios.com/NTM-IA-API.md | | README-NTM-IA.md | Project overview (EN, PT, ZH) | https://netmeios.com/README-NTM-IA.md | | NTM-WHITE-PAPER.md | Original NTM white paper (technical basis) | https://netmeios.com/NTM-WHITE-PAPER.md | ### 19.2. Public endpoints | Endpoint | Description | Format | |:---------------------------------------------------|:--------------------------------------------|:-----------| | https://netmeios.com/ntm-ia-trust.php | Trust Score, price, supply, market cap | JSON / HTML | | https://netmeios.com/api-blocks-ntm-ia.php | Block queries (history, hashes) | JSON | | https://netmeios.com/ai-check-integrity-ntm-ia.php | Chain integrity checker | JSON / HTML | | https://netmeios.com/ai-ntm-ia-stats.php | Public dashboard (3 languages) | HTML | | https://netmeios.com/ai-staking-stats.php | Staking dashboard (3 languages) | HTML | ### 19.3. Relevant files and directories | Path | Content | |:-------------------------------|:------------------------------------------------| | `/blockchain/ntm-ia/blocks/` | NTM‑IA blockchain JSON blocks | | `/blockchain/ntm-ia/last_hash.txt` | Last block hash | | `/staking/staking_data.json` | Current staking state (balances, APY, rewards) | | `/staking/staking_history.json`| Aggregated history (up to 180 days) | | `/staking/snapshots/` | Daily snapshots per staker | | `/ai_ia_uas.json` | Active AI User Agents (UAs) | | `/ai_ia_totals.json` | AI hit totals by bot | | `/llms.json` | Hub entities (dataset) | | `/ai-dash-snippet.php` | Real‑time data (block source) | ### 19.4. External references | Reference | Description | URL | |:------------------------------|:--------------------------------------------------------------|:--------------------------------------------------------------------| | EU AI Act | European AI Regulation | https://eur-lex.europa.eu/legal-content/PT/TXT/?uri=CELEX%3A52021PC0206 | | Cloudflare Radar | Data on AI bots (reference for % IA) | https://radar.cloudflare.com/ | | IDO Launchpad (Binance Academy) | Reference on launchpad market practices for token sales | https://academy.binance.com/en/glossary/initial-dex-offering-ido | > **Note:** External references are provided for information purposes only. NTM‑IA is not endorsed by these entities, nor do these entities endorse NTM‑IA. Mention of IDO launchpads is solely as a reference to market practices, without any commitment regarding the choice of a specific platform. --- ## 20. Final Legal Reference ### 20.1. Reminder of the limits of this document This document has been prepared **for informational purposes only**. It does not constitute an offer to sell, a solicitation to buy, a recommendation, or any form of financial, legal, tax or investment advice, nor an offer of regulated financial products. The information contained herein reflects the project’s understanding as of its publication date (April 2026). The development of NTM‑IA and the regulatory and market context may evolve, and some information may become outdated. ### 20.2. Reference to the initial Legal Notice as primary source For all legal and contractual purposes, the Legal Notice (Disclaimer) in Section 1 of this document prevails over any other provision. Readers must read and fully understand Section 1 before making any decision related to NTM‑IA. In case of doubt or interpretative conflict, the provisions of Section 1 are binding and prevail over any summary, abstract or unauthorised interpretation. ### 20.3. Note on future versions and update mechanism This document may be updated periodically to reflect: - Technical developments of the project (new features, audits) - Relevant regulatory changes - Adjustments to model parameters (e.g. Trust Score caps, weights) - Corrections of errors or omissions Updated versions will be published at the same URL, with the revision date clearly indicated. The team commits to maintaining a version history (changelog) for transparency. > **Final warning:** Nothing in this document constitutes a promise of return, appreciation or financial gain. NTM‑IA is structured as a utility token, and not as a security, but final legal qualification always depends on the competent authorities. Investing in cryptoassets involves significant risks, including the total loss of invested capital. **Each investor must perform their own analysis (DYOR) and consult qualified professionals before making any decision.**