Ignas Delegate Platform

Delegate Platforms
161

418. Proposal: weETH E-Mode Risk Parameter Adjustment on Aave V3 Plasma Instance (Onchain)

  • Date Voted: December 15, 2025

  • Vote: For

  • Rationale: Support this proposal to maximize capital efficiency by raising weETH’s E-Mode LTV and LT to align with the Ethereum Core configuration.

    The initial risk discount is now obsolete, Aave V3 Plasma instance exhibits validated market maturity through deep liquidity and low slippage.

162

Date Voted: December 21, 2025

419. Proposal: Remove USDS as collateral and increase RF across all Aave Instances (Onchain)

  • Vote: For

  • Rationale: Voting yes with the same reason on Snapshot vote

    Setting LTV to 0% helps remove unnecessary exposure and increasing RF improves protocol revenue with minimal downside.

420. Proposal: X Layer network aDI path activation (Onchain)

  • Vote: For
  • Rationale: I support taking the required preparatory steps that allow governance actions to be executed reliably across networks.
163

Date Voted: December 22, 2025

421. Proposal: USDG Listing (Onchain)

  • Vote: For

  • Rationale: Maintain my Yes on this. Onboarding USDG brings another trusted, fully backed stablecoin to Aave.

    Paxos has a strong regulatory track record and clear transparency, which helps strengthen user confidence.

422. Proposal: Add WETH to the wrsETH wstETH E-Mode on Aave V3 Base Instance (Onchain)

  • Vote: For
  • Rationale: Voting yes. Adding WETH to the E-Mode increases capital efficiency while keeping risk contained due to strong ETH correlation and E-Mode safeguards.
164

423. Proposal: [ARFC] $AAVE token alignment. Phase 1 - Ownership (Snapshot)

  • Date Voted: December 23, 2025
  • Vote: Abstain
  • Rationale: The proposal was taken to Snapshot too early, I think it makes more sense to bring it back for a vote at a later stage.
165

Date Voted: December 26, 2025

424. Proposal: December Funding Update (Onchain)

  • Vote: For
  • Rationale: This proposal is a practical funding and operations update that keeps the DAO running smoothly without changing strategy or adding new risk. Voted yes!

425. Proposal: Ethena February E-Modes Adjustments (Onchain)

  • Vote: For
  • Rationale: I support this proposal as it improves capital efficiency and reduces friction for users rolling or adjusting PT positions.
166

426. Proposal: [ARFC] Orbit Program Renewal - Q1 and Q2 2026 (Snapshot)

  • Date Voted: December 29, 2025
  • Vote: For
  • Rationale: Happy to continue contributing to the Aave DAO!
1 Like
167

Date Voted: January 10, 2026

427. Proposal: AGRS (Risk Stewards) migration to Risk Agents (Onchain)

  • Vote: For
  • Rationale: Support the adoption of Chaos Risk Agents, which standardize and secure the ingestion of risk data while keeping full DAO control.

428. Proposal: [ARFC ADDENDUM] Updating rules for ARFC and TEMP CHECK Proposals (Snapshot)

  • Vote: For

  • Rationale: Voting yes.

    The proposal introduces a clear consent requirement that strengthens governance integrity and procedural clarity.

    It avoids disputes over whether the author agreed to proceed, encourages more thoughtful, higher quality governance decisions.

168

429. Proposal: Upgrade Aave instances to v3.6 Part 2 (Onchain)

  • Date Voted: January 14, 2026
  • Vote: For
  • Rationale: Support this part 2 upgrade as it completes the v3.6 rollout on Aave’s core and major pools, improving isolation and configurability.
169

Date Voted: January 17, 2026

430. Proposal: [ARFC] Deploy Aave v3 on Mantle (Snapshot)

  • Vote: For
  • Rationale: This proposal will be an opportunity for Aave to expand their reach and user base through Bybit and Mantle. So yes!

431. Proposal: Add WETH to the rsETH LST E-Mode on Aave Core Instance (Onchain)

  • Vote: For

  • Rationale: I support this proposal.

    Allowing WETH borrowing in the rsETH LST E-Mode unlocks standard and well understood looping strategies, which should meaningfully increase WETH borrowing demand on the Core market.

    This also helps improve ETH utilization and protocol revenue while relying on a proven LST and an existing, low risk E-Mode framework.

