> For the complete documentation index, see [llms.txt](https://docs.neopin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neopin.io/roadmap/2023.md).

# #2023

<figure><img src="/files/KFvQ0qBFXsNfW2S0t3wk" alt=""><figcaption></figcaption></figure>

## 2023 Q1

**Protocol expansion phase 4 for NEOPIN vision**

* Add Support Ethereum, Polygon Bridge and Wrapped Token Features
* Launch Yield Farming Pools, Swap Features for Ethereum, Polygon Coins & Tokens
* Launch Stable Coin related Products
* Add Support Ethereum, Polygon networks on NEOPIN Connect

## 2023 Q2

**Protocol expansion phase 5 for NEOPIN vision**

* Launch NEOPIN Premium Membership Program
* Add Support Liquidity Staked Assets

## 2023 Q3

**Protocol expansion phase 6 for NEOPIN vision**

* Launch Governance Voting Platform with L1 network support
* Add Support Cosmos-compatible Network

## 2023 Q4

**Protocol expansion phase 7 for NEOPIN vision**

* Add support for Finschia Blockchain Network&#x20;
* Add Support 1 EVM-compatible L2 Network and Launch Staking Products
* Launch Bridge Feature on NEOPIN Web
* Release Major NEOPIN Protocol Updates


---

# 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://docs.neopin.io/roadmap/2023.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.