# Initializing the Gradient

{% hint style="success" %}
**Completed**
{% endhint %}

## Paving the Way to Adoption.

> Adoption moves faster when everyone gets it. Gradient's rollout starts by raising awareness and understanding about both the platform and the problem it solves. This develops a community of early adopters, which accelerates platform growth in early stages. Here's how we do it:

### 1. Spreading Awareness

Gradient’s first phase starts with an information rollout introducing: The cost and consequences of price-impact > Gradient's solutions and potential market share > Platform benefits and features > Participation incentives.

### 2. Collaborating with Token Projects

Although any token can be traded through the Gradient permissionlessly, collaborating with leading projects allows for accelerated adoption and boosted incentives. Gradient’s upcoming partner campaign is designed to incentivize token teams to drive early use to the platform:

***

## Building the Gradient.

> Change takes time, but it can never come too quickly. With a high focus on driving immediate adoption, here is how the Gradient will rollout ahead of its full release.

### 1.  Open-Sourcing & Auditing of the Trading Layer

Building trust and showing transparency is key, especially when introducing a new way to trade. All on-chain components of Gradient will be open-source and independently audited.&#x20;

### 2. Interactive Demonstrations

The Gradient will be showcased through a series of interactive demonstrations designed to build a better understanding of how the platform works. These will be targeted towards Gradient’s community of early adopters.


---

# 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.gradient.trade/roadmap/initializing-the-gradient.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.
