# Airdrop Logic

Airdrop Criteria (Policy)

1\. n% of the generated revenue of DMCK Foundation will be used for airdrops.

2\. When n% of revenue is generated, it will be used to pay n% of the rewards. / 20% will be used for foundation operating expenses.

3\. n% of the n% allocated for reward will be distributed to De-Fi Depository Service users, and the remaining n% will be airdropped to NFT holders.

&#x20;

Airdrop Criteria of De-Fi Depository Service

1\. Score of De-Fi Deposit Service usage by number and duration (detailed logic of scoring will be disclosed later)

2\. Aggregate total scores by summing the scores of service users

3\. aggregated total score/DMCK Foundation return (n%) = number of points per 1 point

4\. check the individual scores of service users and airdrop 1/n to the total number of service users

&#x20;

Airdrop Criteria of NFT Membership Issuance Service

1\. Take a snapshot of users who have NFT membership using NFT issuance service

2\. Identify the NFT unique number of the snapshot aggregated users

3\. Compare and identify the aggregated NFT unique number and membership unique number

4\. Airdrop a set number of rewards based on NFT unique numbers


---

# 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://dmc.gitbook.io/dmcs-white-paper/english/token-policy/airdrop-logic.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.
