> For the complete documentation index, see [llms.txt](https://lyzis.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lyzis.gitbook.io/documentation/basics/images-and-media.md).

# Roadmap

**Charting the Journey of Lyzis Marketplace**

The roadmap outlines the strategic milestones for Lyzis, from inception to future expansions, ensuring a seamless and innovative experience for users.

***

**Phase 1: Foundations (2024 Q1 – Q4)**

* [x] ~~**Concept Development:**~~
  * ~~Identified market needs in luxury asset trading.~~
  * ~~Published research papers supporting our proposed solutions.~~
  * ~~Designed a blockchain-based marketplace for RWA trading.~~
* [x] ~~**Company Incorporation:**~~
  * ~~Officially registered Lyzis L.L.C-FZ (Dubai, UAE).~~
* [x] ~~**Early Partnerships:**~~
  * ~~Established collaborations with 3 partner companies.~~
  * ~~Secured 50+ retailers for initial user testing.~~

***

**Phase 2: Platform Launch (2025 Q1 – Q2)**

* [ ] **Pre-Seed Funding**
  * ~~Prepared investor materials & Product demo.~~
  * Targeted $1M pre-seed round.
* [ ] **Beta & LZS Releases:**
  * LZS release with DEXs listings
  * Invited initial user base for testing and feedback.
  * Onboarded early sellers from the watch dealer network.
* [ ] **Core Features:**
  * AI-powered authentication.
  * Escrow service with smart contract security.
* [ ] **User Experience:**
  * Simplified onboarding, masking blockchain complexity for users.
  * Added photo-uploading guidelines and packing recommendations.

***

**Phase 3: Expansion & Growth (2025 Q3 – 2026 Q1)**

* [ ] **C2C Feature Rollout:**
  * Introduced consumer-to-consumer trading with mandatory  authentication.
  * Integrated tracking system for asset prices.
  * RWA price prediction-based trading system available to retail investors.
* [ ] **Premium Subscription Model:**
  * Offered exclusive perks for premium sellers and buyers.
* [ ] **Marketing Campaigns:**
  * Targeted social media outreach and influencer collaborations.
  * Expanded partnerships in the luxury watch industry.
* [ ] **Token Utility Activation & CEX listings:**
  * Launched LZS token staking and governance features.
  * Introduced referral programs and trading competitions.
  * Full integration across all marketplace functionalities.
  * Implemented periodic token burns to sustain deflationary mechanisms.

***

**Phase 4: Scaling Up (2026 Q2 – Q4)**

* [ ] **Marketplace Diversification:**
  * Expanded to include other luxury assets beyond watches.
* [ ] **Funding Round:**
  * Series A funding to support scaling operations.
* [ ] **Dispute Resolution:**
  * Integrated Kleros for decentralized dispute handling.

***

**Phase 5: Long-Term Vision (2027 and Beyond)**

* [ ] **Global Expansion:**
  * Entered international markets with localized support.
* [ ] **Community Governance:**
  * Enhanced voting systems for community-driven decision-making.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://lyzis.gitbook.io/documentation/basics/images-and-media.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.