Delegate Profile/Address: boardroomgov.eth (Profile) (History)
Forum Handle: @boardroom
Twitter: @boardroom_info
Introduction
Proxy is a team of governance and DAO contributors with over four years of experience building governance infrastructure for decentralized protocols. We’ve worked with over 350 DAOs and protocols, providing tools and insights that improve transparency, efficiency, and stakeholder engagement.
Our team has been closely following ZKsync’s evolution and is deeply aligned with its mission to advance Ethereum scaling and the zk-rollup ecosystem. We bring hands-on experience in governance tooling, delegation, and facilitating data-driven decisions. We aim to support ZKsync with a long-term commitment to fostering a healthy and transparent governance ecosystem, aligning our expertise with the DAO’s vision.
Our past contributions across DAOs include building delegate dashboards, designing performance metrics, and helping refine grant processes to ensure resources are deployed efficiently. We’re excited to bring this experience to ZKsync governance and contribute to its next growth phase.
Core Values
- Efficiency: Governance should be impactful, not cumbersome. We prioritize decisions that ensure financial or operational resources are deployed efficiently to support ZKsync’s long-term growth.
- Transparency: We believe in clear and accessible communication. Every vote we participate in will include detailed reasoning, and we’ll actively demand the same from proposals to ensure all stakeholders have the information they need to make informed decisions.
- Accountability: Governance doesn’t end with a vote. We are committed to ensuring that DAO-approved actions are tracked, evaluated, and adjusted as needed. Whether it’s a grant program or new initiatives, we’ll work to set up channels that ensure accountability for all outcomes.
Conflicts of Interest
Proxy actively participates in governance for other DAOs, including Optimism, Moonwell, and others. If any potential conflicts of interest arise in ZKsync governance, we will abstain from voting and disclose the conflict transparently on the forums.
[ZIP-001] Protocol Defense
Voting “yes” ensures ZKsync Era remains efficient, secure, and aligned with industry standards through improved gas usage, stricter code quality rules, and enhanced compatibility. These changes reduce user costs, simplify developers’ debugging, and future-proof the protocol. With a thorough audit confirming no critical vulnerabilities, this proposal strengthens the ecosystem with minimal risk.
[GAP-1] ZKsync Token Program Priorities 2025 Endorsement
We voted For: The proposal provides a clear strategic direction for token allocation focused on protocol development, network growth, and app ecosystem - all critical for ZKSync’s evolution. The flexible nature of these priorities allows for community adjustments as needed.
[ZIP-4] Reduce the execution delay from 21 hours to 3 hours
We voted For: The proposal strikes the right balance between improved efficiency and security safeguards. With the Security Council now in place to provide emergency oversight, the shorter 3-hour window is sufficient for detecting and responding to critical issues while dramatically improving user transaction finality. The technical implementation is sound, with clear parameter updates and testing plans.
[GAP-2] Adopt The SEAL Safe Harbor Agreement
We voted For: This critical governance upgrade strengthens ZKSync’s security posture by empowering whitehat hackers to protect user funds during active exploits. The agreement provides clear legal protection and incentives for security experts while maintaining strict guidelines for intervention. The 72-hour return requirement and predefined bounty structure create the right balance of urgency and accountability. This type of proactive security framework is exactly what responsible governance should prioritize.
AAVE DAO Airdrop Claim Extension Request
We voted For: The request for a capped minter of 8.3M ZK tokens is well-structured with clear accountability measures. Key positive elements: 1) The fixed 6-month timeframe with explicit start/end dates 2) A robust 3/5 multisig with reputable accountability partners 3) Strict limitation that tokens can only be used for user incentives, not operational costs 4) Clear alignment with growing ZKSync ecosystem adoption. The technical implementation via the Capped Minter V2 provides appropriate safeguards.
Proposal: Upgrade Governance Contracts
Vote: For
Rationale: We’re in favor of upgrading the governance contracts. We don’t see any issue with reducing the ZIP voting delay to three days and reducing the quorum extension to three days. The other actions like redeploying ProtocolUpgradeHandler are standard upgrades and we see no need to oppose them.
Proposal: Prepare ZKsync for ZK Gateway
Vote: For
Rationale: As a preemptive measure before a ZK Gateway deployment proposal, we’re in favor of aligning existing contracts with ZK Gateway’s requirements.
Proposal: [ZIP-7] Lens Chain inclusion on Elastic Network
Vote: For
Rationale: We voted in favor of the proposal. The ZIP draft is very well-structured and clear and we’re excited about the opportunity surrounding seamless integration for users at launch.
Proposal: [ZIP-8] Upgrade Chain Creation Params
Vote: For
Rationale: We recognize that, due to a configuration issue, chain initialization became impossible after the ZIP-6 upgrade. ZIP-8 seeks to resolve it and we see no outstanding reasons to oppose its implementation.
Proposal: [ZIP-9] V27 EVM Emulation Upgrade
Vote: For
Rationale: We voted in support of the V27 upgrade. The EVM emulation improves developer experience and ecosystem compatibility which is critical for adoption, the Fflonk verifier’s 30% cost reduction provides clear user benefits, and the security approach with multiple audits is thorough. The proposal demonstrates strong technical preparation while being transparent about tradeoffs.
1 Like