ZKsync airdrop sparks controversy: a look at the dilemma of cold start for Web3 projects

This article is machine translated
Show original

Chainfeeds Introduction:

In general, ZKSync's airdrop plan adopts a distribution method based on property proof, focusing more on rewards for developers, core contributors and ZKSync native Degen whale. This creates a situation: the native Degen whale are laughing, and LuMao Studio is shouting.

Article Source:

https://foresightnews.pro/article/detail/62488

Article author:

Web3Mario


View:

Web3Mario: Airdrop rewards for early bird participants have been proven to be an effective means of cold starting Web3 projects. A good airdrop mechanism setting can help projects attract seed users efficiently in the early stage, and at the same time complete user education and increase product stickiness by stimulating users to use key behaviors of the protocol. This is also the fundamental reason why most Web3 project airdrops have focused on incentivizing interactive behaviors for a long time. However, this has brought a disadvantage, which is to lower the threshold for obtaining rewards and be prone to witch attacks. When a large number of robot accounts pour in, although the protocol will have a short-term false prosperity, these "users" usually live by the water and grass, and cannot provide motivation for the future development of the project. After receiving the rewards, most of them will cash out. This incentive mechanism dilutes the number of rewards for those truly valuable users. My personal experience is that the utility of airdrop activities with interaction as the main incentive object has basically reached its peak when Arbitrum airdropped. This is also the fundamental reason why ZKSync wants to abandon the use of interaction numbers as the basis for identifying valuable users based on the relative size of assets. However, this method of property proof may not be without problems. Although it is possible to effectively identify and eliminate the risk of Sybil attacks, the new problem that comes with it is the uneven distribution of wealth caused by monopoly. In the final analysis, for Web3 projects, when designing a cold start mechanism, it is still necessary to carefully consider the valuable user portraits for their products, and design corresponding mechanisms based on the current environment. It is of utmost importance to effectively motivate the above valuable users while trying to avoid Sybil attacks. Therefore, how to design your own cold start mechanism is a very valuable topic.

Content Sources

https://chainfeeds.substack.com

Source
Disclaimer: The content above is only the author's opinion which does not represent any position of Followin, and is not intended as, and shall not be understood or construed as, investment advice from Followin.
Like
Add to Favorites
Comments