Axia Network — Delegate Communications Thread

Shutter DAO 0x36 SD 0x36 Delegates
1

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.

Tally Profile: Tally | Axia Network

Follow Axia on X: X | Axia Network

1 Like
2

Provide a grant to brainbot gmbh (June 2026)

Rationale: Axia voted FOR a $107,000 grant to brainbot gmbh, for June, to continue advancing the Shutter ecosystem. Going forward, since brainbot gmbh has been requesting these funds from the DAO on a monthly basis, Axia would like to see increased transparency and accountability around how the captail was spent and the outcomes.

2 Likes
3

Keyper Compensation Program — Renewal (6 months)

Rationale: Axia voted FOR because the first six months appear to validate the basic thesis that modest, standards-based compensation improved Keyper uptime and communication without creating a large budget burden.

The renewal keeps the important controls in place: 90% uptime, open communication, monthly review, and periodic DAO payouts, while shifting payment to SHU, which better aligns Keypers with Shutter’s long-term success.

Provide a grant to brainbot gmbh (July 2026)

Rationale: Axia voted For because brainbot remains a core contributor to Shutter’s research, development, and ecosystem work, and the follow-up context helped clarify the request.

The added breakdown across workstreams, FTE focus areas, and cost categories gives delegates a better basis for judging whether the $107k request is reasonable.

We also appreciated the clarification that the current priorities are tracked on a trimester basis, with most items either complete or on track and none currently marked as not achievable. For recurring DAO support, that kind of light-touch reporting is important.

We support continuing funding here, while encouraging brainbot to keep connecting monthly updates back to funded priority areas so the DAO can track progress and treasury use over time.

2 Likes
4

TEMP CHECK: Migration to a New Onchain Governance Platform

Vote

#1 Cactus → # 2 Anticapture → #3 Snapshot X

Rationale

Axia voted Cactus first, with a disclosed COI related to Cactus.

Cactus put forward the clearest migration proposal, including a concrete path to modern OpenZeppelin Governor contracts, support for the existing SHU token, migration/testing steps, and ongoing frontend support. Given that governance execution is critical infrastructure for the DAO, Axia preferred the option with the most explicit implementation plan and lowest ambiguity around what the DAO is approving.

Axia ranked Anticapture second because it is already live, requires the least migration effort, and can support the current governance contracts. However, Axia still has concerns about tying ongoing maintenance/support to approval of a separate retroactive security grant for work the DAO did not request in advance. This should be clarified before the onchain vote.

Axia ranked Snapshot X third because, while Snapshot is a credible governance provider and important partner to Shutter, there was minimal information publicly available on the full cost, scope, or implementation path.

Since this was a temperature check, Axia would like to see more detail from each provider before any onchain vote, including implementation scope, cost, support terms, SLA, migration risk, and long-term maintenance expectations.

TEMP CHECK: Migration to a New Onchain Governance Platform

Vote: No

Axia agrees that Shutter DAO 0x36 should be thinking about runway, treasury composition, and how to preserve non-SHU assets over time. However, Axia does not think a discretionary USDC → ETH swap is the right next step while the DAO lacks a clearer legal/entity structure.

The DAO is already deploying USDC into an onchain Steakhouse/Morpho vault, which may be a reasonable treasury action. But the fact that a strategy is onchain does not remove the broader issue: Shutter DAO 0x36 is actively managing treasury assets, and that creates responsibilities and potential risk for the DAO and delegates.

Axia is also cautious about reducing the DAO’s liquid USDC reserves. The DAO needs stable assets on hand to pay grants, service providers, and other operating expenses that my come up. ETH exposure may be useful in some contexts, but it should not come at the expense of near-term payment flexibility or stable runway.

Axia’s concern is less about whether ETH is the right asset and more about structure and sequencing. Before the DAO expands from stablecoin deployment into discretionary asset allocation, it should clarify whether a legal entity is needed to support treasury management, reduce ambiguity for delegates, and expand the DAO’s investment options over time.

A legal/entity structure could also give the DAO more optionality beyond direct onchain actions, including access to additional treasury-management tools and counterparties that may not be available to an unwrapped DAO.

This is not an argument against ETH exposure permanently. Axia would prefer the DAO first address the structure, accountability, and stable reserve questions around treasury management, then evaluate whether ETH exposure is appropriate.

5

Security Bounty for blockful

Vote: Against

Axia appreciates Blockful’s contribution and the importance of responsible disclosure. However, I do not support retroactive payment here because Shutter DAO did not have a bug bounty program, prior work order, or approved mandate for this scope. Paying an unsolicited, self-priced retroactive request would set a difficult precedent for the DAO. I would support creating a formal bug bounty and responsible disclosure policy going forward, and separately evaluating Anticapture as a service if the DAO wants ongoing support.

Provide a grant to brainbot gmbh (August 2026)

Vote: FOR

Axia voted FOR because brainbot remains a core contributor to Shutter’s research, development, ecosystem growth, and operational continuity.

