[Overview] The DEP Protocol consists of a three-layer structure where "verification module groups" for specific purposes are placed on top of a general-purpose blockchain foundation. Service Providers combine these to build solutions.
4.1 Layer 1: Core Blockchain & Consensus Layer (Foundation Layer)
[Foundation] This is the bottom-most foundation supporting the reliability and settlement of the entire system. Upper-layer modules operate on this layer, where final data finality and value transfer take place.
- Consensus Engine: Consensus formation by decentralized nodes ensures the validity of verification results.
- On-chain Ledger: Records token settlement history, data hashes, and module execution logs in an immutable state.
- DEP Native Standard: Defines basic currency functions to maintain the ecosystem, such as payment of gas fees and staking by nodes.
4.2 Layer 2: Use-Case Specialized Module Layer (Domain-Specific Modules)
[Core Layer] This layer is the core of the protocol. "Dedicated verification engines" developed for specific data demands (AI training, advertising, maps, etc.) are provided like plugins.
[Usage Model] Service providers select necessary modules for their business and call functions by paying usage fees to the protocol in DEP tokens. For example, the following modules are envisioned. These modules are designed to be expandable to various cases via DIP (DEP Improvement Proposal).
- RLHF Verification Module (Reinforcement Learning from Human Feedback): A function to verify and score "human feedback data" necessary for tuning LLMs (Large Language Models). It evaluates the naturalness and accuracy of responses and removes noise inappropriate for AI learning.
- Ad Fraud Detection Module: A function to analyze ad delivery logs and user behavior data to detect and eliminate fraudulent clicks and impression fraud by bots.
- Geo-Spatial Verification Module: Checks the consistency of GPS data and mapping images to generate the latest real-world data while preventing location spoofing.
4.3 Layer 3: Integration & Gateway Layer (Integration Layer)
[Interface] This is the interface layer for end-users and service providers to connect to the protocol.
Embedded SDK (Data Mining Client)
- Protocol Provision and Implementation: The protocol provides "official SDKs" corresponding to each Layer 2 module. Service providers (and partner app developers) select the SDK for the module they wish to use, embed it in their applications, and distribute it.
- Standardization and Security: The protocol manages the SDK's core logic to enhance data tamper resistance and guarantee data collection that fully complies with the verification standards of each module.
API Gateway (Service Interface)
- Service Provider Side: A connection point for operators to call module functions or retrieve verified data. Operators perform DEP token signing here to exercise access rights to modules. Even operators without their own data collection means (like data aggregators) can search for and purchase (acquire) data generated from the global SDK network through this gateway.
4.4 Economic Connection: B2B2B Circular Model (Economic Flow)
[Economic Model] This is an economic model that converts real-economy capital flow (Fiat) into DEP token demand (Token) via service providers.
- End Client (Final Consumer/Enterprise) → Service Provider
- 【Payment: Fiat Currency (JPY/USD)】 Final customers such as AI development companies and advertisers pay service fees (data purchase costs, etc.) to service providers in "fiat currency" or via "invoice payment" according to existing business practices. They do not need to be aware of blockchain or tokens.
- Service Provider → DEP Protocol
- 【Payment: DEP Token (Required)】 Upon receiving Fiat from customers, service providers procure DEP tokens from the market to use protocol modules and use them for payment to the protocol.
【Types of Service Providers】 Two main types of service providers participate in this ecosystem:
- Publisher Type (Pattern A): Operators who introduce the SDK into their own apps and monetize collected data.
- Aggregator Type (Pattern B): Operators who do not have their own data collection apps but buy data from third-party apps through the protocol. They function as "pure data buyers," adding value through advanced analysis and packaging before selling to end clients.