[GAP-6] Allocate Remaining TPP-8 Tokens to ZKnomist

[bendob]

Name	Description
Proposal Title	Allocate Remaining TPP-8 Tokens to ZKnomist
One Sentence Summary	Approve the ZKsync Foundation’s allocation of up to 5,799,091 ZK remaining from TPP-8 to continue funding ZKnomist’s content and community work.
Proposal Author	ZKsync Foundation
Proposal Sponsor	ZKnomist
Date Created	1 September 2026
Version	1.0
Summary of Action	Approve the allocation of the remaining Community Activation proposal balance to fund ZKnomist, with the Foundation executing payments until the funds are exhausted or the engagement is terminated.
Link to Contracts	Not applicable — no onchain action is required to be executed by the Token Assembly.

Abstract

This proposal seeks Token Assembly approval for the ZKsync Foundation to allocate up to 5,799,091 ZK remaining from the Community Activation Pilot Program passed in TPP-8 to continue funding ZKnomist’s content, communications, and community engagement services.

The Foundation will execute the approved allocation in accordance with the expressed will of the Token Assembly. The engagement will continue until the allocated funds are exhausted or the agreement is terminated. Any unused tokens will be returned to the Token Governor Timelock.

Motivation

ZKnomist completed two seasons under the Community Activation Pilot Program, providing consistent content production, visual media, ecosystem education, community calls, case studies, and communications support.

During Season 2, ZKnomist supported 609 posts over 23 tracked weeks, generating approximately 9.75 million impressions and 81,899 engagements. The team met or exceeded its principal deliverables while supporting communications relating to ZKsync, Prividium, ZK Chains, governance, and broader ecosystem developments.

The remaining 5,799,091 ZK originates from the unspent Community RFP Pilot workstream approved for TPP-8. Reallocating this balance will maintain an established communications function without minting tokens or requesting a new treasury transfer.

Specification

By approving this GAP, the Token Assembly approves the ZKsync Foundation, as Program Administrator, allocating up to 5,799,091 ZK from the Community RFP Pilot balance exclusively to ZKnomist’s content and communications workstream.

The ZKsync Foundation will execute this decision in accordance with the expressed will of the Token Assembly by:

• Continuing the engagement until the allocated balance is exhausted or the agreement is terminated.
• Entering into or amending the necessary service agreement through ZKGPS.
• Administering payments and applicable compliance and performance requirements.

The allocation is a spending ceiling rather than a commitment to disburse the entire amount.

Budget and disbursement

The total allocation is 5,799,091 ZK. Payments will be made monthly for services delivered, continuing ZKnomist’s existing Season 2 compensation rate of $10,000 per service month for the full scope described below.

Payments will be converted to ZK using the seven-day moving average ZK/USD price on the final day of each service month.

Based on recent ZK prices, the allocation is expected to fund approximately four to six months. The actual duration will depend on the ZK/USD price and may be longer if the token price increases. No payment may cause the total allocation to exceed 5,799,091 ZK.

If the remaining balance cannot cover a complete month, the Foundation may agree to a proportionately shorter final service period and payment.

Deliverables

The service agreement should require, at minimum:

• Five ZKsync-focused posts per week.
• Two original videos per week.
• One Weekly Roundup thread per week.
• Two ZK Chain case studies per month.
• Two community calls per month, subject to participant availability.
• Discord announcement and community support.
• A public highlights update every three months covering notable content, aggregate impressions and engagements, key outcomes, and priorities for the next period.
• A final public highlights update within 30 days of the engagement ending.

Any changes to the deliverables require approval from the ZKsync Foundation.

Administration and oversight

The relevant tokens are already held in the following program multisig:

• Multisig: Community_Pilot_Multisig2025
• Address: 0x3Da86E64768209Dcd38344Ee052A57c904dD9696
• Control: ZKsync Foundation 3-of-5 multisig

No tokens will be minted, and no transfer from the Token Governor Timelock is required. Implementation consists solely of administrative, contractual, and payment actions by the ZKsync Foundation and ZKGPS.

The Foundation may pause or terminate payments based on non-performance or non-compliance. Upon completion or termination, any unused ZK will be returned to the Token Governor Timelock.

[TheZKnomist]

We’re incredibly grateful for this opportunity!

Thank you for your trust in us. We’ll continue to grow and do our best to support ZKsync and its ecosystem.

[cobinus]

I oppose reallocating the remaining 5.8M ZK from TPP-8 to a single existing vendor.

Here is why this proposal is fundamentally flawed:

• Closed Ecosystem Loop: Treasury and TPP allocations continue to circulate among the exact same small circle of contributors. This is no longer community activation; it is an exclusive retainer.

• Holder Dilution vs. Real Community ROI: Long-term token holders bear the true cost of these token allocations. Instead of funding centralized retainers, these resources should incentivize and empower the actual community to create content, drive genuine engagement, and scale grassroots awareness.

• Content Fatigue & Declining Impact: Both the official ZKsync channels and ZKnomist have suffered from diminishing narrative appeal and engagement fatigue. Running standard weekly roundups and repetitive formats from the same accounts does not expand our reach beyond the existing bubble.

• Need for Decentralized Outreach: Growth requires fresh perspectives, diverse creators, and open bounty models. Relying on a single entity creates a bottleneck and prevents organic community participation.

The remaining TPP-8 funds should either be returned to the Token Governor Timelock or restructured into an open, competitive creator program that genuinely rewards active holders and builders.

[Axia]

Axia recognizes ZKnomist’s demonstrated delivery and supports maintaining effective ecosystem communications. However, the proposed allocation repurposes the remaining Community RFP Pilot balance—originally intended for a competitive, open workstream—to continue funding an existing provider. Axia would be open to support a shorter, clearly defined continuation with a review point, while preserving the remaining balance for a targeted open RFP or returning it to the Token Governor Timelock.

[Manugotsuka]

The following reflects the views of L2BEAT’s governance team, composed of @kaereste and @Manugotsuka, and is based on their combined research, fact-checking, and discussion.

We voted FOR.

We support this proposal because ZKnomist has already been doing this work under TPP-8 and has shown that it can execute consistently. The Season 2 report shows a strong amount of content, community activity, case studies, and ecosystem coverage, which is broadly the type of work ZKnomist was originally funded to provide.

The part we looked at most closely was the source of the funds. ZKnomist was originally funded under the Existing Community Initiatives workstream, while the remaining balance now being requested comes from the Community RFP Pilot. Since that RFP workstream was meant for competitive funding opportunities, we do not think redirecting part of it to one provider should be treated as automatic.

That said, the RFP Pilot was administered by the ZKsync Foundation, and the funds are already sitting in the program multisig. Given that there have not been many new RFPs recently, we think it is reasonable for the Token Assembly to decide whether this remaining balance should be used to continue a workstream that has already shown results.

We also appreciate that this is structured as a ceiling, not an upfront commitment. Payments are expected to happen monthly based on services delivered, and any unused ZK should go back to the Token Governor Timelock.

For these reasons, we voted FOR. This is not a new funding request, the work fits the goals of TPP-8, and the proposal asks for explicit approval before using remaining RFP funds for ZKnomist.