# Playnance Gas Token (PBG)

***

### Overview

The Playnance Gas Token (PBG) is the designated utility token of the PlayBlock network, designed to support transaction fee payments and operational activities across the ecosystem.

PBG is configured with 18 decimals, aligning with the ERC-20 standard to ensure compatibility, consistency, and precise accounting.

This document outlines the functional scope, governance controls, and operational mechanisms of the PBG token, highlighting its role in maintaining network efficiency, security, and user asset protection.

***

### Token Details

* **Token Name:** Playnance Gas
* **Token Symbol:** PBG
* **Decimals:** 18
* **Blockchain:** PlayBlock
* **Chain ID:** 1829

***

### Core Functionalities:

***

#### Minting

* **Capability**

The minting of PBG tokens is exclusively controlled by the PlayBlock governance authority. This mechanism enables controlled supply adjustments in response to network growth and operational requirements.<br>

* **Purpose**

To support scalability and adaptability of network operations through regulated supply expansion.

* **Reference**

OpenZeppelin ERC-20 Minting Documentation [here](https://docs.openzeppelin.com/contracts/3.x/api/token/erc20#ERC20-_mint-address-uint256-).&#x20;

***

#### **Burning**

* **Capability**

The burning function is reserved solely for the PlayBlock governance authority. It allows the removal of PBG tokens from circulation, including tokens held by external addresses.

* **Purpose**

To mitigate network abuse, deter spamming or malicious behavior, and reduce circulating supply when required to protect network integrity.

* **Reference**

OpenZeppelin ERC-20 Burnable Documentation [here](https://docs.openzeppelin.com/contracts/3.x/api/token/erc20#ERC20Burnable).&#x20;

***

#### **Pausing and Unpausing**

* **Capability**

The governance authority may pause and resume PBG token transfers as an emergency response mechanism. During a pause, all token movements are temporarily halted.

* **Purpose**

To protect the network and user assets in the event of detected vulnerabilities, attacks, or critical operational risks.<br>

* **Reference**

OpenZeppelin ERC-20 Pausable Documentation [here](https://docs.openzeppelin.com/contracts/3.x/api/token/erc20#ERC20Pausable).&#x20;

***

#### **Token Recovery**

* **Capability**

A recovery mechanism allows the retrieval of non-PBG assets that are mistakenly sent to the PBG token contract. This functionality is accessible exclusively to the PlayBlock governance authority.<br>

* **Purpose**

To prevent permanent loss of user assets resulting from accidental transfers to the token contract address.

***

### Governance and Operational Integrity

The PBG token incorporates governance-level controls that centralize critical operational functions — including minting, burning, pausing, and recovery — under PlayBlock administration.

This governance model is designed to:

* Strengthen network security
* Enable rapid response to threats
* Maintain operational stability
* Protect ecosystem participants<br>

All governance actions related to PBG are expected to follow principles of transparency, fairness, and accountability, ensuring long-term trust and integrity across the Playnance ecosystem.

***

#### Resources

* Download PDF: <https://www.playnance.com/docs/playnance_gas_token_pbg.pdf>


---

# 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.playnance.com/pbg-gas-token/playnance-gas-token-pbg.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.
