Open Question: What is a problem statement within zkSync that data can address?

Hey everyone.

Apologies for the clickbait open question.

I am here to ask the community: Is there a problem statement that data can help address? I am happy to engage with the community either here or elsewhere to discuss this. I tried popping the question on Discord, but I left because of too much noise.

Few examples of what I mean:

  1. A dashboard to track onchain activities of the DAO like token holders voting, delegating tokens, and voting for which specific proposals, etc. This is a good way to identify active tokenholders, and activate/re-activate formant tokenholders.

  2. A dashboard to track zksync’s airdrop stats based on – addresses receiving the token, selling, holding, and accumulating the token post the airdrop compared to the price of the token. etc. This could help understand what kind of addresses are holding and which ones are selling.

Or something else the community is looking for.

About me:

I am a research analyst at PYOR, an onchain data company. We work with the likes of Arbitrum and Cosmos for their data needs. We’ve built data solutions to track governance, capital efficiency, and DEX metrics.

Happy to chat with the zkSync community to see what we can build (if this post gets approved).

1 Like