# 4. Development Roadmap

## Phase 1: User-Led Labeling Incentive Mechanism (0-6 Months)

* Smart Contract Deployment for User Tagging.
* Incentive & Reward Platform

## Phase 2: Individual Users Payment Model (7-12 Months)

* Automated Behavior Recognition Engine
* API Gateway & Billing System

## Phase 3: User Growth Engine (13-24 months)

* Launch of TRID minting tool.
* FinTax AI completes training for the first 100,000 transaction classification models.
* Integration of tax proof minting feature with 3 major wallets.
* Release of Mercury points system.

## Phase 4: Protocol Compliance Layer (25-36 months)

* Launch of VC verification module and SDK toolkit, supporting DApp integration.
* Establishment of DApp compliance certification system, providing certification labels for verified DApps.
* Launch of user-verifiable credential incentive dashboard, enabling real-time viewing of verification income distribution.
* Launch of enterprise custom development services, offering tailored identity verification engines for large clients.

## Phase 5: Government Collaboration Network (37-48 months)

* Completion of government-side compliance technology certification.
* Pilot on-chain tax audit system with 1-2 national tax authorities.
* Launch of government regulatory dashboard.

## Phase 6: Full-Chain Identity and Credit Ecosystem (After 48 months)

* Cross-chain identity verification: Support TRID identity verification for 10 major blockchains, creating cross-chain identity universality.
* Credit scoring system: Launch of on-chain credit scoring system, generating credit profiles based on on-chain behavior and asset data.
* Scenario expansion: Explore the application of TRID in decentralized social networking, on-chain governance, and other fields to expand ecosystem influence.


---

# 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.mercurynet.org/4.-development-roadmap.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.