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

# Playnance Introduction

***

### Overview

Playnance is building a live on-chain economy designed to support large-scale entertainment applications.\
The ecosystem enables gaming, trading, betting, and prediction markets to operate with real economic flows, where rewards, transactions, and settlement are executed transparently on-chain.

Playnance focuses on abstracting blockchain complexity while preserving core on-chain principles — ownership, transparency, and verifiable execution.\
Users interact through familiar Web2-style experiences while all value movement, accounting, and state changes are handled by blockchain infrastructure in the background.

***

### Who this documentation is for

This GitBook is intended for stakeholders who require a clear understanding of the Playnance ecosystem — including its infrastructure, economic model, and operational logic.

It provides technical, economic, and structural documentation for teams and organizations interacting with or building on Playnance, including:

**‏• Investors & Strategic Stakeholders** — seeking visibility into the token economy, scalability model, and long-term roadmap.\
\
**‏• Web2 Companies Entering Web3** — looking to onboard users on-chain through Playnance infrastructure and partner portals.\
\
**‏• Product & Technology Teams** — requiring clarity on architecture, system components, and economic flows.\
\
‏**• Partners & Operators** — managing portals and needing insight into revenue logic, on-chain accounting, and operational best practices.\
\
‏**• Developers** — accessing APIs, integration paths, token flows, and sandbox environments.\
\
**‏• Regulatory & Legal Teams** — reviewing compliance frameworks, licensing structure, and risk controls.

This GitBook is structured in layers — starting from high-level ecosystem context and progressing into technical architecture, economic mechanisms, APIs, and settlement logic.\
Readers may follow the documentation sequentially or navigate directly to the sections relevant to their role.

The content is designed to support building, integrating, operating, and evaluating Playnance as a production-grade on-chain ecosystem.

***

#### Quick Access

Playnance Official Website: [Playnance](https://playnance.com)

PlayBlock Explorer: [PlayBlock Explorer](https://explorer.playblock.io/)

Pitch Deck: [Pitch Deck](https://docs.playnance.com/pitch-deck/)

{% file src="/files/CKdtUsfujQK0tb7BPMi9" %}

***

#### Social Channels

Twitter (X): [Playnance X](https://x.com/playnance_?s=21)

Telegram: [Playnance Telegram](https://t.me/playnance_official)

Instagram: [Playnance Instagram](https://www.instagram.com/playnance_?igsh=MWt4YTFiN2MwbG0zaQ%3D%3D\&utm_source=qr)

LinkedIn: [Playnance LinkedIn](https://www.linkedin.com/company/playnance/)

***

#### Ecosystem Access

PlayW3: [PlayW3](https://playw3.com)

PlayQuack: [PlayQuack](https://playquack.com)

Sharker: [Sharker](https://sharker.com)

Partner Portal: [Partner Portal](https://playw3.com/partners)


---

# 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.playnance.com/documentation/playnance-introduction.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.