# Token Layer ### **$EPT Token:** 1. **Payment Token for Gaming Companionship** * $EPT is the primary payment method for all gaming companion services on the E-PAL platform * Enables seamless transactions between users and Epals 2. **Fans Protocol Currency** * $EPT may be used for minting and trading Fan Tokens of gaming companions * The token powers the entire Fan Token economy within the ecosystem, and may also be distributed to creators to incentivize quality content creation 3. **Governance Token** * $EPT grants holders voting rights on platform upgrades and protocol changes * Proposal submissions and voting power would require users to stake $EPT as an indicator of commitment 4. **Platform Service Token** * $EPT is the main Payment method for all Balance platform services * Required for accessing advanced platform functionalities 5. **Gas Token for Balance Chain** * The protocol itself does not provide any network resources, so it relies on a network of decentralized nodes which would provide GPU/computing resources (e.g. chain abstraction layer). $EPT would be paid by users and distributed to these nodes in order to incentivize them to actively provide valuable network resources. 6. **Balance ID Operations** * Required for Balance ID creation and updates * Used for Balance ID premium features and services ### **Fan Tokens:** 1. **Customized Tokens for Engagement**: Fan Tokens are tailor-made to enhance community interaction and personalized experiences within the Balance ecosystem. 2. **User-Driven Economies**: Users can issue and manage their own Fan Tokens, creating exclusive economic circles that deepen community engagement and loyalty. --- # 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://balancefun.gitbook.io/balance/products/token-layer.md?ask= ``` 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.