> For the complete documentation index, see [llms.txt](https://parallel-game.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://parallel-game.gitbook.io/docs/faq/faq-frequently-asked-questions.md).

# FAQ — Frequently Asked Questions

<details>

<summary>What is Parallel?</summary>

Parallel is a Web3-native card battle game and ecosystem built around NFTs. It transforms collectible cards into playable, evolving game assets, combining fast off-chain gameplay with on-chain ownership and verification.

</details>

<details>

<summary>Is Parallel a game or an ecosystem?</summary>

Both. Parallel starts as a **game-first product**, but is designed to expand into a broader ecosystem that supports new mechanics, integrations, and community-driven experiments over time.

</details>

<details>

<summary>Why are battles off-chain?</summary>

Battles are executed off-chain to ensure:

* Fast gameplay
* Low latency
* Better player experience

Critical outcomes (such as ownership, progression milestones, and achievements) are verified on-chain to preserve trust and transparency.

</details>

<details>

<summary>Which blockchain does Parallel use?</summary>

Parallel anchors NFT ownership and core verification on **Base**, chosen for its low fees, scalability, and strong ecosystem support.

</details>

<details>

<summary>Is Parallel fully on-chain?</summary>

No. Parallel uses a **hybrid architecture**:

* Off-chain systems for gameplay and iteration speed
* On-chain systems for ownership, validation, and ecosystem-level events

This approach balances performance with decentralization.

</details>

<details>

<summary>What is the current stage of the project?</summary>

Parallel is currently in **active development**, progressing toward an MVP and early access release. Core systems are being built and iterated based on internal testing and early feedback.

</details>

<details>

<summary>Will Parallel have a token?</summary>

Yes, a Parallel token is planned.

However, the token launch is **not the initial focus**. The ecosystem and gameplay must demonstrate real usage and traction before token mechanics are introduced.

</details>

<details>

<summary>What will the token be used for?</summary>

Token utility will be aligned with actual ecosystem needs, such as:

* Governance signaling
* Ecosystem incentives
* Contributor rewards

Exact mechanics will be defined closer to launch.

</details>

<details>

<summary>How can I participate early?</summary>

Early participation will be available through controlled access programs, testing phases, and community initiatives. Details will be shared as systems become ready.

</details>

<details>

<summary>Is Parallel open-source?</summary>

Some components may be open-sourced in the future. Initial development prioritizes stability and security before broader code exposure.

</details>

<details>

<summary>Who is Parallel for?</summary>

Parallel is built for:

* Players who value real ownership
* Collectors who want utility for their NFTs
* Builders interested in game-centric Web3 ecosystems

</details>

<details>

<summary>How can I stay updated?</summary>

Follow official Parallel channels and documentation updates. Major changes and releases will always be communicated transparently.

If you have additional questions, feedback, or want to contribute, the Parallel team welcomes thoughtful discussion and collaboration.

</details>


---

# 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://parallel-game.gitbook.io/docs/faq/faq-frequently-asked-questions.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.