Ignas - Delegate Communication Thread

1. Basic Info

  • Name: Ignas
  • Delegate Address: ignasdefi.eth | 0x3DDC7d25c7a1dc381443e491Bbf1Caa8928A05B0
  • X (Twitter): x.com
  • Telegram: @ignasdefi
  • Website: https://pinkbrains.io/

2. Intro

I’m Ignas, a solo researcher with the main focus on DeFi. My mission is to provide clear, in-depth insights helping my audiences stay up-to-date with the latest trends while actively supporting DAO development.

I believe in the decentralized future and it means actively participating in zkSync DAO in every way I can—whether it’s by serving as a delegate, joining working groups, discussing any proposals or seizing new opportunities that come up. I’ll also be sharing key DAO decisions on X and my blog.

3. Delegate Communication Intent

I’m committed to keeping the zkSync community informed with regular, transparent updates. I’ll provide clear insights into my voting choices and reasoning to ensure everyone understands the direction we’re headed and why.

4. Why I Want to be a Delegate
Currently, DeFi DAOs face several internal issues, such as voter apathy leading to governance attacks, insider voting, and voting concentration among a few active voting addresses. Additionally, they face external challenges like regulatory uncertainty.

I believe in a decentralized future, even if it seems naive. However, the current state of crypto is plagued by misaligned incentives that prioritize short-term speculative gains over the core DeFi values of self-sovereignty and custody.

Equally concerning is the trend of McKinsification in DAOs, where decisions are increasingly made by one or two professional consultant delegates. This discourages individual participation, as their opinions and votes have less impact.

To make DeFi DAOs viable, we must align incentives to encourage active participation in governance from the broader crypto community. I believe that community must be at the core of every DAO. Without giving the community a say in protocol governance, we’re no better than the Web2 companies we aim to replace—companies that view their “community” merely as users to extract value from.

I will support initiatives that align token holders with the protocol, such as revenue sharing or other methods to bring value to the token. Token holders are frustrated with exploitative tokenomics that only benefit early insiders who acquired tokens at much lower prices, leaving no upside for new investors. Without incentives to buy and hold tokens, the attractiveness and health of DAOs decline.
As mentioned, I will highlight key votes and decisions of the DAO on X and my blog, as I believe the general public is often unaware of important actions being taken.

5. Disclosure

I am the co-founder of Pink Brains, an organization dedicated to promoting various crypto projects through educational content. You can find more info about us here: pinkbrains | Twitter | Linktree.

I’m a delegate for Lido, Instadapp, Arbitrum, Aave, Uniswap, Optimism Collective,… I plan to apply as a delegate to other DAOs soon, with the same mission of strengthening them and aligning token holders with the protocol.

I always make appropriate disclosures and recuse myself from voting when necessary.

6. Delegation

If anyone would like to delegate to me, please use the following address: 0x3DDC7d25c7a1dc381443e491Bbf1Caa8928A05B0

2 Likes

1. Proposal: [ZIP-001] Protocol Defense (Tally)

  • Date Voted: November 26, 2024
  • Vote: For
  • Rationale: Thanks for sharing this in an easy-to-understand way. I’ve voted yes because I believe this proposal will have a positive impact on both the short-term and long-term success of the protocol. For example, by improving gas efficiency, ZKsync will become more attractive compared to other L2, which could bring in more users and enhance their overall experience.

2. Proposal: [ZIP-002] Reduce the execution delay from 21 hours to 3 hours (Tally)

  • Date Voted: December 3, 2024
  • Vote: For
  • Rationale: I believe this change will definitely improve the user experience. Faster transactions make ZKsync more attracting to users. No reason to block it so voted For

3. Proposal: [ZIP-003] Resubmission of Protocol Defense (Tally)

  • Date Voted: December 17, 2024
  • Vote: For
  • Rationale: These changes will definitely make ZKsync stand out compared to older versions. Voted For on Tally!

4. Proposal: [GAP-1] ZKsync Token Program Priorities 2025 Endorsement (Tally)

  • Date Voted: January 16, 2025
  • Vote: For
  • Rationale: Voting yes, absolutely. Passing this proposal will boost ZKsync’s tech, network, and ecosystem while strengthening their competitive edge in the blockchain space.

5. Proposal: [ZIP-4] Reduce the execution delay from 21 hours to 3 hours (Tally)

  • Date Voted: January 17, 2025
  • Vote: For
  • Rationale: Same as the previous vote. I believe this change will definitely improve the user experience. Faster transactions make ZKsync more attracting to users. So voted For

6. Proposal: [GAP-2] Adopt The SEAL Safe Harbor Agreement (Tally)

  • Date Voted: January 20, 2025
  • Vote: For
  • Rationale: Security is the top priority. Voting yes :slightly_smiling_face:. This proposal helps ZKsync respond faster and better to potential attacks or vulnerabilities.

7. Proposal: AAVE DAO Airdrop Claim Extension Request (Tally)

  • Date Voted: January 22, 2025
  • Vote: For
  • Rationale: Voted yes. This proposal makes sense to me.

