# [ARFC] SVR Expansion: Next Phase of Multi-Network

- Space: [Aave DAO](https://snapshot.box/s:aavedao.eth.md)
- Author: 0x2cc1ADE245020FC5AAE66Ad443e1F66e01c54Df1
- State: Passed
- Voting type: Basic
- Start: 2026-10-21 08:59 UTC
- End: 2026-10-24 08:59 UTC
- Votes: 99
- Discussion: https://governance.aave.com/t/arfc-svr-expansion-next-phase-of-multi-network-expansion/25332
- Open in Snapshot: https://snapshot.box/#/s:aavedao.eth/proposal/0x8d58b2adeea86e86b5d204f5d5c90534fc5a5e71bca9efdf7b5912ce0888630f

## Results

- For: 371,294.5 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0.02 voting power, 0.0%

## Proposal

---

title: [ARFC] SVR Expansion: Next Phase of Multi-Network Expansion
author: @TokenLogic
created: 2026-07-16

---
# Summary

This analysis evaluates the historical performance of Aave's existing SVR deployments, identifies the most promising candidates for future SVR integrations, and highlights opportunities to improve the performance of existing deployments.

Since launching on Ethereum in 2025 and subsequently expanding to Base and Arbitrum, SVR has processed approximately $877.6M of liquidation volume, generating more than $21.3M in gross revenue, of which approximately $13.9M has accrued directly to the Aave DAO. Historical results demonstrate that recapture rates are influenced by differences in the underlying MEV supply chain, the auction architecture, and the distribution of liquidation sizes. As a result, Base and Arbitrum have achieved recapture rates of approximately 89%, compared to approximately 52% on Ethereum Core V3.

Based on the analysis below, we recommend prioritizing Avalanche, Polygon, and BNB Chain V3 deployments for future SVR integrations. Assuming 80% SVR coverage and an 80% recapture rate, these deployments would have generated an additional $1.81M in revenue for the Aave DAO over the past year, representing an approximately 11% increase relative to the revenue generated by existing SVR deployments over the same period.

# Overview of SVR

SVR is a mechanism that enables Aave to capture a portion of the value traditionally extracted by liquidators during oracle driven liquidations. Rather than allowing searchers to compete for liquidation opportunities immediately following a price update, SVR auctions the right to execute transactions alongside the associated oracle update, allowing a portion of the resulting value to be redirected to the protocol.

Aave shares SVR proceeds with Chainlink, with 65% allocated to Aave and 35% to Chainlink, and has progressively expanded SVR coverage across its deployments. The first implementation was introduced on Aave V3 Ethereum in March 2025, initially covering a limited set of assets before being expanded through additional deployment phases in June and August 2025.

In March 2026, SVR was expanded to Aave V3 on Base and Arbitrum through Chainlink's Atlas based cross chain auction framework. Aave V4 launched on Ethereum mainnet on March 30, 2026 using standard price feeds, SVR was added roughly six weeks later, on May 15, 2026, when eligible assets across V4's spoke oracles had their price sources swapped to SVR feeds.

| Deployment | Chain | Since |
|----|----|----|
| Aave V3 Core | Ethereum | March 2025 |
| Aave V3 Prime | Ethereum | May 2025 |
| Aave V3 | Base | March 2026 |
| Aave V3 | Arbitrum | March 2026 |
| Aave V4 | Ethereum | May 2026 |

As of today, Ethereum, Base, and Arbitrum represent the primary production deployments from which historical SVR performance can be evaluated. Markets on these chains provide the basis for assessing recapture rates and estimating the potential revenue impact of extending SVR to additional Aave instances.

# Improvement Areas

While the previous sections focus on expanding SVR to additional Aave deployments, the historical data also identifies opportunities to improve the performance of existing deployments. The most significant opportunity lies in increasing recapture rates for large liquidation events on Ethereum.

Historical liquidation data shows a clear inverse relationship between liquidation size and SVR recapture rate. As liquidation size increases, both the proportion of the liquidation bonus recaptured through SVR and the number of liquidators able to participate in these auctions decline materially, as illustrated in the "Recapture Rate and Distinct Liquidators by Liquidation Size Bucket" chart presented in the previous section.

![image|1551x1014](upload://djaYYEq151xdIOsNas2MuGqXJiv.jpeg)

This effect is particularly pronounced for liquidations exceeding $5M in size, where the average recapture rate falls to approximately 36.7%, substantially below the rates observed for smaller liquidations.

![image|1189x690](upload://tuPNRkYY3nr4VI0JUWa4qSdArp.png)

The impact of this decline becomes apparent when comparing the revenue generated by these liquidation size buckets. Although the $5M-$50M bucket represents the largest source of liquidation volume, totaling approximately $378M over the past year, it generated $4.2M in protocol revenue due to its relatively low recapture rate of 36.7%. By comparison, the $500K-$5M bucket processed a smaller liquidation volume of $318M, yet generated $5.6M in protocol revenue because it maintained a higher recapture rate of 57.7%.

![image|1290x670](upload://ucTEoYe0zzDcoIrtPwSCGylAdQG.png)

This disparity suggests that large liquidation opportunities remain one of the largest untapped sources of incremental SVR revenue.

Several factors contribute to the lower recapture rates observed for larger liquidations. Large liquidations require substantially greater capital commitments, expose liquidators to higher execution risk and slippage, and often require more sophisticated inventory management and financing strategies. These higher execution costs reduce the amount of liquidation value that can be competitively bid through SVR auctions. In addition, fewer liquidators possess the capital and operational infrastructure necessary to compete for multi million dollar liquidation opportunities, resulting in reduced auction competition relative to smaller liquidations.

Despite these structural constraints, historical data indicates that there remains meaningful room for improvement. Increasing competition for large liquidation opportunities, could materially increase protocol revenue.

Illustratively, if the average recapture rate for liquidations between $5M-$50M increased from 36.7% to 55%, Aave would have generated approximately $2.09M in additional SVR revenue over the past year.

Similarly, the $500K-$5M liquidation bucket represents another meaningful opportunity for improvement. Its current recapture rate of 57.7%. Increasing the average recapture rate for this bucket to 70% would have generated approximately $1.2M in additional SVR revenue over the same period.

| Liquidation Bucket | Current Recapture Rate | Illustrative Target | Additional Aave Revenue (365D) |
|----|----|----|----|
| $5M-$50M | 36.7% | 55% | +$2.1M |
| $500K-$5M | 57.7% | 70% | +$1.2M |

These results suggest that improving auction competition for large liquidations may represent one of the highest-return opportunities for Ethereum development. While structural factors such as execution costs and slippage are likely to impose an upper bound on achievable recapture rates, even modest improvements could generate protocol revenue comparable to, or exceeding, the impact of several additional SVR deployments.

### Note: Some text has been removed due to Snapshot character count limitations. Please refer to the forum post linked below for the full details.

# Specification

Based on the analysis presented in this report, we recommend enabling SVR for the following assets across the corresponding Aave deployments.

| Deployment | Assets |
|----|----|
| **Avalanche V3** | BTC.b, AVAX, sAVAX, USDC, WETH.e, USDT, DAI.e, EURC, LINK.e, AUSD, AAVE.e, WBTC.e, sUSDe, FRAX, USDe |
| **Polygon V3** | WBTC, USDT0, USDC, WETH, wstETH, POL, USDC.e, DAI, AAVE, EURS, LINK, MaticX |
| **BNB Chain V3** | BNB, BTCB, USDT, USDC, ETH, wstETH, FDUSD, CAKE |

## **SVROracleSteward**

As with all SVR activations on other instances of the Aave Protocol, this expansion will include `SVROracleStewards`.

To refresh, the SvrOracleSteward allows for the Aave Protocol Guardian to replace any of the newly introduced SVR feeds with the non-SVR feed currently used in production. In the very worst-case scenario where the new SVR is simply not functional or has a major issue, the Aave Protocol Guardian could immediately switch back to the standard price feeds currently used in production.

Existing `SVROracleStewards` for Arbitrum and Base used in the [previous expansion](https://governance.aave.com/t/arfc-aave-chainlink-svr-multi-network-expansion-base-arbitrum/24241) shall be deprecated by removing their asset listing permission. This step has already been executed for [Ethereum Mainnet](https://github.com/aave-dao/aave-proposals-v3/pull/999/changes#diff-35e448207c30b0751e737b51f2ff695fbb3ad907ced1f48d957541ce35c53c1bR14).

# Next Steps

* Gather feedback from governance participants and relevant service providers.
* Incorporate any necessary revisions based on community discussion and technical feedback.
* If there is broad community support, proceed with an ARFC.
* If the ARFC is approved, proceed with an AIP to replace the existing price oracles with SVR enabled oracles on the approved deployments.

# Disclaimer

TokenLogic is an active service provider to the Aave DAO, the beneficiary of stream 100086 and the KPI as outlined in this [publication](https://governance.aave.com/t/arfc-service-provider-compensation-reform-for-v4-alignment/23246). The scope of this engagement is available via this forum [proposal](https://governance.aave.com/t/arfc-tokenlogic-phase-ii-extension/24846).

TokenLogic supports and maintains an independent [delegate voting platform](https://governance.aave.com/t/tokenlogic-delegate-platform/12516) within the Aave community.

TokenLogic and associated entities have no undisclosed material conflicts of interest at the time of submission.

# Next Steps

1. Gather feedback from the community.
2. If consensus is reached on this ARFC, escalate this proposal to the Snapshot stage.
3. If Snapshot outcome is YAE, escalate this proposal to the AIP stage.

# Copyright

Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

