> For the complete documentation index, see [llms.txt](https://guide.pepeunchained.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.pepeunchained.com/developer-resources/development-best-practice.md).

# Development Best Practice

Welcome to the Pepe Unchained ($PEPU) ecosystem. To ensure a smooth building experience and successful integration, please follow these technical guidelines and use the official resources provided below.

### Network Configuration

When configuring your development environment (Hardhat, Foundry, or MetaMask), use the following RPC and Explorer details for the V2 Testnet:

* Network Name: Pepe Unchained V2 Testnet
* RPC URL: `https://rpc-pepu-v2-testnet-vn4qxxp9og.t.conduit.xyz`
* Chain ID: `97740`
* Currency Symbol: PEPU
* Block Explorer: [PepeScan Explorer](https://explorer-pepu-v2-testnet-vn4qxxp9og.t.conduit.xyz)

### Token Data & APIs

For developers building dashboards, tracking supply, or integrating $PEPU into UI elements, use the official Supply API:

* Supply API Endpoint: `https://tokens.pepuscan.com/supply`
* Usage: This endpoint provides real-time circulating and total supply data essential for CoinGecko/CoinMarketCap integrations and internal analytics.

### Assets & Marketing

Don't reinvent the wheel. Use the official Pepe Unchained brand kit to ensure your project looks "Unchained."

* Marketing Assets: To get access to the shared folder containing high-quality assets and FwB (Friends with Benefits) materials, please join our developer community.
* Get Listed: Want your project featured on the [Pepe Unchained Ecosystem Page](https://pepeunchained.com/en/ecosystem)?

#### 🤝 Join the Dev Group

The best way to stay updated on network upgrades and collaborate with the core team is through our Telegram.

* Inquire Here: [Pepe Unchained Dev Telegram](https://t.me/pepeunchn/1)


---

# 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://guide.pepeunchained.com/developer-resources/development-best-practice.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.