Date Voted: February 19, 2025

8. Proposal: Upgrade Governance Contracts (Tally)

  • Vote: For
  • Rationale: Voted yes since all changes make sense to me. These updates help the system react faster to community needs.

9. Proposal: Prepare ZKsync for ZK Gateway (Tally)

  • Vote: For

  • Rationale: Clear and well structured proposal. I voted yes.

    This sets up ZKsync for better interoperability, smoother bridging, and more flexible data options

10. Proposal: [ZIP-7] Lens Chain inclusion on Elastic Network (Tally)

  • Date Voted: March 4, 2025
  • Vote: For
  • Rationale: It’s an easy yes from me. We need more consumer apps like Lens. It will expand the Elastic Network, keeps user experience smooth and ensures security and transparency in the data migration process :slightly_smiling_face:

11. Proposal: [ZIP-8] Upgrade Chain Creation Params (Tally)

  • Date Voted: March 10, 2025
  • Vote: For
  • Rationale: Voted yes since this proposal allows zkSync to continue expanding its network by enabling new chain creation while also enhancing the stability and reliability of contract deployment.

12. Proposal: [ZIP-9] V27 EVM Emulation Upgrade (Tally)

  • Date Voted: April 14, 2025

  • Vote: For

  • Rationale: I’m voting For. This proposal can make it easier for EVM builders to launch on ZKsync, which means more dApps, more users, and more TVL to the ecosystem :slight_smile:

    I also appreciate the clear audits and transparency, we will see more Ethereum-native apps growing here.

13. Proposal: [GAP-3] Authorization for Security Council to Convert Recovered ETH into ZK (Tally)

  • Date Voted: May 9, 2025

  • Vote: For

  • Rationale: This is a strong step toward restoring trust after the exploit.

    Converting the recovered ETH back to ZK and putting it under DAO control shows ZKsync is serious about transparency and real community governance.

    Voted yes!

Date Voted: May 16, 2025

14. Proposal: [TPP-4] Deactivate Capped Minters for TPP-1 Ignite Program (Tally)

  • Vote: For

  • Rationale: Taking away the minting rights from these capped minters will stop any uncontrolled token printing and help prevent unwanted inflation.

    Good action to protect the token’s value, enhance security, and maintain transparent governance. Voted in favor!

  1. Proposal: [TPP-3] ZIP Audit Reimbursement Program (ZARP) (Tally)
  • Vote: For

  • Rationale: I vote YES to support the ZIP Audit Reimbursement Program.

    This proposal will make zkSync more secure by encouraging SP to do proper audits before launching upgrades.

    Reimbursing the audit cost can give teams a good reason to focus on safety and avoid vulnerabilities and potential exploits.

Date Voted: May 20, 2025

16. Proposal: [ZIP-11] V28 Precompile Upgrade (Tally)

  • Vote: For

  • Rationale: I believe this upgrade is an important step. By moving complex math operations into the zkEVM circuit, it makes onchain cryptography much faster and cheaper.

    It also keeps things compatible and has been fully audited.

    Support the proposal!

17. Proposal: [ZIP-10] Activate ZK Gateway as a Settlement Layer (Tally)

  • Vote: For
  • Rationale: Voting yes on ZIP-10. This proposal will unlock cheaper and more predictable settlement for ZK Chains while preserving optionality and Ethereum-level security

18. Proposal: [TPP-5] ZKsync Security Council Bridge Funding (Tally)

  • Date Voted: July 15, 2025

  • Vote: For

  • Rationale: I am voting Yes as this proposal provides essential short term funding to ensure the uninterrupted operation of the ZKsync Security Council.

    Sustaining protocol security during this interim period is both prudent and necessary.

19. Proposal: [TPP-6] ZKsync Security Council v2 Funding (Tally)

  • Date Voted: August 11, 2025
  • Vote: Yes
  • Rationale: Support this proposal. It can ensure the ZKsync Security Council remain fully funded and operational for the next 12 months while significantly reducing costs by over 50% compared to the previous term.

20. Proposal: [TPP-7] ZKsync Guardians Funding 2024-2026 (Tally)

  • Vote: Yes

  • Rationale: This is a reasonable funding request.

    I support this proposal as it secures long term funding for the Guardians, ensuring they can continue to protect the protocol’s security and neutrality while providing reliable oversight for the ZKsync ecosystem.

21. Proposal: [TPP-8] ZKsync Community Activation Pilot Program (2025–2026) (Tally)

  • Date voted: September 18, 2025

  • Vote: Yes

  • Rationale: Support the program.

    This program uses tokens that are already minted, so the real cost to the DAO is low, while the potential impact on adoption ahead of upcoming chain launches and Prividium is high.

    That said, I believe we should strengthen governance oversight and execution controls before unlocking the full 20M ZK allocation.

22. Proposal: [TPP-9] ZKsync Prividium Prize (Tally)

  • Date Voted: September 22, 2025
  • Vote: Yes
  • Rationale: I voted yes. This program is a good way to bootstrap Prividium adoption while keeping incentives aligned through milestone based rewards and rate limited minting.