> For the complete documentation index, see [llms.txt](https://rwaperp-1.gitbook.io/rwaperp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rwaperp-1.gitbook.io/rwaperp-docs/rwaperp-points/rules-for-point-generation.md). # Rules for Point Generation RWAPerp Points are used to track users' genuine transactions, fund retention, invitations, and ecosystem contributions on the platform. ### 1. Weekly Base Point Generation RWAPerp uses a fixed weekly point pool mechanism for general users: 1,000,000 Points / Week The weekly base Points fixed output is 1,000,000 Points. All eligible users will jointly participate in the allocation of the weekly point pool based on their effective contributions during that week. The 1,000,000 Points per week do not include exclusive points and incentives for Market Makers, as Market Makers use a separate point and incentive mechanism. ### 2. How to Earn Points Users can earn Points by making genuine and effective contributions on RWAPerp, including but not limited to: #### Trading * Effective Trading Volume * Fee Contribution * Effective Trading Days * Quality of Holdings and OI #### Deposit * Effective Net Deposit * Account Fund Balance * Fund Retention Time With the launch of products like Vault and LP, related fund contributions may gradually be included in the Points system. Initially, only trading and deposit are supported. Subsequent updates to the Points system may support other dimensions, such as: #### Referral Inviting real users to join RWAPerp and completing an effective Deposit, Trading, or continuous use of the platform may earn corresponding Referral Points. #### Market & Community Contribution Participation in certain key RWA Markets, newly launched markets, and community contributions that generate real value for the RWAPerp ecosystem may also earn corresponding Points. ### 3. Limited Points Boost During the initial Launch phase and certain designated promotional periods, RWAPerp will offer a limited-time, limited-quantity Points Boost. Users who qualify for the promotion can receive extra point rewards in addition to the normal Base Points. Specific details of the Boost: * Promotional Period * Eligibility * Reward Amount * Boost Rules * Eligible Markets will be subject to the corresponding promotional page and official announcements. The limited-time Boost does not change RWAPerp's long-term fixed weekly base generation mechanism of 1,000,000 Base Points. ### 4. Points Settlement Points are statistically calculated and settled weekly. After each Epoch ends, the system will calculate the corresponding Points based on the user's effective contribution for the week and issue them after completing data and risk review. The following abnormal behaviors may not be counted towards points, including but not limited to: * Self-Trading * Wash Trading * Cross-trading between associated accounts * Sybil Accounts * Abnormal volume manipulation * Price manipulation * Other behaviors deemed by the platform as non-genuine transactions ### Important Notes * Market Maker Points are not included in the point pool mentioned above. * An additional limited-time, limited-quantity Points Boost may be offered during the Launch phase and specified promotional periods. * Points do not represent any promise of return, Token distribution promise, or guarantee of future asset value. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://rwaperp-1.gitbook.io/rwaperp-docs/rwaperp-points/rules-for-point-generation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.