432. Proposal: stkABPT Emission Update (Onchain)

  • Vote: For

  • Rationale: Voting yes with same reason on Snapshot vote.

    This proposal takes a balanced approach to strengthen Aave’s economics by reducing Safety Module and Umbrella emissions, removing slashing risk, shortening cooldowns, and introducing more efficient liquidity provisioning.

433. Proposal: Upgrade Aave instances to v3.6 Part 3 (Onchain)

  • Vote: For

  • Rationale: This proposal completes the pending Aave v3.6 upgrade on networks that were not executed in Part 2 due to expiry protection

    I support this proposal. It completes the v3.6 rollout across Aave’s core and major pools and improves isolation and configurability.

170

434. Proposal: [ARFC] Onboard Strata srUSDe PT tokens to V3 Core Instance (Snapshot)

  • Date Voted: January 19, 2026

  • Vote: For

  • Rationale: PT-srUSDe is a mature, well-adopted PT asset with clear expiry and conservative risk settings.

    Onboarding it expands high quality collateral options on Aave while maintaining strong risk isolation. Voting yes!

171

435. Proposal: [ARFC] Deploy Aave v3 on Mantle (Snapshot)

  • Date Voted: January 21, 2026
  • Vote: For
  • Rationale: This proposal will be an opportunity for Aave to expand their reach and user base through Bybit and Mantle. So yes!
172

436. Proposal: Onboard syrupUSDC on Base (Onchain)

  • Date Voted: January 22, 2026

  • Vote: For

  • Rationale: Support onboarding syrupUSDC to Aave V3 Base.

    syrupUSDC has already been approved on Core and is onboarded on Base with very conservative risk parameters.

173

437. Proposal: MegaEth aDI path activation (Onchain)

  • Date Voted: January 23, 2026
  • Vote: For
  • Rationale: This is a necessary technical prerequisite to enable cross-chain governance messaging for a future Aave v3 MegaEth activation. Voted yes!
174

Date Voted: January 25, 2026

438. Proposal: [ARFC] Deficit Realization Risk Oracle: Forcing Timely Bad-Debt Recognition via Dust-Collateral Cleanup (Snapshot)

  • Vote: For

  • Rationale: I am voting yes. This proposal improves the protocol’s risk hygiene by ensuring losses are recognized in a timely and consistent way.

    The design is narrowly scoped, budget-capped, and does not subsidize liquidations or change deficit semantics.

439. Proposal: Extend stkAAVE Emissions (Onchain)

  • Vote: For
  • Rationale: This is a simple top up to avoid interrupting stkAAVE rewards. Continuous rewards and operational continuity justify a Yes vote.

440. Proposal: Gho Mantle Activation (Onchain)

  • Vote: For
  • Rationale: This proposal will be an opportunity for Aave to expand their reach and user base through Bybit and Mantle. So yes
3 Likes
175

441. Proposal: [ARFC] Deploy Aave V3 to MegaETH (Snapshot)

  • Vote: Option 1 - Points Program + Revenue Guarantee (with Rollover)
  • Rationale: I support option 1. It offers the same guaranteed minimum revenue and allows excess revenue from strong years to roll forward into weaker periods.

442. Proposal: MKR and USDtb oracle adjustments (Onchain)

  • Vote: For
  • Rationale: This change improves oracle safety for both MKR and USDtb by applying more conservative and reducing unnecessary risk. Voting yes!

443. Proposal: Listing PT Ethena May (Onchain)

  • Vote: For

  • Rationale: Parameters follow a proven setup and keep exposure tightly controlled via E-Mode and oracles.

    This is a clean rollover of existing PT listings to the next expiry. Voted yes!

444. Proposal: Enhancing Market Granularity in Aave v3.6: Part 1 (Onchain)

  • Vote: For

  • Rationale: The proposal uses Aave v3.6’s improved configurability to clearly separate general purpose assets from those better suited for eMode. This is a clean, technical improvement that improves long term market safety.

    So voting yes!

445. Proposal: Onboard Strata srUSDe PT tokens to V3 Core Instance (Onchain)

  • Vote: For
  • Rationale: PT-srUSDe is a mature, well adopted PT asset with clear expiry and conservative risk settings.

446. Proposal: [ARFC] Focussing the Aave V3 Multichain Strategy - Phase 1 (Snapshot)

  • Vote: For

  • Rationale: Freezing underperforming V3 instances reduces unnecessary operational and governance overhead.

    It also allows DAO to focus resources on markets that generate real usage and revenue. The proposed revenue floor for future deployments also sets a healthy precedent, ensuring Aave is fairly compensated for the value it brings to new chains.

