> For the complete documentation index, see [llms.txt](https://peardao.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://peardao.gitbook.io/docs/pear-events/beta-user-airdrop.md). # Beta User Airdrop **Total Airdrop Amount: 30,000,000 PEX** Early Beta Tester Airdrop Details: Beta Period and target user: During the PearDAO Beta period (1.15-00:00 - 1.31-24:00), all addresses that have successfully traded on peardao.io Airdrop Amount Calculation: Total Airdrop Amount \* Proportion of the trading volume \* Trading Score / (∑ Trading Score of participating addresses) What is a Trading Score: Higher Trading Score will be attributed to users who have traded a larger amount of trading volume and number of trades in the Beta phase. The specific parameters are set as follows: * 1-10 completed trades = Trading Score 1; * 11-20 completed trades = Trading Score of 1.5; * 21-30 completed trades = Trading Score of 2; * 30 completed trades = Trading Score of 6, and 6 is the maximum score. Why do some addresses have transactions but Trading Score is lower than 1: After our initial Beta phase, the team has identified some addresses to be making fraudulent transactions through automated contract interactions, and their activities include but are not limited to: 1. Multiple addresses managing gas fees through the same funding channel; 2. Circulate funds through scripting to boost transaction records; 3. Complete multiple transactions in a very short period of time, resulting in a large number of invalid transaction records. The team believes that these behaviours are deemed fraudulent and will impede the healthy development of the platform. After much consideration, the team has decided to reduce the Trading Score of all participants who have displayed the stated behaviours to 0.1. --- # 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://peardao.gitbook.io/docs/pear-events/beta-user-airdrop.md?ask=&goal= ``` `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.