Final Report: ZK Stack Content Program (Community Activation RFP 2 – Extension)

Token Mechanics Community Activation Program
1

Final Report: ZK Stack Content Program (Community Activation RFP 2 – Extension)

Program Period: March 16 – June 12, 2026
Final Report Date: June 16, 2026 (due June 18, 2026)

Key Results

The ZK Stack Content Program was the 13-week extension of Community Activation RFP #2. It moved from the original open-submission experiment to a focused cohort of proven creators delivering consistent, high quality content on X.

The content strongly aligned with the required narratives

  • ZKsync Privacy & Prividium

  • ZKsync as the Bank Stack / institutional infrastructure

  • ZK token utility (fee flow, staking, governance, adoption)

  • ZKsync beyond L2 (tech differentiation, interop, comparisons to other solutions)

Total Combined Output

  • Total Posts: 650

  • Total Views: 1,270,497

  • Total Comments: 3,252

  • Total Likes: 19,373

  • Total RTs: 2,966

These figures exceed the program’s success KPIs

Content Highlights

Privacy / Prividium & Bank Stack / Institutional Adoption

  1. zksyncturk – Informative post about Cari Network and why banks building on ZKsync
  2. joinelastic (ENC) – Post about five US banks + multiple “The Bank Stack” videos
  3. CryptoWalker46 –Token insights during crash + corporate blockchains
  4. joinelastic – “Privacy, Zcash Vulnerability and ZKsync Prividium” + Bank Stack videos
  5. raadheyyyyy – Videos on The Truest-Privacy project/ZKsync and ZK X NYSE

ZK Token, Fee Flow, Staking, Governance & Adoption

  1. dinomaxzk – $ZK token meme
  2. neutize – Governance post
  3. satyaxbt– Deep posts on ZKsync vs other L2s and Prividium
  4. Multiple strong posts on ZK token fee flow, staking, and institutional adoption from raadheyyyyy,neutize,zksyncturk, and others.

ZKsync Beyond L2 / Tech Differentiation

  1. ZaksansPG – Vitalik recycle post
  2. CryptoWalker46 – ZIP-16 v31 interop content
  3. Various high-engagement posts comparing ZKsync vs Canton and explaining ZKsync’s unique advantages.

For the full breakdown of the highlights with links to the posts, follow this link : Highlights 3 Months RFP - Google Sheets

Overview of Content Themes & Performance

The cohort stayed tightly focused on the required narratives. Memes and short videos drove broad awareness and virality. Threads, explainers, and videos performed best for education and deeper engagement. Localized content (especially Turkish) extended reach effectively. Creators responded quickly to ecosystem developments such as governance proposals, partnerships (Cari, Revolut), token updates, and interop upgrades.

Conclusion & Recommendations

The extension successfully scaled the original RFP #2 model into a reliable content program. With 650 posts, 1.27 million views, and strong engagement, the program exceeded its KPIs while maintaining excellent narrative focus.The selected creators delivered high quality, on-theme content that reinforced ZKsync’s positioning around privacy, institutional infrastructure, and ZK tech advantages.

Recommendations for future programs:

  • Continue with the curated high performing cohort model.

  • Increase emphasis on short-form video and interactive content.

  • Maintain close alignment with real time developments (governance, partnerships, token utility).

  • Reconsider a more stable total budget to keep the program flexible and expandable.

All deliverables completed on schedule.

We have built a dedicated dashboard for creators that tracks their total performance and RFP performance. For simple navigation, the main page shows the total performance, while you can scroll down to open each creator and view their individual performance, for example, follower growth and every post included in the RFP.

Questions welcome!

4 Likes
2

First of all, hello everyone!

As individuals who have been contributing to ZKsync for nearly four years, it has now been exactly 10 months since we founded and began building ENC, an initiative that started with a simple vision.

Over the years, we spent countless hours supporting the community, answering questions, assisting users, and helping newcomers better understand the ecosystem. Through those experiences, we noticed a recurring pattern.

While ZKsync continued to evolve and expand, many people still viewed it as simply another Layer 2.

The reality was very different.

ZKsync was becoming an ecosystem of interconnected ZK Chains, each with its own purpose, community, and specialization. Yet much of this remained poorly understood across the broader community. Concepts such as the Elastic Network, interoperability, governance, and the growing network of chains were often either misunderstood or entirely unknown to many participants.

What stood out to us was that the technology was advancing faster than the collective understanding around it.

Builders were shipping. New chains were launching. Governance was evolving. The network itself was becoming larger and more interconnected. Yet many people were still seeing only a small piece of what was actually being built.

ENC was created to help bridge that gap.

Our objective was simple: explain what was being built in a way that was accessible, engaging, and easy to understand while helping people discover the broader ecosystem that existed beyond a single chain.

At the same time, we wanted to approach the ecosystem differently.

