# 10.1 Token Design Philosophy: Single Token with Multi-Role Functionality

GET is based on the design policy of “one token, diverse roles, and concise UX,” creating an alternative structure to the traditional "Dual Token Model". What is the Dual Token Model? Many Web3 projects issue two types of tokens with separate utility and governance roles (e.g., UTIL + GOV), but the following challenges exist * User experience is complicated and easily confused by beginners * Value is distributed among tokens, and price and usage are unstable * Smart contract design and regulatory compliance tend to be complicated **GET’s Model:** One on-chain token (GET) with two off-chain auxiliary point (GET Pay and GET Miles) mechanism ensures convenience and expandability.


Asset	Type	Main Role
GET	On-chain Token	The cornerstone of the economy, including voting, payment, NFT purchases, support, staking, etc.
GET Pay	Off-chain Currency	Off-chain currency “In-app points” that enable instant, lightweight payments for live shows, movies, merchandise sales, etc.
GET Miles	Off-chain Reward	Off-chain rewards Reward points awarded for actions such as voting, posting, and contributions

Model Comparison and Advantages


Comparison axis	Dual Token Model	GET model (1 token + 2 points)
Easy-to-understand UX	Difficult to distinguish between different tokens	GET is the axis, and auxiliary functions can be used like an app
Liquidity and price formation	Value is dispersed, and price formation tends to be complicated	Focus on GET, and evaluation axis is clear
Flexibility in implementation and development	Design required for each token	Flexible and agile response with off-chain auxiliary design
Legal arrangement	Regulations and approvals must be arranged for each token	One type of token. Auxiliary points can be classified as in-app currency

Thus, the GET model is oriented toward a new standard for Web3 as a clear, robust, and scalable tokenomics. --- # 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://docs.global-entertainment-token.org/10.-token-allocation-and-economic-design-tokenomics/10.1-token-design-philosophy-single-token-with-multi-role-functionality.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.