Ignas Delegate Platform

Date Voted: March 4, 2026

460. Proposal: [TEMP CHECK] Deploy Aave Protocol on Monad (Snapshot)

  • Vote: For

  • Rationale: Monad’s high throughput, low latency architecture is well positioned for fintech and onchain neobank integrations.

    Establishing Aave early as the core liquidity layer increases the probability of capturing long term credit and stablecoin demand rather than short term mercenary liquidity.

    Voted yes on this tempcheck!

461. Proposal: [ARFC] Deploy Aave v3 on X Layer (Snapshot)

  • Vote: For

  • Rationale: Voted yes with same reason Snapshot vote

    X Layer gives the protocol a first mover advantage in a payment focused ecosystem that is aiming for strong DeFi adoption.

    The proposed risk parameters are conservative and incentives plus GHO integration improve the likelihood of real adoption.

Date Voted: March 6, 2026

462. Proposal: ACI Is Leaving Aave (Onchain)

  • Vote: For

  • Rationale: This is not an easy decision. I am voting yes.

    ACI has been a key contributor to Aave governance and has shown strong principles in focusing on what is best not only for the protocol but also for $AAVE token holders.

    Appreciate all the work. And best luck with the future endevours!

463. Proposal: Activate Capo Risk Agent and expand Rates Agent on more networks (Onchain)

  • Vote: For
  • Rationale: Voting yes. This expands the existing risk agent framework and adds CAPO to keep parameters for yield bearing assets closer to real market dynamics.

464. Proposal: Enhancing Market Granularity in Aave 3.6: part 2 (Onchain)

  • Date Voted: March 7, 2026

  • Vote: For

  • Rationale: I voted yes.

    Removes unnecessary exposure and cleans up legacy configurations, bringing Aave closer to a more disciplined and modular risk framework.

465. Proposal: [ARFC] Safety Module - Reduce Emissions (Snapshot)

  • Date Voted: March 9, 2026

  • Vote: For

  • Rationale: This proposal improves the efficiency of the Safety Module while maintaining strong protocol security.

    Coverage is well above what the protocol needs. I voted yes!

466. Proposal: [TEMP CHECK] Aave V4 Bug Bounty Program on Sherlock (Snapshot)

  • Date Voted: March 13, 2026

  • Vote: For

  • Rationale: Support launching a dedicated Aave V4 bug bounty program on Sherlock.

    Aave V4 introduces new architecture and attack surfaces, so having a dedicated, always-on bug bounty program is an important additional security layer alongside audits and formal verification.

467. Proposal: [ARFC] Buyback Program - Budget Adjustment (Snapshot)

  • Date Voted: March 14, 2026
  • Vote: For
  • Rationale: Support.

This is a necessary recalibration given declining revenue and a projected deficit.

Dropping to $30M still keeps Aave consistently buying back, but without putting unnecessary pressure on the treasury.

Prioritizing ETH funded buybacks is a sound treasury optimization, leveraging existing exposure and correlation with AAVE to reduce stablecoin outflows.

468. Proposal: [TEMP CHECK] Aave V4 Licensing (Snapshot)

  • Date Voted: March 16, 2026

  • Vote: For

  • Rationale: Clear, enforceable licensing that protects V4 in the short term while preserving a path to open source.

    DAO ownership and the CLA remove legal ambiguity and enable scalable, permissionless contributions. Voted yes!

Date Voted: March 17, 2026

469. Proposal: wstETH CAPO Oracle Incident User Reimbursement (Onchain)

  • Vote: For

  • Rationale: Clear protocol fault led to unjust liquidations, with users bearing no responsibility.

    Fully reimbursing them is the right decision to uphold trust, reinforce Aave’s credibility, and demonstrate strong accountability in edge case failures.

470. Proposal: Gho X-Layer Activation (Onchain)

  • Vote: For

  • Rationale: This sets up essential cross chain infrastructure via Chainlink CCIP, enabling GHO liquidity and usage on X Layer from day one.

    Support the proposal!

471. Proposal: [ARFC] Aave <> Chainlink SVR. Multi-network expansion (Snapshot)

  • Date Voted: March 20, 2026

  • Vote: For

  • Rationale: Voted yes.

    SVR has already proven effective on Ethereum, capturing liquidation value without introducing disruptions, even during volatile periods.

    Expanding to Base and Arbitrum is a logical next step, especially now that Chainlink has adapted the architecture to fit L2 environments.

Date Voted: March 22, 2026

472. Proposal: Reduce Safety Module Emissions (Onchain)

  • Vote: For
  • Rationale: Voted yes with same reason on ARFC stage. This proposal improves the efficiency of the Safety Module while maintaining strong protocol security.

473. Proposal: [ARFC] Aave V4 Activation on Ethereum Mainnet (Snapshot)

  • Vote: For

  • Rationale: V4 is a clear step in the right direction, the Hub and Spoke design and broader credit flexibility align well with where onchain finance is heading.

    Voted yes!

Date Voted: March 25, 2026

