Cap / thecap.eth - Delegate Communication Thread

Delegates
1

Gm everyone,

Tally: Tally Profile
Delegate address: thecap.eth
X: @thecaphimself
Warpcast: thecap.eth
Telegram: @thecaphimself

About me

I’ve been actively involved in crypto since the early days, and over the past six years, I’ve been focused on building products, investing in good teams, and contributing in DAOs. Before crypto, I founded and grew two successful tech startups. Now, I run Namespace, an official ENS Service Provider, where we help drive the adoption of ENS by doing partnerships, integrations, and building developer tools that make decentralized identities more accessible. My 3 years at ENS DAO have been all about fostering collaboration with ENS and its ecosystem projects, and I hope to bring all of that knowledge and experience to ZKsync Nation.

Vision, Contribution, and Focus

Vision

Much like ZK Nation’s vision of empowering builders, my long-term focus is on cultivating a thriving developer ecosystem on the ZKsync chain. I believe that developer activity is a core metric for a chain’s health and an indicator of its future success.

Contribution

I would like to contribute by creating a supportive environment with grants, resources, and a space where builders, entrepreneurs, and developers can thrive. Whether it’s financial backing, technical help, or simply a place where builders can connect and collaborate, I want to ensure that anyone with a vision has the tools to turn it into reality.

Focus

By focusing on developer support, we’re not just supporting individual projects—we’re strengthening the foundation of the entire chain and creating a culture that reflects our values. By investing in builders, the ecosystem will thrive, and ZKsync will become the go-to place for the biggest talent in Web3 creating cutting-edge apps and innovation.

Decision-making

As a Delegate in governance decision-making, I take a balanced approach, blending community input with data-driven analysis. I believe that decisions should benefit the ZKsync chain and its broader ecosystem and reflect its values. I will actively gather community feedback, and evaluate proposals based on their long-term impact, alignment with our shared goals, and the value they bring to the ecosystem. I want to ensure every voice is heard while keeping governance efficient and forward-looking.

3 Likes
2

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

4

TPP-001 voted FOR

Even though I initially had ‘concerns’ with: the lack of automation, alignment with what TPPs aspire to become, potentially setting a bad precedent for others, lack of details for KPIs and results the incentives would bring, user retention/stickiness, and some others – all of them have been communicated, discussed, addressed and updated in the proposal.

Time to market beats the implementation details and it’s much more important to start generating onchain activity and increasing liquidity than hashing out smaller details of the proposal for which we lack the tools to build them according to our vision.

All in all, the pros of this proposal heavily outweigh the cons, and I’m confident in my vote. The team behind the proposal is competent, professional, and reputable, guaranteeing its execution to be as perfect as possible.

5

ZIP-001 [Protocol Defense] - Voted FOR

I’m not too technical but this proposal clearly contributes to improving the codebase and optimization for the ZKsync Era chain and deserves to be passed.

6

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

Voted: FOR

I see shortening the execution delay from 21 hours to 3 hours as the overall progress of the ZKsync chain, net-positive for the chain and its ecosystem, and getting it closer to the end goal. I don’t see any downside to implementing this especially since the Security Council is now officially formed.

7

[ZIP-003] Resubmission of Protocol Defense

Voted: FOR

This proposal is a resubmission of ZIP-001 which I also voted FOR.

[GAP-1] ZKsync Token Program Priorities 2025 Endorsement

Voted: FOR

The inspiration behind this proposal was derived from the ZKsync Roadmap which I’m fully aligned with! Furthermore, this GAP defines the direction of the ZKsync ecosystem development. It aligns the broader community around the top 3 most important priorities for ZKsync which I believe will establish it as the most dominant L2.

8

[GAP-2] Adopt The SEAL Safe Harbor Agreement

Voted: FOR

I was excited to learn about the SEAL Safe Harbor Agreement. It’s a proactive security measure that allows a rapid response from whitehats to jump in if/when necessary in case of any exploit or security breach, protecting the protocol and user funds.

9

[TPP-2] AAVE DAO Airdrop Claim Extension Request

Voted: FOR

Even though some delegates brought up valid points and concerns around potentially setting the wrong precedent by making an exception for AAVE with this request, I believe this will benefit the end users of ZKsync the most. Therefore I believe it’s important for the ZKsync ecosystem and its users.