作者:@Web3Mario(https://x.com/web3_mario)
摘要:上周最火热的议题肯定是ZKsync的公开空投查验的事件了,本来笔者正在学习并书写一些关于TON的DApp开发的学习经验,但是看到这个颇具争议的事件,以及引发的社区的广泛讨论,颇有一些感受,因此撰文一篇,希望与大家分享。总的来说,ZKSync的空投方案采用了一个基于财产证明的分配方式,更聚焦于对开发者,核心贡献者和ZKSync原生Degen巨鲸的奖励,这就造成了一个局面原生Degen巨鲸在笑,撸毛工作室在叫。
For a long time, Web3The industry seems to have formed a paradigm of attracting users to use products through Airdrop, thereby achieving a cold start of the project. This is especially true in the Layer2 track. By guiding developers and users’ expectations for potential airdrops, it stimulates developers to actively build and maintain DApp, while stimulating users to bridge funds to target Layer2 in the early stages of development, and actively participate in the ## running on target Layer2 #DApp, so as to activate the ecology, this has become a standard.
因此在過去,用戶普遍對於ZKSync的空投預期是對標它的兩個直接競品,Arbitrum 和Optimism。當然無論從行業影響力,VC背景,募資規模等角度來思考,這個結論都是合乎邏輯的,然而結果卻大相徑庭,這就導致了很多復用過去經驗來參與ZKSync的用戶似乎並沒有得到期望內的獎勵數量,從而導致了社群陷入了廣泛的爭論中。
为了探究这个争论背后的原因并探讨一些对未来的借鉴意义,自然是需要回顾一下之前的Arbitrum和Optimism的空投规则的设置。首先回顾一下Arbitrum的空投活动,这要追溯到2023年3月,其为Aribitrum用户分配了占总供应量11.62%的Arb空投,同时为Arbitrum生态中运行的DAO分配了1.13%的Arb空投。空投活動的設定是基於2023年2月##6日的快照數據,針對使用者俱體的規則如下:#
Each detailed rule will have a specific score calculation method. The upper limit of the score is 15 points. This score is calculated using In order to determine the number of Arb that the user can receive, the calculation method can be approximated as a linear relationship, but the starting reward starts from 3 points. The capped reward is 10200Arb. As for the rewards for DAO, the specific amount is determined directly according to the activity evaluation method. From the results, the final number is 137 DAO received airdrops, among which Treasure and GMX received the most, respectively. For 800 ten thousandArb, according to the current essence, this is really a huge profit.
接下來回顧Optimism#,與#Arbitrum不同,Optimism 的空投共分多輪次進行,總共分配獎勵數量佔總供應量的19%,其最早的第一輪空投活動要追溯到 2022年6月,總共有5%的獎勵被分發給了26萬個位址,截止到目前已經進行了四輪空投,其每輪空投的具體規則如下:
from From the above review, it is not difficult to find that the number of interactions will be an important reference indicator in its specific activity settings. Users who interact more frequently will usually receive more rewards.然而这个潜规则似乎被ZKSync摒弃了,在ZKSync的空投设计中,ZKsync 用户的资格和分配分为四个连续步骤来选取并计算,具体规则大致如下:
从具体规则我们不难发现,在奖励的计算中并不涉及到交互次数这个纬度,更聚焦在单个账户的资金量与配置风险资产的意愿度。因此当结果公布之后,让很多秉持着过去经验在ZKSync上大量交互的撸毛党或工作室大跌眼镜,这也是引爆整个争议的源头。因为该部分用户为了增加获得潜在空投的地址数量,通常会选择将大资金尽可能的分散到地址群中,这些地址群通常为几百甚至上千个,并使用小资金参与某协议,通过预判一些可能的激励行为,通过自动化脚本或手工的方式频繁的刷交互,做任务的方式提高潜在的收益。而ZKSync的空投设置让这个策略失效,很多频繁交互的地址所付出的手续费甚至都比获得的奖励还高,这自然引起了该部分人群的不满。
而且我们在X中不难发现大量的空投猎人KOL,该部分人群以教大家如何方便获得项目方空投为主题发布内容,通常有着广泛的粉丝群体,具有较强的号召性,因此通过社交媒体给ZKSync官方施压,从而期望改变这个局面。然而从官方的态度来看,似乎也很强硬,并没有因承压而修改规则,所以才有了现在的局面。争论的过程中所引发的对于一些可能的作恶行为的指摘与辩解更是这场舆情大战的看点。
从结果来看,两边的诉求似乎都可以理解,个中对错只能看从什么角度去论述了,但我认为有些东西是值得思考的,那就是时至今日,Web3项目冷启动阶段的核心价值用户究竟是谁,或者说什么样的用户才是冷启动阶段应该去激励的用户。
对早鸟参与者基于Airdrop奖励,已经被证明是一个行之有效的Web3项目冷启动的手段,好的空投机制设置能够帮助项目在早期高效的吸引种子用户,同时通过刺激用户对协议关键行为的使用而完成用户教化,增加产品的粘性。这也是很长一段时间内,大部分Web3项目的空投设置着重于对交互行为进行激励的根本原因,然而这样做带来了一个弊端,就是降低了获得奖励的门槛,容易使得活动遭遇女巫攻击。因为交互行为是容易被自动化和批量化,这就给了很多专业团队批量操作的空间,当大量的机器人账户涌入后,虽然会让协议出现短暂的虚假繁荣,然而这些“用户”通常是逐水草而居,无法为项目未来的发展提供动力,在获得奖励后大部分也会套现用于增加资金周转率从而提升收益,这种激励机制反倒稀释了项目方对于那些真正价值用户的奖励数量,实在得不偿失。
那么为什么这种机制在早期效果不错呢,这自然是由于彼时类似的专业团队并没有那么多,大部分用户还没有对这种激励机制形成思维惯式,交互行为还是比较纯粹的,属于真实用户,这就让激励能够较为高效的分配给这些用户,由此产生的财富效应也帮助项目方实现上述好处,然而随着于此而来的赚钱效应的影响,这种方式显然已经无法有效的吸引真实用户。我的一个切身的感受,以交互为主要激励对象的空投活动的效用到Arbitrum空投时基本上已经到了顶点。
这也是ZKSync想要围绕资产相对规模而舍弃使用交互数来作为价值用户识别的依据的根本原因。然而这种财产证明方式也未必没有问题。虽然能够较为有效的识别并排除女巫攻击的风险,但与之而来的新问题就是垄断所引发的财富分配不均。
We know that one of the core values of the Web3 project is the bottom-up distributed autonomy model. This means that the support of grassroots users (real users with small amounts of capital) is the basis for the development of a project. It is precisely with the grassroots users that some whale users can pour in and form a more sustainable development form. After all, the financial advantage is still available in most scenarios. Only if there are enough grassroots users, the whale users will benefit. Just big enough. Then the distribution system of property certificate will lead to the obvious benefits of whale users among its early bird users at the beginning of the cold start. This makes it difficult to form effective incentives for grassroots users, and naturally it is impossible to form a cohesive community.
In the final analysis, for the Web3 project, when designing the cold start mechanism, you still have to carefully consider the value of your product to users. The top priority is to create a portrait and design a corresponding mechanism based on the current environment to effectively motivate the above-mentioned value users while trying to avoid witch attacks. Therefore, how to design your own cold start mechanism is a very valuable topic, and everyone is welcome to leave a message in my X for discussion. Brainstorm some fun options together.
The above is the detailed content of ZKSync airdrop caused controversy, let's look at the dilemma of cold start of Web3 project. For more information, please follow other related articles on the PHP Chinese website!