> For the complete documentation index, see [llms.txt](https://docs.chainparty.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chainparty.xyz/chain-party/our-goals.md).

# Our Goals

<figure><img src="/files/7Etzi9ImaE5QuWVQEn3m" alt=""><figcaption></figcaption></figure>

**Chain Party** is designed to achieve the following goals:

**Community-Based Economy**

The **Chain Party** ensures a fair and transparent structure that rewards community contribution through the usage of blockchain technology.

**Player Liquidity**

The gamified platform experience of the **Chain Party** creates a concrete motivation structure for player liquidity to circulate among the games.

A liquid player base enables high player retention on the platform and value accrual to the platform.

**Mass Adoption**

We’ve made it easy for everyone to get started. No need to be a tech expert—just jump in and enjoy a seamless gaming experience!

***

To achieve these goals, the **Chain Party** is composed of 3 elements:

**A Gamified Platform Experience**

The **Chain Party** offers a platform-native gamified experience through the mechanism of Party2Earn and Share2Earn, where users can collect rewards for game-level benefits.

**Platform Composability**

The **Chain Party** provides systematic composability across games on the platform.

**Quality Games Driving Intrinsic Motivation**

The **Chain Party** intends to start with a small number of quality games to create a solid community, then extend the system out through the continuous onboarding of new high-quality titles.

A combination of high-quality titles and a series of mini-games to be launched on the platform create a great balance between game quality and widespread access, stimulating various intrinsic motivations of gamers.

<br>


---

# 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.chainparty.xyz/chain-party/our-goals.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.
