Airdrop Farmers Frustrate Developers with GitHub Spam
Airdrop farmers have been spamming comments on GitHub repositories in an attempt to secure token airdrops from future projects. This practice has frustrated developers who are already stretched thin. Airdrop farming has been around since 2020 when some projects started giving governance tokens to early users. Initially, it focused on on-chain activity, but recent airdrops like Celestia and Starknet have changed their distribution criteria. For example, Celestia gave out 6% of its supply in an airdrop, with a third going to contributors on GitHub. Starknet allocated 7% of its airdrop to contributing developers.
Targeting GitHub Repositories for Potential Airdrops
GitHub repositories are now being targeted by airdrop hunters hoping to gain eligibility for future airdrops. One example is the Starknet airdrop, where eligible contributors received tokens for simple actions such as making comments that weren’t even merged. As a result, Scroll’s GitHub repository received over 1,000 comments from airdrop farmers over the weekend. To prevent spam, some projects have implemented limits on activity in their repositories. However, distinguishing between genuine contributors and airdrop farmers who have been using their accounts for a while can be challenging.
Preventing GitHub Spam and Potential Benefits
Developers can introduce measures to prevent spam on GitHub, such as limiting interactions in repositories. While the influx of comments may be frustrating, it can also lead to positive outcomes like identifying spelling mistakes and improving grammar in project repositories. Overall, it’s important for contributors to focus on their strengths rather than following trends and for projects to maintain a healthy ecosystem growth.
By
By
By
By