Curia - Delegate Communication Thread

Delegates
1

Curia Delegate Platform

Key Information

About Us

Curia Lab is a team of seasoned DAO governance researchers, data analysts, blockchain engineers, and developers. We are committed to strengthening the DAO ecosystem through specialized tools, insights, and delegate services.

Our Mission & Vision

Curia Lab is dedicated to empowering DAOs with robust, data-driven tools, ensuring transparency and efficiency in governance processes. Our mission extends beyond tool creation; we actively engage in DAO governance as a professional delegate, leveraging our hands-on experience to refine our toolings for each DAO. This commitment to being part of the governance process ensures that our tools are battle-tested and evolved, addressing the challenges of data inaccessibility, opaque delegate actions, and governance risk assessments with precision and relevance.

Our vision is a future where the governance of DAOs is seamless, fully transparent, and informed by comprehensive data. We aspire to create an ecosystem where the influence of delegates is clear and their contributions are measurable, enabling real-time monitoring and strategic enhancement of DAO operations. We see Curia Lab at the forefront, leading DAOs into an era where every decision is strategic and data-driven, ensuring a resilient and dynamic governance model.

Our Goal for ZKsync

Curia Lab aims to support ZKsync’s vision of scalable, secure, and decentralization through our expertise in data-driven governance. Our dedication to advancing the DAO ecosystem motivates us to contribute actively to ZKsync, leveraging our deep involvement in DAO governance to enhance decision-making and transparency. With our team’s comprehensive skills in research, data analysis, and blockchain development, we’re excited to be contributing to ZKsync’s growth and progressive decentralization.

Disclosure

As a governance and DAO research team, we work with several other projects and DAOs, such as SafeDAO, Optimism Collective, and ArbitrumDAO, to enhance their governance and decision-making processes. We are committed to maintaining transparency and avoiding conflicts of interest in our work with the ZKsync community. When required, we will disclose any potential conflicts of interest that may arise in the course of our engagement.

Waiver of Liability

By delegating to Curia, you acknowledge and agree that Curia will participate in ZKsync governance on a best-effort basis and will not be liable for any form of damages related to participation in ZKsync.

4 Likes
2

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

4

Proposal: [TPP-2] AAVE DAO Airdrop Claim Extension Request

Vote: For

Rationale: We’re in favor of this proposal since the reasoning makes sense, and the amount requested is in line with what’s already being allocated. Plus, @ACI has shared plenty of details, so we have no concerns!

5

Proposal: [ZIP-5] Upgrade Governance Contracts

Vote: For

Rationale: We are voting in support of ZIP-5 as it introduces a crucial set of upgrades that enhance both the efficiency and long-term viability of ZKsync’s governance. Reducing the voting and quorum extension periods to 3 days will enable the DAO to operate with greater agility and responsiveness to the community’s needs. In addtion, transitioning to an upgradable contract is a necessary and forward-thinking measure that future-proofs our governance system.

Proposal: [ZIP-6] Prepare ZKsync for ZK Gateway

Vote: For

Rationale: We are voting in support of ZIP-6 as it represents a prudent and strategic approach to evolving the ZKsync protocol. By separating the preparatory work from the future deployment of ZK Gateway, this proposal significantly de-risks and simplifies a critical upcoming network upgrade. These enhancements empower individual ZK Chains with greater flexibility and improve the developer experience, making this a vital step forward for the growth, customization, and long-term adaptability of the entire Elastic Network.

Proposal: [ZIP-7] Lens Chain inclusion on Elastic Network

Vote: For

Rationale: We will support this proposal because it delivers a seamless, automated migration of Lens V2 data to the new Lens Chain on the Elastic Network, ensuring that users retain their profiles and content without disruption.

Proposal: [ZIP-8] Upgrade Chain Creation Params

Vote: For

Rationale: We will support this proposal because it makes zkSync stronger by ensuring new chains start with reliable, consistent settings. By fixing the compilation discrepancies, unblocking chain creation after ZIP6, correcting token naming, and adding a securely reviewed L1GenesisUpgrade contract, this change helps the system grow smoothly without impacting existing chains.

6

Proposal: [ZIP-9] V27 EVM Emulation Upgrade

Vote: For

Rationale: We support ZIP-9 because it makes ZKsync much easier to build on by adding full EVM compatibility, so developers can use existing contracts and tools without any changes.

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

Vote: For

Rationale: We are voting For on this essential housekeeping proposal. Since the Ignite program is now complete, deactivating its minters is a straightforward and necessary security measure to permanently secure the unminted token supply.

Proposal: [GAP-3] Authorization for Security Council to Convert Recovered ETH into ZK

Vote: For

Rationale: We are voting in support of this proposal, as it provides a clear and secure path to conclude the incident recovery process. While our preference, like other delegate mentioned, would be for the DAO to retain the recovered ETH for treasury diversification and future operational needs and potentially avoiding the need to sell ZK later.

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

Vote: For

Rationale: We voting in support of the ZIP Audit Reimbursement Program (ZARP) as it represents a direct and strategic investment in the fundamental security and integrity of the ZKsync protocol. By removing the significant financial barrier of third-party audits, this program powerfully incentivizes all contributors, large and small, to uphold the highest security standards for their proposals.

Proposal: [ZIP-10] Activate ZK Gateway as a Settlement Layer

Vote: For

Rationale: We are voting to approve the activation of ZK Gateway, as it represents a significant and strategic evolution for the entire Elastic Network. By providing an optional shared settlement layer, this proposal immediately offers ZK Chains a path to cheaper and more stable transaction costs, a direct benefit that will be passed on to end-users.

Proposal: [ZIP-11] V28 Precompile Upgrade

Vote: For

Rationale: We support the V28 upgrade, as moving key cryptographic functions into native circuits will cut gas costs by up to 94%, making advanced DeFi and privacy applications significantly more viable on our network. While audits highlighted this upgrade’s complexity, the resolution of all initial findings gives me confidence in this well-vetted and strategically vital enhancement for ZKsync.

7

Proposal: [TPP-5] ZKsync Security Council Bridge Funding

Vote: For

Rationale: We vote in favor of this proposal because the Security Council is indispensable for safeguarding the protocol. This temporary, two-month funding is a responsible measure to ensure its operational continuity while a permanent plan is developed. The proposal is strengthened by clear accountability, giving the Token Assembly the power to cancel the funding and requiring public reporting.