create dairdrop application

[jyaymusk]

Project Abstract

Decentralized airdrop application that does not must require a centralized server, and it can also create some community interaction games based on it. Based on this project, the community will explore more airdrop strategies within the Polkadot ecosystem and continuously improve the user experience in airdrops.

https://github.com/dota-network/Grants-Program/blob/master/applications/dairdrop.md

Grant level

• Level 1: Up to $10,000, 2 approvals
• [2] Level 2: Up to $30,000, 3 approvals
• Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

• The application template has been copied and aptly renamed (project_name.md).
• I have read the application guidelines.
• Payment details have been provided (Polkadot AssetHub (USDC & DOT) address in the application and bank details via email, if applicable).
• I understand that an agreed upon percentage of each milestone will be paid in vested DOT, to the Polkadot address listed in the application.
• I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
• The software delivered for this grant will be released under an open-source license specified in the application.
• The initial PR contains only one commit (squash and force-push if needed).
• The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
• I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

[PieWol]

Hey, thanks a lot for the application. It sounds very interesting and I also don't know about an existing solution that solves the issue of distributing airdops. I left a few comments and questions for you to review.
Looking forward to your answers :)

[PieWol]

Where can I see these contributions of yours that involve parachains or substrate development? On your github I only found your work on the dota indexer.

[jyaymusk]

Where can I see these contributions of yours that involve parachains or substrate development? On your github I only found your work on the dota indexer.

In the past few years (from 2019 to the present), I have primarily developed in an anonymous state due to privacy concerns. I was previously employed by several parachain teams and was a core development member for them. If you're interested, we can discuss this privately.

[PieWol]

great, please forward this private information via e-mail to grants@web3.foundation.

[jyaymusk]

great, please forward this private information via e-mail to grants@web3.foundation.

I will send you an email in a few days.

[PieWol]

Hey @jyaymusk , I don't think I have received an email from you yet. Can you still follow up on this? :)

[PieWol]

what is the backend? I suppose the substrate pallet and the ink implementation serve directly as the backend.

[jyaymusk]

what is the backend? I suppose the substrate pallet and the ink implementation serve directly as the backend.

On-chain storage primarily contains the final state and completed Merkle proof verification. We need to provide an off-chain backend that allows users to obtain their Merkle proofs, submit transactions to claim airdrops, and access more information about the airdrop, such as progress, the number of participants, and which users have not yet participated. Additionally, anyone should be able to claim airdrops for others.

[PieWol]

isn't this part of the web-service?

[jyaymusk]

isn't this part of the web-service?

Yes, considering the PC app, I developed it as part of the public section. The web server simply calls the APIs it needs from there.

[PieWol]

To what granularity will the merkle tree resolve? To each individual address? To a group of addresses which will always be claimed together? I'd love to hear more about the strategy. Have you conducted any research up to which address amount your solution is able to scale?

[jyaymusk]

To what granularity will the merkle tree resolve? To each individual address? To a group of addresses which will always be claimed together? I'd love to hear more about the strategy. Have you conducted any research up to which address amount your solution is able to scale?

We will provide a complete Merkle tree for each airdrop event, which includes the airdrop information for every user and is stored in the backend. This will support up to 2^160 addresses.

[PieWol]

If you are storing all the addresses individually why do you need the merkle tree at all? Still do you have a more in depth design doc to share about your concept? I'd appreciate it.

[jyaymusk]

If you are storing all the addresses individually why do you need the merkle tree at all? Still do you have a more in depth design doc to share about your concept? I'd appreciate it.

You can think of each airdrop event as a Merkle tree, where each person's airdrop information is stored in the leaves. They will receive their Merkle proof from here and then submit it to the chain for verification to obtain their airdrop amount.

[jyaymusk]

This is very flexible and scalable. By adding some information to each recipient's airdrop data, we can create conditional claims for everyone, which can be applied in gaming and social applications.

[PieWol]

I'm still keen to see a design document

[jyaymusk]

Hey, thanks a lot for the application. It sounds very interesting and I also don't know about an existing solution that solves the issue of distributing airdops. I left a few comments and questions for you to review. Looking forward to your answers :)

Thank you very much for your outstanding work and responses. I'm very happy that we can discuss this application together.

[jyaymusk]

Hey, thanks a lot for the application. It sounds very interesting and I also don't know about an existing solution that solves the issue of distributing airdops. I left a few comments and questions for you to review. Looking forward to your answers :)

@PieWol, Thank you very much for your suggestions. I've updated the application accordingly. Regarding the desktop app issue, I agree that we should remove it, allowing us more time to focus on UX optimization and creating a product that is very user-friendly. However, our team is considering that community users are often non-technical and have diverse airdrop needs. Some may not want to provide a remote web service or might not know how to run a local program using Docker, which could impact community engagement and growth. If you have better suggestions, we are open to them. Our goal is to create an airdrop application that can be used in all scenarios.

[PieWol]

Hey @jyaymusk
thanks for getting back to me this quickly. I noticed that some of my comments were not addressed. E.g. the pc-app is still mentioned in the features and deliverables. Looking forward to your replies and changes once again.

[jyaymusk]

Hey @jyaymusk thanks for getting back to me this quickly. I noticed that some of my comments were not addressed. E.g. the pc-app is still mentioned in the features and deliverables. Looking forward to your replies and changes once again.

Thank you very much for your professionalism and patience. I hope my response addresses your questions.

[jyaymusk]

Hey @jyaymusk thanks for getting back to me this quickly. I noticed that some of my comments were not addressed. E.g. the pc-app is still mentioned in the features and deliverables. Looking forward to your replies and changes once again.

I will update the application in a few days.

[jyaymusk]

Hey @jyaymusk thanks for getting back to me this quickly. I noticed that some of my comments were not addressed. E.g. the pc-app is still mentioned in the features and deliverables. Looking forward to your replies and changes once again.

@PieWol, I have updated the application. If there are any new questions, we would be very happy to discuss them with you and would appreciate your feedback. I will send you an email as soon as possible. Enjoy your weekend!

[idfree]

Thank you very much for this proposal! A decentralized airdrop application is exactly what the Polkadot ecosystem needs, and at AIWeb3, we've been eagerly awaiting something like this for a long time. Do you think it could be integrated directly into our website? And when might this application be ready for use? Looking forward to seeing this in action!

[jyaymusk]

Thank you very much for this proposal! A decentralized airdrop application is exactly what the Polkadot ecosystem needs, and at AIWeb3, we've been eagerly awaiting something like this for a long time. Do you think it could be integrated directly into our website? And when might this application be ready for use? Looking forward to seeing this in action!

@idfree We hope to have it ready for use right after the launch of the Dota 2.0 network, which will still take about a month of development time. I'm very pleased that we share this common need, as it allows us to maintain it together in the future. Such an airdrop application will be very useful for community events, and in the future, we will only need to add a small code to create some gaming applications on Telegram or the web. If you have any better ideas, we can also consider adding more features. We envision that in the future, Polkadot airdrop creators will only need to select the network and connect their wallets on our webpage, and then simply click the Assets icon to quickly create or claim their airdrops. Imagine being able to create an airdrop for any Telegram or Discord group with just a click on a webpage. Isn't that cool?

[PieWol]

Hey @jyaymusk , I have followed up on a few more comments. Feel free to start the KYC process already. I would also appreciate more in depth documentation about the concept of distributing airdrops. Anyways I'll share your application with the committee.