> For the complete documentation index, see [llms.txt](https://whitepaper.pethereum.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.pethereum.io/technology.md).

# Technology

### Polygon

All in-game and NFT transactions are made through Polygon. Thanks to Polygon technology, users will pay much lower gas fees for NFT transactions. In addition, thanks to Polygon all NFTs in the Pethereum metaverse can also be displayed on OpenSea.

Polygon is a protocol and a framework for building and connecting Ethereum-compatible blockchain networks. Aggregating scalable solutions on Ethereum supporting a multi-chain Ethereum ecosystem.

With polygon, any project can easily spin up a dedicated blockchain network that combines the best features of stand-alone blockchains (sovereignty, scalability, and flexibility) and Ethereum (security, interoperability, and developer experience). Additionally, these blockchains are compatible with all the existing Ethereum tools (Metamask, MyCrypto, Remix, etc.), and can exchange messages among themselves and with Ethereum.

For more information, you can visit the relevant page on the polygon website.

### **Binance Smart Chain**

Pethereum($PETH), the governance token of the Pethereum metaverse, is an BSC-based token. BSC is a dual-chain architecture that will empower its users to build their decentralized apps and digital assets on one blockchain and take advantage of the fast trading to exchange on the other.


---

# 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://whitepaper.pethereum.io/technology.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.