ZK Airdrop
Certain jurisdictions are blocked from the ZK airdrop, these include: Cuba; Iran; North Korea; Russia; Syria; specific regions of Ukraine: Crimea, Donetsk and Luhansk. These geographical regions must be blocked to comply with the sanctions regulations set forth by the U.S. Department of Treasury’s Office of Foreign Assets Control (“OFAC”), the United Nations Security Council (“UNSC”), the European External Action Service (“EEAS”), and His Majesty’s Treasury (“HMT), which mandate the prohibition of providing product or services accessible from domains to persons from specific countries and territories. Additionally, persons residing in the United States will also be prohibited from participating in the airdrop.
There are two ways in which wallets qualified for the 17.5% airdrop:
Users (89%): ZKsync users who bridged funds onto ZKsync Era and met at least one of the seven eligibility criteria.
Contributors (11%): Individuals, developers, researchers, communities, and companies who contributed to the ZKsync ecosystem and protocol through development, advocacy, education or participation regardless of their ZKsync network usage.
Usage-Based Airdrop
Eligibility and allocations for ZKsync users had four sequential steps:
Eligibility: Every address that has ever transacted on ZKsync Era and ZKsync Lite was checked against eligibility criteria.
Allocation: A value-scaling formula adjusts an address’s allocation based on amounts sent to ZKsync Era and how long those crypto-assets have stayed on the wallet.
Multipliers: Addresses that met certain criteria could receive multipliers on their allocation.
Sybil Detection: A standard sybil filtering methodology applied heuristics to detect bot behavior.
Step 1: Eligibility
Every address that has ever bridged funds into ZKsync Era was checked against eligibility criteria that identifies people who thoughtfully spent time exploring ZKsync. Each address must have at least one point to be eligible for the airdrop.
Step 2: Allocation
Allocations for eligible addresses was based on a value-scaling formula. This formula adjusts an address’s allocation based on amounts sent to ZKsync Era and how long those crypto-assets have stayed on the wallet. That is to say, an address with 100 USD sent to ZKsync Era at mainnet launch will be weighted more than an address who only put 100 USD a month before snapshot. Crypto-assets held on ZKsync Lite do not count when determining an address’s allocation.
Value scaling is a multi-step process:
First, the daily USD balance of crypto-assets held by an address was calculated, including the wallet’s balance or crypto-assets sent to DeFi protocols.
Next, to emphasize the increased utility of crypto-assets at work compared to those sitting idly in wallets, crypto-assets in DeFi were valued at 2x their nominal value.
Finally, the time weighted average balance was calculated for each wallet by summing the daily balance and dividing by total number of days in the snapshot period. The snapshot period from public mainnet launch of ZKsync Era on March 24, 2023 to March 24, 2024 is 366 days long.
Below are two examples demonstrating how value scaling is calculated and the effect which time, amount of money, and DeFi usage have on the resulting time weighted average balance.
Alice
Alice sent $100 in crypto-assets to ZKsync Era 250 days before the snapshot was taken. After 50 days, they sent another $100 in crypto-assets and kept it in their wallet for the remainder of the time until snapshot
Bob
Bob sent $1,000 in crypto-assets to ZKsync Era just 25 days before the snapshot was taken. He immediately put $500 in crypto-assets of this into a DEX liquidity pool and left the rest in their wallet where it remained until snapshot.
Recall that crypto-assets in DeFi protocols are weighted at 2 times their nominal value
Step 3: Multipliers
Each address could receive multipliers based on activity that signaled a high likelihood of human behavior or contribution to ZKsync. These multipliers apply on top of eligibility and allocations from ZKsync Era and Lite usage.
These multipliers include:
Hold one of these ZKsync native NFT collections at snapshot: Dudiez, Hue, Moody Mights, Webears, ZKPENGZ, zkSkulls, or zkVeggies.
These seven collections were selected based on having a median trade price of at least $25 and a total trade volume of $20,000 in the 30 days prior to snapshot.
Hold at least $50 of one of these ZKsync native ERC-20 tokens at snapshot: AAI, HOLD, KOI, MEOW, MUTE, RF, ZF, ZORRO.
Similarly to the seven eligible NFT projects above, tokens of the top seven projects ranked by market capitalization at the time of snapshot. Eight tokens are included because KOI and MUTE are the same project
Smart Contract Wallets created via ZKsync Era native account abstraction.
Held at least 50% of the ARB/OP/ENS airdrop for more than 90 days after claiming.
In the first 1,000 addresses to interact with qualifying Ethereum smart contracts at least two times. A qualifying contract is one with at least 100 ETH in transaction fees spend on it.
After Step 3, each address was assigned a token allocation. Addresses had to meet a minimum requirement of 450 ZK and were capped at a maximum of 100,000 ZK. Addresses with fewer than 450 ZK had their tokens recycled back into the pool. Addresses with more than 100,000 ZK had their excess tokens recycled back into the pool as well. These tokens were then redistributed and brought the minimum allocation up to 917 ZK.
Step 4: Sybil Detection
The combination of eligibility criteria, value scaling, and multipliers eliminated most bot swarms. However, our sybil detection methodology further filtered the remaining bots. It intentionally used a very conservative heuristics framework, to avoid accidentally punishing real people. The core idea is to find large groups of externally owned accounts (EOAs) that are ultimately owned by the same user or entity and filter them from the eligible addresses.
To group EOAs into clusters of common ownership, two heuristics were used:
CEX deposit address reuse heuristic
Common funding heuristic
Finally, the clusters from the two heuristics were combined into a single list of EOA clusters, and all the clusters with more than 20 EOAs were filtered.
CEX Deposit Address Reuse
The first heuristic leverages centralized exchange (CEX) deposit address reuse. CEXs create deposit addresses for customers to process deposits. Since they usually have a single deposit address per customer, if multiple addresses send crypto-assets to the same deposit address, they are likely all controlled by the same entity.
Using this insight, this heuristic groups EOAs that sent transactions to the same CEX deposit address during a 1 year period.
Funding Source Patterns
The second heuristic examines funding patterns. Every time a new address is created, its owner needs to fund it with ETH to pay for transaction fees. If we find a group of EOAs with the same ultimate funder, they are likely owned by the same entity. Concretely, we look for funding transfers of similar amounts that occurred within a predefined time window
Contribution-Based Airdrop
GitHub Developers and ZKsync GitHub Discussion Helpers must associate their address to their handle by June 25th, 00:00 CEST to claim. External Projects, Protocol Guild and ZKsync native project contributors will be able to claim starting June 24th, 2024
ZKsync Native Projects
215,250,000 Tokens
Allocation directly to the contributors and treasuries of ZKsync native projects building on ZKsync Era, including DeFi protocols, ZK chains, NFT collections, marketplaces, infrastructure, gaming, and more. A full list of these projects can be found here.
Builders
86,895,375 Tokens
Allocated to individuals, developers, researchers, communities, and companies who contributed to the ZKsync ecosystem and protocol through development, advocacy, or education
Onchain Communities
102,375,000 tokens
Allocated to a small group of experimental onchain communities for exploring novel ways to organize using tokens and NFTs.
Last updated
