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

# Token Contract Details

* Token Name: ***Orbler Token***
* Symbol: ***ORBR***
* Max Total Supply: ***2,000,000,000 ORBR***

Token Contract Address: 0xdA30f261a962d5AAe94C9ecd170544600d193766&#x20;

*This is the unique address on the Ethereum blockchain where the Orbler Token smart contract resides. Users can interact with this contract to perform actions such as transferring, staking, and checking their ORBR balance.*

Decimals: 18

*This means that the Orbler Token can be divided down to 18 decimal places, allowing for micro-transactions and greater divisibility.*

Standard ERC-20

*As an ERC-20 token, ORBR complies with the Ethereum token standard, making it compatible with a wide array of wallets and platforms that support the ERC-20 protocol.*

Explorer: <https://etherscan.io/token/0xdA30f261a962d5AAe94C9ecd170544600d193766>

*Etherscan is a block explorer and analytics platform for Ethereum. By following the provided link, users can view detailed information about the Orbler Token, including its total supply, holders, and transfers. It also offers transparency and verification of the token's activities on the Ethereum blockchain.*


---

# 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:

```
GET https://docs.orbler.io/tokenomics/token-contract-details.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.
