404 Gov Delegate Communication Thread

Delegates
1

Name: 404 Gov

Delegate Address: 0xE93D59CC0bcECFD4ac204827eF67c5266079E2b5

Delegate ENS: 404gov.eth

Forum Username: @404Gov

Tally Profile: 404 Gov's Delegate Profile

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, 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.