404 Gov Delegate Communication Thread

Delegates
1

Name: 404 Gov

Delegate Address: 0xE93D59CC0bcECFD4ac204827eF67c5266079E2b5

Delegate ENS: 404gov.eth

Forum Username: @404Gov

Tally Profile: https://www.tally.xyz/profile/404gov.eth

About 404 Gov:

404 Gov is a leading delegate across the Ethereum ecosystem. We actively contribute to many top protocols, including Uniswap, Arbitrum, Optimism, and Wormhole. Our team is dedicated to promoting sustainable governance practices, growth, and decentralization.

Our experience includes active participation in various working groups and councils/committees, including Arbitrum LTIPP, Optimism ACC, Arbitrum Onboarding Lead, and Arbitrum MSS.

Our Team:

404 Gov is led by Cole Schendl and Rika Goldberg. Other governance team members include 0xManny, 0xTraub, Kaleb Rasmussen, and Ryan Demattia. Our team possesses a diverse range of technical and non-technical skills, from analytics and business development to cybersecurity and MEV. You can learn more about our team here.

Disclosure of Conflicts of Interest:

404 Gov is an active delegate in Arbitrum, Optimism, Uniswap, Scroll, Morpho, NEAR, Rootstock and Wormhole. When necessary, we will disclose conflicts of interest and abstain from voting.

6 Likes
2

Sounds like a good idea. I would support this proposal

2 Likes
3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

5

Rationale for Votes

  1. [TPP-001] ZKsync Ignite Program: Creating a Liquidity Hub for ZKsync

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR TPP-001 to fund the Ignite Program. We support initiatives that drive liquidity and asset growth on ZKsync and have confidence in the team and their approach.
      Allocating 300M ZK tokens over nine months is a strategic and reasonable investment to attract liquidity and strengthen the Era chain’s market presence. The program’s design focuses on foundational infrastructure by targeting essential trading pairs and key asset pools, ensuring long-term sustainability.
      Moreover, the Ignite Program incorporates critical elements often overlooked in incentive structures, including a dedicated marketing agency and built-in iteration cycles to refine strategies over time. We are excited to see Ignite play a pivotal role in kickstarting ecosystem incentives for ZKsync.

  2. [ZIP-001] Protocol Defense

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR on ZIP-001, Protocol Defense, to implement a set of code quality improvements and optimizations for ZKsync Era. We support quality of life improvements that optimize security and are aligned with best practices in the Ethereum ecosystem.

  3. [ZIP-002] Reduce the execution delay from 21 hours to 3 hours

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR on ZIP-002, to reduce the execution delay from 21 hours to 3 hours. Given the Security Council’s ability to initiate a soft freeze for 12 hours along with all council members under time-based SLA to address any potential issues leads us to support the execution delay decrease to 3 hours.

  4. [ZIP-003] Resubmission of Protocol Defense

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR on ZIP-003, Resubmission of Protocol Defense. We understand that this resubmission of ZIP-001 was requested by the Security Council due to an error in the upgrade message sent from ZKsync Era to the L1.

  5. [GAP-1] ZKsync Token Program Priorities 2025 Endorsement

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR on GAP-1 to endorse the Token Assembly’s 2025 ZK token allocation priorities. Establishing clear strategic priorities for evaluating Token Program Proposals is essential for the Token Assembly to allocate funds effectively and drive informed decision-making. We support the focus on accelerating ZKsync development, establishing a network of ZK chains, and positioning ZKsync as the home for elastic applications.

  6. [ZIP-4] Reduce the execution delay from 21 hours to 3 hours

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR on ZIP-004, Reduce the execution delay from 21 hours to 3 hours. We understand that similar to the resubmission of ZIP-003, this resubmission of ZIP-004 was requested by the Security Council due to an error in the upgrade message sent from ZKsync Era to the L1.

  7. [GAP-2] Adopt The SEAL Safe Harbor Agreement

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR this proposal. We support initiatives that enhance protocol security and protect user funds. Specifically, this proposal covers possible fund recovery during active exploits, a critical area not covered in ZKsync’s Bug Bounty Program.

  8. AAVE DAO Airdrop Claim Extension Request

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR this proposal to establish a new capped minter, ensuring that Aave users on ZKsync can claim their allotted airdrop tokens. Given the technical complexities involved in the original claims process, an extension is both necessary and justified. Furthermore, we support this extension because of Aave DAO’s commitment to utilizing the claimed tokens for user incentives on ZKsync, as well as to foster cross-protocol collaborations, strengthening Aave’s presence in the ZKsync ecosystem.
6

  1. [ZIP-5] Upgrade Governance Contracts

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR this proposal to upgrade governance contracts. Decreasing the initial voting delay from 7 to 3 days and quorum extension from 7 to 2 days will increase execution and implementation timelines for the DAO. Overall, we support initiatives that enhance governance systems, specifically those that streamline governance activities.

  2. [ZIP-6] Prepare ZKsync for ZK Gateway

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR this proposal to prepare the ZKsync protocol for the upcoming ZK Gateway upgrade. We understand this proposal will support development customizations specifically around Elastic network chain support.

  3. [ZIP-7] Lens Chain inclusion on Elastic Network

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR this proposal to include Lens Chain on the Elastic Network. As a thriving protocol, we are excited that Lens chose to migrate from Polygon to ZKSync. We appreciate the team’s commitment to a seamless transition while preserving users’ existing Lens profiles and their inclusion of block 0 specifications.

  4. [ZIP-8] Upgrade Chain Creation Params

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR this proposal to update the chain creation parameters for new chains. This is an important upgrade that will unblock the creation of new chains after the ZIP-6 upgrade.
7

  1. [ZIP-9] V27 EVM Emulation Upgrade

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR this proposal to enable the direct deployment and execution of EVM contracts on ZKsync without recompilation. This is an important upgrade that will improve the developer experience and improve security.

  2. [GAP-3]

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: 4. We voted FOR this proposal to authorize the ZKsync Security Council to convert ETH, recovered from the April 2025 exploit of unclaimed airdrop tokens, back into ZK tokens. We support the Security Council executing its authority to convert the recovered ETH into ZK tokens.

  3. [TPP-3] ZIP Audit Reimbursement Program (ZARP)

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR this proposal to to reimburse security audit costs for successfully executed ZKsync Improvement Proposals (ZIPs) in 2025. We support proposals that enhance security and providing reimbursements for audits, a costly expense for projects, is a prudent use of the DAO’s funds.

  4. [TPP-4] Deactivate Capped Minters for TPP-1 Ignite Program

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR this proposal to removes the minter role from all Ignite Program capped minters since the Ignite Program has concluded.

  5. [ZIP-10] Activate ZK Gateway as a Settlement Layer

    1. Proposal: Tally | ZKsync | [ZIP-10] Activate ZK Gateway as a Settlement Layer
    2. Vote: FOR
    3. Reasoning: We voted FOR this proposal to whitelist ZK Gateway chain as a settlement layer for the Elastic Network. We understand that this proposal will optimize pricing for ZK Chains by enabling them to receive more stable batch settling pricing, while allowing prices that are much cheaper than L1.

  6. [ZIP-11] V28 Precompile Upgrade

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR this proposal to implement key Ethereum precompiles directly in ZkVM. We support proposals that improve performance and reduce gas costs.

  7. [TPP-5] ZKsync Security Council Bridge Funding

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR this proposal to fund the operations of the ZKsync Security Council for June and July. The Security Council plays a pivotal role in the DAO and after deliberation, we think it makes sense to approve this funding given the SC’s current SLA structure.

  8. [TPP-6] ZKsync Security Council v2 Funding

    1. Proposal: Link
    2. Vote: FOR
    3. Reasoning: We voted FOR this proposal to fund 12 months of ZKsync Security Council operations. This proposal is an improvement over the previous structure and we support the 53% budget reduction.

  9. [TPP-7] ZKsync Guardians Funding 2024-2026

    1. Proposal: Link
    2. Vote: FOR
    3. We voted FOR this proposal to to fund the compensation of ZKsync Guardians for 2 years from the governance launch in September 2024 through to September 2026. After deliberation, we decided to support this proposal as it provides the necessary retro compensation for Guardians and includes runway.