474. Proposal: Aave V3.6 XLayer Activation (Onchain)

  • Vote: For
  • Rationale: Clean final step after all approvals. Risk is well controlled with conservative caps and limited borrowability. Voted yes!

475. Proposal: Enable SVR on Base and Arbitrum (Onchain)

  • Vote: For

  • Rationale: Voted yes with same reason on snapshot!

    SVR has already proven effective on Ethereum, capturing liquidation value without introducing disruptions, even during volatile periods.

    Expanding to Base and Arbitrum is a logical next step, especially now that Chainlink has adapted the architecture to fit L2 environments.

476. Proposal: [ARFC] Bug Bounty Program on Sherlock (Snapshot)

  • Vote: For

  • Rationale: Supports adding an always on bug bounty for Aave V4 via Sherlock.

    The stake gated model is a practical way to reduce spam and keep focus on high severity issues. The 5% success based fee aligns costs with actual outcomes and avoids fixed overhead.

Date Voted: March 27, 2026

477. Proposal: [ARFC] Aave V4 Licensing (Snapshot)

  • Vote: For

  • Rationale: Voted yes with the same reason on snapshot vote. Clear, enforceable licensing that protects V4 in the short term while preserving a path to open source.

    DAO ownership and the CLA remove legal ambiguity and enable scalable, permissionless contributions.

478. Proposal: Onboard BTC.b to Aave V3 Core Instance (Onchain)

  • Vote: For

  • Rationale: Proven asset on Avalanche with validated risk, and Lombard infra already trusted via LBTC.

    Listing BTC.b as collateral only is a low risk way to expand BTC liquidity on Core.

479. Proposal: Aave V4 Activation on Ethereum Mainnet (Onchain)

  • Vote: For
  • Rationale: V4 is a step in the right direction, the Hub and Spoke design and broader credit flexibility align well with where onchain finance is heading. Voted yes!

480. Proposal: [TEMP CHECK] Onboard USSD to Aave V3 Sonic Instance (Snapshot)

  • Vote: For

  • Rationale: Support onboarding USSD as a native RWA-backed stablecoin to strengthen Sonic liquidity and expand stable borrowing on Aave.

    Given this is a new asset, looking forward to detailed risk analysis and conservative parameters in the next phase.

Date Voted: April 2, 2026

481. Proposal: [ARFC] Update Signers and SAFE Configuration March 2026 (Snapshot)

  • Vote: For
  • Rationale: Voted yes. Moving from 3/4 to 3/5 improves signer availability and reduces execution delays.

482. Proposal: [ARFC] sGHO Launch Configuration (Snapshot)

  • Vote: For

  • Rationale: This upgrade turns sGHO into a clean, native yield primitive.

    The fixed 4.25% rate is competitive, and the migration design is well structured to drive adoption.

    I voted in favor.

483. Proposal: Listing PT Ethena 18JUN2026 (Onchain)

  • Vote: For
  • Rationale: This is a clean rollover of PT USDe and sUSDe that has already proven to drive inflows. The conservative design keeps risk contained. Voted yes!

Date Voted: April 4, 2026

484. Proposal: [ARFC] Onboard PT-USDG-28MAY2026 to Aave V3 Core Instance (Snapshot)

  • Vote: For

  • Rationale: This adds dollar-based asset (USDG from Paxos) that already has real usage on Pendle Finance.

    A simple way to expand collateral options and let users unlock liquidity from existing positions. Voted yes!

485. Proposal: [ARFC] Continued Deprecation Steps of Aave V2 Markets (Snapshot)

  • Vote: For

  • Rationale: I support this proposal.

    These changes are well aligned with the goal of safely deprecating Aave V2, a risk aware approach to reduce bad debt and ensure an orderly wind down of V2.

486. Proposal: March Funding Update (Onchain)

  • Vote: For

  • Rationale: A standard treasury and operations update that improves capital efficiency and ensures DAO can continue executing its strategy smoothly.

    Voted yes!

487. Proposal: Listing PT Strata 25JUN2026 (Onchain)

  • Vote: For
  • Rationale: Voted yes. This extends a well established PT framework to a new maturity, maintaining consistency with previous listings.

488. Proposal: Umbrella Deficit Updates (Onchain)

  • Vote: For

  • Rationale: Support the proposal!

    Increasing the offset ensures DAO properly acts as the first loss layer, reducing unnecessary slashing in normal liquidation regimes while still preserving slashing for true tail events.

489. Proposal: Collateral Parameters Adjustment on MegaETH v3 (Onchain)

  • Vote: For
  • Rationale: Vote yes. This enables cross-margin use of WETH, BTC.b, and wstETH while keeping eMode risk protections and using conservative parameters for safety.

490. Proposal: Aave Will Win Framework: Primary Funding Request (Onchain)

  • Vote: For
  • Rationale: Vote support this proposal as it is a direct execution of the broader Aave Will Win framework already approved by the DAO through Snapshot.

