How to 'Rescue' the ZKsync Airdrop?
TechFlow Selected TechFlow Selected
How to 'Rescue' the ZKsync Airdrop?
Set the initial allocation of shares to "users" at 20.3% and adopt a points system similar to Arbitrum.
Navigating Web3 tides with focused insightsAuthor: CC2 Ventures
Translation: Felix, PANews
Recently, the zkSync airdrop has been a hot topic in the crypto community, with many users criticizing the concentration of token distribution and excessive allocations to Sybil addresses.
Crypto KOL CC2 Ventures published a thread explaining how zkSync could "rescue" its airdrop and achieve a more "decent" distribution.
Below is the full content.
First, remove projects that have not yet deployed on zkSync from the 17.5% “Airdrop” portion. They will receive allocations once “ecosystem incentives” go live. Second, increase the initial airdrop supply by 3.5%.
These two steps set the initial allocation to “users” at 20.3% (not 21%, as 0.7% goes to some zkSync-native projects, which is reasonable).
Cap the maximum eligible airdrop per address at 85,000 tokens (currently up to 100,000). The reduction for these top-tier addresses would be minimal but sufficient to reallocate supply to previously ineligible addresses, maximizing decentralization.
Use Arbitrum’s anti-Sybil list and third-party platforms (such as Nansen) to scan all addresses. This could free up an additional 0.5%–0.7% of supply—or even more.
Overall, zkSync's initial airdrop criteria were relatively fair. LPers, time-weighted asset holders, memecoin traders, and holders were all well rewarded—so don’t cut them further. Now there’s an extra ~6% available (author did not calculate exact figures, only reverse-engineered via this thread).
-
Reallocate supply using Arbitrum/third-party Sybil filters + un-deployed zkSync project allocations
-
zkSync’s FDV slightly above Arbitrum’s ($9.87B; ZK ~$0.47)
Roughly 6% of supply is available for reallocation (potentially up to 8%), worth approximately $592 million—depending on how many wallets exceed 15k and the number of filtered Sybil addresses.
After extensive Sybil filtering, approve an additional 300,000 addresses. Each newly qualified address would receive approximately 1,973 ZK tokens—some more, some less. Now apply a point system similar to Arbitrum’s for these 300,000 previously ineligible addresses:
-
Connected to zkSync Lite before zkSync Era launch
-
Completed 3 transactions on zkSync Lite before Era launch
-
Categorize transaction volume on Era into tiers: 1K, 10K, 25K, 100K
-
Categorize number of transactions on Era into tiers: 10, 25, 50, 100, 250
-
Categorize months active on Era into tiers: 3, 6, 12
Design a solid points system for these metrics. If it seems too extreme, perhaps add small bonus rewards and tier them appropriately. Adjust percentages and scoring until it “makes sense,” and finalize with 1 million addresses as the baseline.
Some may still be dissatisfied—after all, zkSync has 8 million addresses, and not everyone can get an airdrop (survival of the fittest). But now, the initial circulating supply is significantly more decentralized.
The author reiterates: no detailed calculations were made for all the above steps, so numbers may be highly inaccurate. However, applying even some of these measures could certainly salvage the situation.
Join TechFlow official community to stay tuned
Telegram:https://t.me/TechFlowDaily
X (Twitter):https://x.com/TechFlowPost
X (Twitter) EN:https://x.com/BlockFlow_News
PANews
