# Introduction

Viridian Exchange aims to be the main liquidity provider in the Core ecosystem, helping the chain grow and connecting EVM and Bitcoin for users and liquidity. Our goal is to offer a smooth and user-friendly experience by using the best features from other DEXes.

**One Pager of the Viridian Exchange:**

<figure><img src="https://1191514248-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTN8YmTue1VkQbxdIu8Qv%2Fuploads%2FMZhb30h9VVMed6kzfdYC%2Fone%20page.png?alt=media&#x26;token=de7380db-dc31-4345-a9c4-1b96f5078fac" alt=""><figcaption></figcaption></figure>

### Why Core?

* Core EVM lacks a strong AMM, and Viridian aims to fill that role.
* Each month, 1 million CORE will be distributed among protocols based on TVL, volume, transaction count, and other metrics. This makes Core an ideal chain for maintaining reward flow for our platform.
* Core DAO and Viridian share a vision for expanding blockchain's utility beyond traditional finance, focusing on scaling solutions and new networks while addressing blockchain challenges.
* Core EVM is a decentralized app secured by Bitcoin, using EVM-compatible smart contracts on a blockchain powered by Bitcoin. It combines delegated Proof-of-Work and delegated Proof-of-Stake.
* The years 2024 and 2025 are set for significant growth in the Core ecosystem, boosting expansion even further.

Additional details about the Core Ecosystem can be found on the linked pages below.

{% embed url="<https://coredao.org/>" %}

{% embed url="<https://docs.coredao.org/core-white-paper-v1.0.6/>" %}

{% embed url="<https://docs.coredao.org/developer/introduction/getting-started>" %}


---

# 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://viridian-hub.gitbook.io/viridian/welcome/introduction.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.