> For the complete documentation index, see [llms.txt](https://dannychain.gitbook.io/danny/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dannychain.gitbook.io/danny/token-and-contract/dan-token.md).

# DAN Token

## 🌐Network Information

| INFO            | RESULTS                                         |
| --------------- | ----------------------------------------------- |
| Network Name    | Danny                                           |
| Chain ID        | 5069 (Hex: 0x13cd)                              |
| Currency Symbol | DAN                                             |
| HEX             | 0x13cd                                          |
| RPC URL         | [rpc.dannyscan.com](https://rpc.dannyscan.com)  |
| Block Explorer  | [https://dannyscan.com](https://dannyscan.com/) |
| DeFi App        | [https://dandex.io](https://dandex.io/)         |

## 💰 Token Specifications

Every transaction on the DannyChain network requires a small amount of DAN to process.
\
DAN is used similarly to: ETH on Ethereum, BNB on BNB Chain, MATIC/POL on Polygon

<table><thead><tr><th>Specification</th><th width="374">Details</th></tr></thead><tbody><tr><td>Native token</td><td>Danny</td></tr><tr><td>Token Symbol</td><td>DAN</td></tr><tr><td>Ecosystem</td><td>Danny Chain</td></tr><tr><td>Blockchain Support</td><td>Danny Chain + BNB Smart Chain</td></tr><tr><td>Decimals</td><td>18</td></tr><tr><td>Total Supply</td><td>300,000,000 DAN</td></tr><tr><td>Max Supply</td><td>300,000,000 DAN</td></tr><tr><td>Consensus Mechanism</td><td>Proof of Authority (PoA)</td></tr><tr><td>Block Time</td><td>&#x3C;2 second</td></tr><tr><td><strong>Finality</strong></td><td>&#x3C;1-2 second</td></tr></tbody></table>

## ⚡ Performance Analysis

#### 🚀 Speed

DannyChain uses a Proof of Authority (PoA) consensus mechanism, enabling faster block confirmations and lower resource consumption compared to traditional Proof of Work systems.

With an average block time of approximately 2 seconds:

TPS ≈ Transactions / Seconds<br>

{% hint style="info" icon="paper-plane" %}

#### ☎️Need Help? <a href="#need-help" id="need-help"></a>

Reach out to us for support, suggest improvements, or file a ticket using the [**Support**](mailto:admin@dannychain.com) on Telegram. Our team is here to assist you!

* [**Telegram**](https://t.me/dannytoken): Join our developer community
* [**Twitter**](https://x.com/Dan74668): information Danny Chain
  {% endhint %}

### 🔹 Example Formula

Gas cost calculation on EVM chains generally follows:

*Transaction Fee= Gas Used × Gas Price*

Where:

* **Gas Used** = computational workload
* **Gas Price** = price paid per gas unit

### 🔐 Security Considerations <a href="#security-considerations" id="security-considerations"></a>

#### Best Practices <a href="#best-practices" id="best-practices"></a>

1. **Hardware Wallets**: Use for large holdings
2. **Multi-Signature**: For treasury management
3. **Regular Audits**: Smart contract reviews
4. **Secure Storage**: Never share private keys

#### Risk Management <a href="#risk-management" id="risk-management"></a>

* **Volatility**: Cryptocurrency price fluctuations
* **Smart Contract Risk**: Audit before interaction
* **Bridge Risk**: Verify bridge contracts
* **Custody Risk**: Self-custody responsibility

{% embed url="<https://dannyscan.com/>" %}


---

# 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://dannychain.gitbook.io/danny/token-and-contract/dan-token.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.