The current proposal identifies the main workstreams brainbot is supporting, including encrypted mempool development, private voting, ecosystem growth, and broader Shutter coordination. Given Shutter’s current stage, continued execution capacity across these areas is important.

Axia supports this grant and encourages brainbot to keep connecting future monthly updates back to the funded priority areas so the DAO can track progress, blockers, and treasury use over time.

6

Migration to a New Onchain Governance Platform

Vote: Snapshot X.

Axia voted for Snapshot X.

Anticapture is already live and useful. It provides a good interface for the DAO’s current governance contracts, and blockful’s work around governance monitoring and security is valuable. However, Anticapture does not resolve the core issue that started this process: Shutter DAO 0x36 is still relying on the Azorius/Decent governance stack.

Decent is winding down support, and Azorius is not meaningfully maintained as a long-term governance system. A new frontend can extend the life of that stack, but it does not remove the underlying maintenance risk. If Shutter stays on Azorius, future fixes, integrations, or governance upgrades may require custom work on an orphaned module.

Snapshot X addresses that issue directly. It moves Shutter DAO 0x36 onto a maintained onchain governance protocol while preserving the existing Safe-based control structure.

For Axia, this vote is not a criticism of Anticapture. It is a decision about where Shutter’s core governance execution should live over the long term. Anticapture can still be valuable as a security and analytics layer, but the primary governance path should move away from Azorius.

For these reasons, Axia has voted for Snapshot X.

7

TEMP CHECK: Retroactive Grant for blockful’s Security Work

Vote: $0

Axia appreciates Blockful raising the issue and believes potential vulnerabilities should be responsibly disclosed promptly. However, Axia does not support retroactive compensation for work that was not requested, scoped, or authorized by Shutter DAO in advance. The appropriate sequence is to disclose an issue, allow the DAO or its designated technical team to assess it, and then agree any additional scope, authorization, and compensation before further work is undertaken.

Shutter did not have a bug-bounty policy, work order, or other agreed framework in place here. The work also concerned the Azorius module, which the DAO is moving away from following Decent’s shutdown and the decision to use Snapshot. That does not negate the value of identifying the issue, but it does affect the case for a large retroactive payment or an ongoing service commitment connected to that module.

The weighted-median vote settled at $50,000, and Axia respects that outcome. Axia would support establishing a formal responsible-disclosure and bug-bounty policy for future findings, with clear scope, severity criteria, and compensation parameters. Any future AntiCapture engagement should be evaluated separately against Shutter’s current governance stack and needs.

8

Provide a grant to brainbot gmbh (September 2026)

Vote: FOR

Axia supports continued funding for brainbot as Shutter’s core research, development, ecosystem, and operational contributor. The August update provides useful evidence of continued work across Keyper operations, encrypted-mempool research, private voting, and ecosystem programs, while also identifying several dependencies outside brainbot’s direct control.

Given the recurring nature of this support, Axia encourages brainbot to continue reporting progress against each priority as completed, progressing, externally blocked, or reprioritized, and to confirm whether the FTE and high-level cost allocation shared in July remains materially unchanged. Clarifying the valuation used for the sUSDS disbursement would also make the treasury request easier to assess.

Keyper Compensation Payout (April-August 2026)

Vote: FOR

Axia supports this payout because it executes an approved, performance-linked compensation program for Keypers that met the 90% uptime and communication standard. The proposal provides a clear recipient-level breakdown for 60 qualifying Keyper-months across 12 operators, totaling $3,000 USDC-equivalent.

Axia supports settling the payout in SHU, consistent with the renewed program. For this and future SHU-denominated payouts, the DAO should document the conversion-rate source and timestamp alongside the transfer amounts so delegates can verify how the USD-equivalent rate was applied.

Add Snapshot X Module to Shutter DAO 0x36 Safe

Vote: FOR

Axia supports adding the Snapshot X module as the first onchain step in Shutter DAO 0x36’s migration away from the retiring Decent/Azorius governance stack. The proposed sequence—add the new module, conduct simulations and live tests, then return for a separate Azorius-removal vote—preserves a parallel-validation period before the legacy execution path is retired.

Before execution, the DAO should publish the Snapshot X space and final module configuration, confirm the module address being authorized, and document the test plan and success criteria. Those details will give delegates a clear record of what execution authority is being added and the basis for the subsequent Azorius-removal decision.

Keyper Compensation Program — Renewal (6 months) - Sept 2026 - Feb 2027

Vote: FOR

Axia supports renewing the Keyper Compensation Program for a further six months. The program remains a modest, performance-linked mechanism for supporting reliable Keyper participation: operators qualify only when they meet the uptime and communication standard, and recent payouts show that compensation adjusts with actual performance rather than operating as a fixed subsidy.

The expected cost is limited and the program has a clear operational purpose. For future SHU-denominated payouts, Axia encourages publication of the price source, timestamp or averaging window, and recipient-level calculations so delegates can verify how each USDC-equivalent amount converts into SHU.