Rather than viewing each chain as an isolated community, we believed the Elastic Network should be treated as a connected ecosystem. We wanted to help create awareness across chains, encourage discovery, and strengthen the connections between communities spanning more than 18 different networks.

Because interoperability is not only about technology.

The strongest networks are built when information, ideas, builders, users, and communities move freely as well.

In many ways, what we set out to build was the community layer of interoperability.

Over the last 10 months, this vision evolved into a growing ecosystem hub that delivered educational content, technical explainers in an easy and engaging format, Custom-designed infographics, weekly ecosystem recaps, Motion graphics and animations, seasonal campaigns, AI-powered animations, community initiatives, giveaways, and ecosystem tools such as the Flywheel Simulator.

Each initiative was built around the same core idea: making the ecosystem easier to understand, easier to discover, and easier to participate in.

Beyond written content, the ENC team invested heavily in original creative production, designing custom infographics, educational visual explainers, ecosystem diagrams, campaign assets, article visuals, and video content. These assets were created through a combination of research, scripting, visual design, and post-production workflows, helping simplify complex ZKsync concepts and improve accessibility for a broader audience.

Throughout this period, the ENC team generated:

• 2.28 million impressions

• 52,596 engagements

• 10,001 profile visits

This equates to an average of approximately:

• 190,000 impressions per month

• 4,380 engagements per month

• 6,270 impressions per day

• 145 engagements per day

One of our flagship initiatives, TheNewsPaper series, summarized weekly developments across more than 18 chains and generated 21,136 views across its first seven editions, averaging approximately 3,019 views per episode.

While those numbers are encouraging, we have always viewed them as a byproduct rather than the goal itself.

The real objective was helping people better understand ZKsync, discover the broader ecosystem, and feel connected to something larger than their individual community.

That remains just as true today as it was on day one.

While we are proud of what has been built so far, many of our original goals remain unfinished, including weekly podcasts, the official ENC website, recurring ecosystem-wide events, and several additional initiatives planned for the future.

In many ways, we still feel like we are only getting started.

We are committed to remaining an active part of the ecosystem not only by continuing the work we have done so far, but by expanding it and further strengthening the community layer that connects the broader ZKsync ecosystem. As we move forward, we will be looking forward to new and updated RFP opportunities that enable us to keep building, supporting, and contributing to the growth of the network.

Best Regards.

ENC TEAM / Raadheyyyyy & Itslawyey

2 Likes
3

Dear ZK Team and Community Members,

I deeply appreciate the high-quality content created by many experienced contributors in the forum. These discussions have provided significant value in terms of technical depth and governance.

However, I have also noticed that the current format of content remains quite difficult for most ordinary token holders and potential users to understand. Many non-technical users have expressed that reading these materials feels like a primary school student trying to learn university-level courses, which often leads to frustration and information anxiety. This is likely one of the reasons why we frequently see misunderstandings and negative comments about ZK across various platforms.

I believe that relying solely on traditional passive content creation is no longer sufficient to support ZK’s long-term development. We need a more proactive, accessible, and scalable way to communicate with the community.

My suggestion is to develop a ZK-based AI Agent that can:

  • Be available 24/7 to respond to user questions across platforms such as X, Discord, and the forum (both proactively and reactively);
  • Explain technical concepts, governance proposals, and product usage in language that ordinary people can understand;
  • Provide differentiated guidance for different groups — ordinary users, developers, and long-term holders;
  • Help developers quickly find relevant technical resources and development paths;
  • Reduce information asymmetry and FUD, allowing more people to patiently understand ZK’s long-term value.

This AI Agent is not intended to replace existing content creators. Instead, it would serve as a supplement and amplifier, making high-quality content more accessible and digestible for a broader audience.

I understand that deploying an AI directly comes with challenges, such as accuracy issues, hallucinations, and ongoing maintenance costs. Therefore, I suggest a phased approach:

  1. Start with a limited scope (for example, only answering frequently asked questions on the forum);
  2. Establish a human review and correction mechanism;
  3. Gradually expand its coverage based on performance and feedback.

I believe that if we can implement this properly, it would provide meaningful support for ZK’s long-term ecosystem development.

These are my personal thoughts, and I welcome any discussion or suggestions from the team and the community.

1 Like
4

Thank you for sharing your thoughts.

We actually agree with the core challenge you’re highlighting. In many ways, it’s the same challenge that led us to create ENC in the first place.

Over the years, we kept noticing a recurring pattern (something we’ve said before) but we’d like to take a step back for a moment and share a little more context around it because it played a big role in why ENC came to exist. It might take a few minutes to read, but we hope you’ll find it worthwhile.

Whenever people talked about ZKsync, they were often talking exclusively about Era.

We would regularly come across posts comparing ZKsync solely through Era TVL, Era activity, or Era user numbers, followed by conclusions such as “ZKsync is just another L2,” “Nobody is using ZKsync,” or “ZKsync isn’t growing.”

