> For the complete documentation index, see [llms.txt](https://chordarc.gitbook.io/chordarc-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chordarc.gitbook.io/chordarc-docs/getting-started-with-chordarc/project-background.md).
# Project Background
Understanding ChordArc
A wallet is more than an address. It is a record of where you've been, what you've participated in, and how long you've been part of the on-chain economy. That is why ChordArc is designed to recognize the journey that brought you here.\
\
For our launch, ChordArc will recognize on-chain activity across selected networks: Ethereum, Arbitrum, Optimism, Base, BNB Chain, Polygon, Avalanche, Linea, Scroll, Blast and Arc.
These networks form the foundation of most on-chain footprints, and they would be the dependent factors for ChordArc footprint. Your history is proof that you were already on the way.
ChordArc introduces a different approach to ecosystem rewards: recognizing users for the history they have already created on-chain.
Rather than treating every user as a new address arriving on Arc, we look at the history they already carry.
* The early users.
* The active participants.
* The explorers who moved from one ecosystem to another.
Their history is part of the story.
{% hint style="success" %}
**ChordArc Criteria:** All you need is **w**allets that have active history onchain!
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://chordarc.gitbook.io/chordarc-docs/getting-started-with-chordarc/project-background.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