491. Proposal: [TEMP CHECK] Onboard USSD to Aave V3 Sonic Instance (Snapshot)

  • Vote: For

  • Rationale: USSD is positioned to become a core stablecoin in the Sonic Labs ecosystem, onboarding it helps Aave capture early lending and borrowing demand around a strategic liquidity asset.

    Final implementation should remain subject to satisfactory risk parameters at ARFC. I support the proposal in this Tempcheck phase!

492. Proposal: Deprecate Aave V3 Scroll Instance (Onchain)

  • Vote: For
  • Rationale: With liquidity and TVL on Scroll declining significantly, offboarding this instance is a sensible risk management step. Voted yes!

493. Proposal: Onboard PT-USDG 28MAY2026 on V3 Core (Onchain)

  • Vote: For

  • Rationale: This adds dollar-based asset (USDG from Paxos) that already has real usage on Pendle Finance.

    A simple way to expand collateral options and let users unlock liquidity from existing positions. Voted yes!

494. Proposal: Onboard USDe to the Aave V3 MegaETH Instance (Onchain)

  • Vote: For
  • Rationale: Adding USDe to Aave V3 MegaETH expands the stablecoin market with a proven asset and maintaining prudent risk controls through E-Mode restrictions. Voted yes!

495. Proposal: Upgrade Aave instances to v3.7 Part 1 (Onchain)

  • Vote: For
  • Rationale: For. A clean upgrade that simplifies the protocol and improves maintainability.

496. Proposal: GHO Inclusion into E-Modes on Aave V3 Plasma (Onchain)

  • Vote: For
  • Rationale: Adding GHO as a borrowable asset in these E-Modes strengthens its integration without introducing new collateral risk or changing core parameters.

497. Proposal: April Funding Update (Onchain)

  • Vote: For
  • Rationale: Voting yes on April Funding Update. This keeps funds organized, maintains runway, and makes sure incentives, audits, and ops can continue effectively.

498. Proposal: Onboard USDe to the Aave V3 MegaETH Instance (Onchain)

  • Vote: For

  • Rationale: The propopsal adds a high demand asset and unlocks yield looping on MegaETH. Risk is contained through E Mode restrictions and conservative caps.

    I support the proposal!

499. Proposal: [ARFC] Pause AAVE Buybacks (Snapshot)

  • Vote: For

  • Rationale: I support the proposal.

    Risk control should come first. Preserving treasury assets and maintaining flexibility is more important than continuing buybacks while uncertainty remains.

    Strengthening the DAO’s financial position now will better support confidence and long term resilience.

500. Proposal: [ARFC] rsETH Incident Funding Update (Snapshot)

  • Vote: For

  • Rationale: Using part of the treasury to help resolve the rsETH shortfall can protect affected Aave markets, reduce broader contagion risk, and reinforce user confidence.

    Support!

501. Proposal: rsETH Incident: Liquidate rsETH attacker positions (Onchain)

  • Vote: For
  • Rationale: A very necessary risk containment step following the incident. Liquidation is the cleanest way to lock funds, limit bad debt, and move assets under DAO control for recovery. I support the proposal!

502. Proposal: Orderly Transition and Offboarding Plan for Chaos Labs (Onchain)

  • Vote: For

  • Rationale: This proposal formalizes a smooth handoff to LlamaRisk, ensuring continuity while keeping the offboarding clean and time bound.

    Appreciate all the work Chaos Labs has done for Aave.

503. Proposal: Winding Down the LEND Migration Contract (Onchain)

  • Vote: For
  • Rationale: I support this proposal as a necessary and long overdue cleanup of legacy infrastructure.

504. Proposal: [ARFC] Aave Protocol Bug Bounty Programs Restructure (Snapshot)

  • Vote: For

  • Rationale: Splitting bug bounties by subsystem better reflects Aave’s complexity and improves clarity for researchers.

    Aligning rewards with risk, especially increasing critical payouts is necessary to attract top talent. I support the proposal!

505. Proposal: [ARFC] Renew LlamaRisk as Risk Service Provider - epoch 4 (Snapshot)

  • Vote: For
  • Rationale: Appreciate LlamaRisk stepping in to ensure continuity during a critical transition, as well as the focus on building verifiable, DAO controlled risk infrastructure. I support the proposal!

506. Proposal: rsETH Incident: WETH LTV Restoration Across V3 Instances (Onchain)

  • Vote: For

  • Rationale: Voting For on Restore WETH LTV Across Aave V3 Instances!

    Recovery is effectively complete. 95% of unbacked rsETH recovered, attacker positions liquidated, and binding commitments in place for the remainder.

507. Proposal: Add CoW Swap Adapters to flashBorrowers (Onchain)

  • Vote: For
  • Rationale: This is a simple tradeoff, drop a negligible fee, keep users from routing elsewhere.
    Better swap execution means more activity stays inside Aave, where protocol revenue actually comes from. Voted yes!

508. Proposal: sGho Launch (Onchain)

  • Vote: For

  • Rationale: Voting yes with the same reason on Snapshot. This upgrade turns sGHO into a clean, native yield primitive.

    The fixed 4.25% rate is competitive, the migration design is well structured to drive adoption.