Those weren’t just observations we noticed from a distance. We spent a lot of time actively engaging in those conversations. If someone reduced ZKsync to Era alone, more often than not we would reply, provide context, and try to explain the broader picture in a way that felt approachable and easy to understand, rather than simply throwing more technical jargon into the conversation and hoping it would help.

A significant part of our work throughout late 2025, particularly during October, November, and December, involved writing replies, educational/engaging posts, (easy to understand) articles, and ecosystem breakdowns aimed at addressing exactly this misunderstanding. Def not to argue with our people, but to help explain that many of the conclusions being drawn were based on looking at only one piece of a much larger ecosystem (THE ZKSYNC NETWORK).

In many cases, people weren’t misunderstanding the numbers they were looking at. They were simply looking at one part of the ecosystem and assuming it represented the whole.

What often got missed was that ZKsync had already evolved far beyond a single chain.

ZKsync Era is one chain within the ZKsync Network.

ZKsync ≠ just ZKsync era

Alongside the Era zkChain, there are 15+ other similar zkChains, each built around different goals, communities, and use cases. Some focus on gaming, some consumer focused, some on trading, some on creators, some are designed for institutions, and others serve entirely different sectors.

That distinction was often missing from the conversation.

As a result, people would look at Era alone and assume they were looking at all of ZKsync, even though an entire network of chains was growing around it.

So a large part of ENC’s work became helping people zoom out and see the bigger picture. And not really by throwing more technical terminology at them, but by helping connect developments that often appeared unrelated when viewed individually.

: Through storytelling, ecosystem newspapers, animations, simplified breakdowns, community discussions, and everyday conversations, we tried to explain not only what was happening, but why it mattered and how it connected to everything else being built across the network.

We also learned that not every misunderstanding appears in a forum post or on X. Sometimes it starts with someone simply looking for clarity. Some of those conversations happened through our Telegram community, where people reached out with questions, assumptions, or concerns about ZKsync, and often those one-on-one discussions became opportunities to provide context that doesn’t always fit into a thread.

In many ways, we were trying to solve the same challenge you’re describing: helping people understand what is being built without needing to become experts in every technical detail.

And this is also why we find your AI Agent idea interesting.

The approach is different, but the challenge being addressed feels very familiar. AI could help make information more accessible, answer questions instantly, and reduce friction for newcomers, while community-driven initiatives can continue providing context, discussion, and the Human Side of education that helps information truly stick.

We believe there is room for both.

Ultimately, both are trying to solve the same problem:

Helping more people understand what is actually being built.

2 Likes
5

Love the results.

The statistics are very good but I feel we can do better.

From my understanding, Community Activation Pilot Program is still live and I would love to create a proposal titled ZKsyn on campus initiative, a 3 month program targeted at 4 universities and general Africa Communities, this initiative will focus on

  1. Onboarding and education of thousands of university students to ZKsyn

  2. Training of both technical and non-technical skills

  3. Product development

  4. Massive Social Media activity

We have done it with Stellar and we can do it again

6

Critical Feedback: Economic Impact, Audience Reality, and Accountability

While the report shows high engagement metrics, it does not answer the only meaningful question for a treasury-funded program: what did the token or ecosystem actually gain in economic terms from this spend?

1. No demonstrable benefit to token performance or demand

The program period coincided with a price decline from approximately $0.022 to ~$0.011 (~50%). While marketing is not expected to control price, there is also no evidence of:

increased sustained buying interest
improved demand formation
stronger holder retention or accumulation trends

If the objective of “community activation” is to translate attention into participation or demand, then the observable outcome does not support that claim.

2. Retail audience by design , but no visible conversion

Despite institutional framing in narrative terms, the actual distribution channel is clearly retail-facing social content.

This implies the real mechanism was:

retail exposure –> attention –> potential token buying behavior

However, there is no indication that this attention translated into measurable demand. In practice, the audience is small retail participants, not institutions, and institutions do not respond to memes, repost cycles, or influencer content.

3. Question of value creation vs speculative promotion

A large portion of output functions as narrative reinforcement around the token and ecosystem. This raises a key question:

did the program create adoption, or primarily attempt to stimulate retail interest in the token?

If the latter, then the effectiveness must be judged on market response , which in this case shows no positive correlation with price or demand strength.

4. Governance concern: execution and reporting concentration

There is also a structural issue in program design: the same administrative entity appears to be involved in proposal design, execution coordination, and final reporting.

This concentration of roles reduces independent validation of outcomes and creates a situation where:

success metrics are defined internally
performance is reported by the same party responsible for execution
there is limited external verification of impact

This is not necessarily improper, but it is a governance weakness that should be acknowledged.

Conclusion

Overall, it is difficult to justify that the ~300k ZK allocated to this program produced measurable economic return for token holders or in general a benefit that would justify the treasury spending.

The outcome appears to be high-volume content production with no clear evidence of demand generation or ecosystem growth, raising concerns about treasury efficiency and accountability in “community activation” programs.