Contribution types based on the ZKsync criteria

[sergfeldman]

We can learn different contribution types to incentivize these cases by the Ubiquity OS

Criteria defined by the ZKsync https://blog.zknation.io/zk-token/

The remaining amount was allocated to contributors, companies, and individuals that laid the groundwork on which ZKsync was built:

• Contributors to organizations developing Ethereum including execution clients, consensus clients, developer tooling, RPCs, and other projects that have had a positive impact on ZKsync.
• Contributors to Github repos that have advanced blockchain technology and directly or indirectly contributed to ZKsync's success, including important work related to blockchains, zero knowledge proofs, developer tooling, and developer education.
• Educators onboarding developers and security researchers, and contributed to the ZKsync Community Hub on GitHub
• Contributors to Github repos working on zero knowledge proofs, Ethereum dev tooling, open-source software.
• Security researchers participating in audit contests hosted by Cantina, Code4rena, and CodeHawks
• ZKsync community mods, ZK Credo translators, ZK Quest participants, and in-person event attendees.
• Finally, 0.4875% of the total supply was allocated to a small group of experimental onchain communities for exploring novel ways to organize using tokens and NFTs. These communities include $DEGEN and $BONSAI airdrop recipients, Crypto the Game players, and Pudgy and Milady holders.

[sergfeldman]

Builders

Allocated to individuals, developers, researchers, communities, and companies who contributed to the ZKsync ecosystem and protocol through development, advocacy, or education

https://docs.zknation.io/zk-token/zk-airdrop#contribution-based-airdrop