Axia Network is a delegate across DAOs in the EVM ecosystem. Axia is committed to growing alongside the ecosystem and contributing responsibly to each protocol’s long-term success.
Axia’s values emphasize supporting protocols through sustainable long-term growth, education, and strong oversight, while preserving decentralization by creating and sustaining pathways for community participation and meaningful checks and balances that ensure accountability and transparency across governance stakeholders.
Rationale: Voted FOR this proposal to donate 64M ZK to the ZKsync Association in support of its non-profit mandate as issuer of the ZK token. Axia Network recognizes the importance of funding public-goods infrastructure and the Association’s stewardship role. Axia supports this funding to help keep governance functional and resilient over the next 12 months.
[TPP-17] ZKsync Immunefi Bug Bounty Program 2026
Vote: FOR
Rationale: Voted FOR this proposal to approve $1.6M USD in ZK to fund the ZKsync bug bounty program on Immunefi for 2026 and $400k USD in ZK for bug bounty payouts made in 2025. This proposal funds mission-critical protocol security and strengthens a core part of ZKsync’s emergency response framework.
[TPP-16] ZKsync Audit Reimbursement Program 2026 (ZARP v2)
Vote: FOR
Rationale: Voted FOR this proposal to fund the ZKsync bug bounty program on Immunefi with $1,600,000 USD equivalent in ZK tokens for forward-looking bug bounties and $400,000 USD equivalent in ZK tokens in reimbursement to Matter Labs for bug bounty payouts made in 2025. The Audit Reimbursement program is a critical part of ZK’s commitment to protocol security.
Rationale: Voted ABSTAIN. I understand the operational logic behind reducing the size of the Security Council and aligning compensation and thresholds with the current stage of the protocol. However, I am not fully convinced by the broader governance implications of moving to a smaller, entity-only council, particularly when the rationale is tied in part to enterprise preferences rather than decentralization or independence considerations.
This may be a practical change, but I do not think the case has been fully made that it is the strongest governance design choice for the ecosystem long term.
[TPP-18] 2026 ZKsync Protocol & Network Development Allocation
Vote: FOR
Rationale: I understand the concerns around dilution, timing, and current market conditions. 67M ZK per month is not a small ask, and I don’t think the community’s concerns should be brushed aside.
I support this proposal because I see Prividium as an important strategic bet for ZKsync. It is a focused attempt to turn an institutional pipeline into real deployments, usage, and hopefully long-term network activity.
I would like to see the reporting continue improving around pipeline stages. There is a big difference between early conversations, signed agreements, technical integrations, and live production deployments. Delegates should be able to understand where institutional interest is becoming real usage without requiring Matter Labs to disclose commercially sensitive information.
This is where I think ZKsync governance will need to keep improving over time. As the DAO funds more strategically sensitive work, the challenge will be finding the right balance between confidentiality and accountability. Some institutional pipeline information cannot reasonably be made fully public, but delegates still need a way to verify whether claims are supported by real progress.