# Table of Contents

Executive Summary                                                                       

     Key Metrics and Targets

1. Strategic Context: Quantum Threats and the Liquidity Crisis in DePIN

     1.1 The “Harvest Now, Decrypt Later” (HNDL) Threat

     1.2 The DePIN Adoption Cliff: The CapEx Trap

          Case Studies of CapEx-Centric DePIN Failures

     1.3 The GAIB Model: Structural Precedents and Key Differences

     1.4 Why Liquidity-First Is the Optimal Path

2. Market Opportunity and Demand Validation

     2.1 Total Addressable Market

     2.2 Target Customer Segments

          Segment 1: Zero-Knowledge (ZK) Protocols

          Segment 2: Cross-Chain Bridges

         Segment 3: Institutional Custody

          Segment 4: Oracle Networks

          Segment 5: Enterprise Compliance

     2.3 Evidence of Demand Validation

     2.4 Competitive Landscape

3. Platform Architecture: Liquidity-First Model

     3.1 Separation Model: Physical Layer and Economic Layer

          Physical Layer — Operator Domain

          Economic Layer — Investor Domain

          Inter-Layer Interaction Protocol

          System Resilience Through Separation

     3.2 Receivables as an Asset: Vault Mechanism

          Composition of Receivables

     3.3 Operator Lending Model

          Operator Eligibility

          Loan Structure

          Default Protection Waterfall

4\. Technical Advantage: Hardware-Based Trust

     4.1 qSIM Node Specifications

          QRNG Module

          PQC Signature Module

          HSM / Secure Enclave

     4.2 Proof of Service (PoSv) Protocol

          Protocol Sequence

     4.3 Remote Attestation and Sybil Resistance Protocol

          Node Registration

          Sybil Resistance

          Continuous Integrity Monitoring

     4.4 Oracle-Free Trust Model

5\. Tokenomics: Dual-Asset Engine

     5.1 $QBT — Gas and Work Token

          Function 1: Network Gas

          Function 2: Operator Staking Collateral

          Function 3: Governance

          Burn Mechanism

     5.2 $qYield — Synthetic Yield Token

          What $qYield Represents

          Minting and Redemption

          Value Accrual: Buyback-and-Burn Model

     5.3 Value Accrual Loop: Dual-Token Flywheel

          Forward Flywheel

          Reverse Spiral: Honest Risk Assessment

          Minimum Viable Network (MVN) Threshold

     5.4 Supply Schedule and Token Allocation

6\. Team, Governance, and Roadmap

     6.1 Core Team

     6.2 Governance Architecture

          Phase 1: Foundation-Led (0–12 months)

          Phase 2: Hybrid (12–24 months)

          Phase 3: Full DAO (24+ months)

     6.3 Development Roadmap

7\. Regulatory and Risk Strategy

     7.1 Compliance-by-Design Architecture

          Howey Test Analysis

          SPV Issuance Structure

          Jurisdictional Roadmap

          On-Chain Access Control

     7.2 Operational Risk Controls

          Operator Default Protocol

          Insurance Fund

          Concentration Controls

          Smart Contract Security

          SLA Enforcement

     7.3 RWA Expansion Roadmap

8\. Risk Register

     R1: Regulatory Crackdown

     R2: Liquidity Crisis / Death Spiral

     R3: Operator Centralization

     R4: Hardware Supply Chain Attacks

     R5: Rapid Competitive Catch-Up

9\. Financial Projections and Scenario Analysis

     9.1 Revenue Model

     9.2 Three-Scenario Outlook (24 Months)

          Key Assumptions

     9.3 Sensitivity Analysis

10\. Open Questions and Data Requirements

11\. Legal Disclaimer


---

# 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://railquant.gitbook.io/quantarail/table-of-contents/table-of-contents.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.