# Roadmap

### 2024: Foundation

* Staking for rewards live
* Dlicom beta release
* App listed on stores
* 1,500+ token holders
* social channels and community hubs launched
* first community event (Dubai)
* 5,000+ organic app downloads

### 2025: Product Expansion

* Dlicom v1.0 launch
* browser extension
* WebApp beta
* major UI/UX upgrade
* new blockchain integration
* tipping feature release
* 3,000+ token holders
* 10,000+ organic app downloads
* 20,000+ wallets created
* community event (Turkey)

### 2026: Scale, Utility, Monetization

#### Q1 2026

* DliClips launch
* affiliate platform launch
* WebApp launch
* Hacken audit
* Discord Roles System Launch
* brand refresh and visual identity rollout
* multi-platform growth campaigns

#### Q2 2026

* Watch2Earn launch
* premium users feature (v1)
* in-app swap on iOS
* UGC viral challenge season 1
* affiliate and validator programs activation
* SFR utility goes live
* Airdrop Phase 1 launch
* UGC viral challenge season 2
* Base ecosystem partnerships
* credibility partnerships and ecosystem validation initiatives

#### Q3 2026

* ads engine launch
* premium users feature (v2)
* personalized AI feeds
* DLI utility activated in-app
* mini apps v1.0
* retention and activation upgrades
* creator and advertiser early access
* traction highlights
* token generation event (TGE)
* strategic ecosystem co-marketing
* community event

#### Q4 2026

* ads management center launch
* in-platform ads rollout
* content monetization go-to-market
* category leadership positioning
* ads marketplace scale-up
* brand and platform partnerships
* annual ecosystem report
* flagship community and partner event


---

# 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://whitepaper.dlicom.io/roadmap/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.