447. Proposal: Aave V3.6 MegaETH Activation (Onchain)

  • Vote: For

  • Rationale: This proposal completes the necessary steps to proceed with the activation of the Aave V3 MegaETH pool, following prior approvals, technical validation, and risk parameter recommendations.

    Voted yes!

448. Proposal: Aave V3.6 Mantle Activation (Onchain)

  • Vote: For

  • Rationale: I support moving forward with a controlled, well vetted deployment.

    This proposal finalizes the activation of Aave V3 on Mantle following completed governance signaling, technical review, and risk assessment.

176

Date Voted: February 11, 2026

449. Proposal: Increase WBTC Liquidation Bonus and EURS Reserve Factor on Polygon V3 (Onchain)

  • Vote: For

  • Rationale: I support the proposal. This is a targeted risk fix.

    Increasing the WBTC liquidation bonus helps resolve stuck EURS liquidations, while raising the EURS reserve factor stops value leakage from a deprecated market.

450. Proposal: [ARFC ADDENDUM] Mandatory Disclosures and Conflict-of-Interest Voting (Snapshot)

  • Vote: For

  • Rationale: Clear disclosure and ethical abstention norms will improve transparency and protect the legitimacy of Aave governance, without adding onchain complexity.

    I support the transparency here. Voted yes!

177

Date Voted: February 19, 2026

451. Proposal: [ARFC] Revenue-indexed deficit offsets for Umbrella (Snapshot)

  • Vote: For

  • Rationale: I support this proposal.

    It makes the system more fair by linking liquidation revenue with how losses are covered before hitting Umbrella stakers.

    The proposed framework is conservative and consistent with how the DAO has historically handled moderate bad debt.

452. Proposal: Update syrupUSDC liquidation protocol fee (Onchain)

  • Vote: For

  • Rationale: This is just fixing a clear setup mistake. Updating it brings the configuration back in line with the original intent and protects DAO revenue

    Voted yes!

1 Like
178

Date Voted: February 24, 2026

453. Proposal: February 2026 - Funding Update (Onchain)

  • Vote: For
  • Rationale: The proposal improves capital efficiency, strengthens liquidity and reduces operational friction. Voted yes!

454. Proposal: Create Allowance GHO Mantle (Onchain)

  • Vote: For
  • Rationale: This is a necessary step to successfully deploy Aave V3 and GHO on Mantle. Voted yes!

455. Proposal: Focussing the Aave V3 Multichain Strategy - Phase 1 (Onchain)

  • Vote: For

  • Rationale: Freezing underperforming V3 instances reduces unnecessary operational and governance overhead.

    It also allows DAO to focus resources on markets that generate real usage and revenue.

    The proposed revenue floor for future deployments also sets a healthy precedent, ensuring Aave is fairly compensated for the value it brings to new chains.

179

Date Voted: February 26, 2026

456. Proposal: [TEMP CHECK] Aave Will Win Framework (Snapshot)

  • Vote: NAY

  • Rationale: Voting No.

    The ~$51M ask is too high given the execution track record since 2022, the lack of detailed financial reporting, and undisclosed governance power exposure.

    Bundling revenue redirection, funding, brand control, and Aave V4 ratification into one vote limits proper scrutiny, these items should stand on their own.

    If V4 is strong enough, it shouldn’t require forced V3 deprecation to succeed.

457. Proposal: [ARFC] Aave v3.7 candidate (Snapshot)

  • Vote: For

  • Rationale: This upgrade focuses on simplifying the protocol and removing unnecessary components, which strengthens long term security and operational efficiency.

    I’m in favor.

180

Date Voted: March 2, 2026

458. Proposal: Add GHO on Aave Plasma and deploy GSM on Plasma. (Onchain)

  • Vote: For

  • Rationale: Voting yes.

    It’s a strong step to grow GHO’s presence on Plasma, expand its use cases, and deepen liquidity.

    The plan is well coordinated across incentives and markets, while keeping risks controlled.

459. Proposal: GSM Migration (Onchain)

  • Vote: For

  • Rationale: Voting Yes.

    This upgrade strengthens GHO’s architecture and governance control, supporting its long term scalability and resilience.