8
  1. [TPP-8] ZKsync Community Activation Pilot Program (2025–2026)
    1. Proposal: Link
    2. Vote: FOR
    3. We voted FOR this proposal to to fund three existing community initiatives and a Community RFP Pilot. We support using Treasury funds to support educational initiatives, both existing ones that have already shown traction and success, and new ones by qualified service providers. We are confident in the ZKSync Foundation to oversee strategy and approve funding for these initiatives.
9
  1. [TPP-9] ZKsync Prividium Prize
    1. Proposal: Link
    2. Vote: FOR
    3. Rationale: We voted FOR the ZKsync Prividium Prize Proposal. The timing of this proposal is opportune and should support Prividium strategy and acquisition efforts. Additionally, we are happy with the design of the eligibility requirements to receive rewards as well as the capped minter limits and structure. We look forward to future updates regarding Institutions adopting Prividium.
10

  1. [TPP-9] ZKsync Prividium Roadshow
    1.Proposal: Link
    2.Vote: FOR
    3.Rationale: We voted FOR the ZKsync Prividium Roadshow to allocate $25M ZK to secure sponsorships, speaker opportunities, and institutional networking. We are supportive of Prividium and understand the need to allocate funds to activities that will enhance its traction and adoption amongst enterprises.

  2. [ZIP-12] V29 Interop Messaging Upgrade
    1.Proposal: Link
    2.Vote: FOR
    3.Rationale: We voted FOR the V29 Upgrade which introduces interop messaging for ZKchains. We are supportive of this upgrade which paves the way for advanced interoperability features.

  3. [ZIP-13] Adding a ZKsync OS CTM
    1.Proposal: Link
    2.Vote: FOR
    3.Rationale: We voted FOR adding a ZKsync OS–based ChainTypeManager (CTM). This is an exciting upgrade towards adoption of ZKSync OS which will enable chains to have full EVM equivalence.

  4. [TPP-11] ZKsync Governance System Infrastructure Funding
    1.Proposal: Link
    2.Vote: FOR
    3.Rationale: We voted FOR this proposal to fund the ZKsync Association with 33M ZK in services to maintain and evolve the governance infrastructure. We understand this funding is critical for executing protocol upgrades, token programs, and network coordination through December 2026.

  5. [TPP-12] ZKnomics Token Staking
    1.Proposal: Link
    2.Vote: FOR
    3.Rationale: We voted FOR this proposal to activate a capped minter with 37.5M ZK (~$1.9M USD at $0.05/ZK) to trial ZK token staking rewards. We are supportive of staking as it aligns the interests of governance stakeholders and enhances security.