[ARFC] Deploy Aave v3 on Sonic

[ARFC] Deploy Aave v3 on Sonic

Author: ACI

Date: 2025-01-07


Risk Parameters have been provided by Service Providers and this section has been updated 2025-01-30

Risk Parameters have been updated again by Service Providers due to improvements and market conditions, and this section has been updated again 2025-02-20

Simple Summary:

This ARFC seeks the community’s input on the deployment of Aave V3 on Sonic Mainnet.

Background:

Sonic is a new Layer 1 EVM blockchain offering 10,000 TPS and fee monetization for app builders. It is the newest blockchain from the creators of Fantom which reached a peak TVL of circa $14.5 billion in 2021.

Motivation

Aave has deployed on multiple promising new L1 and L2 EVM networks and is often one of the largest protocols on these networks. Given the impressive history of the team building Sonic, and the innovations it promises, it represents a strong candidate for deployment of Aave V3. In addition, the fee monetization for apps has potential to be an additional income source for Aave.

Proof of Liquidity (POL) and Deposit Commitments:

The Sonic Foundation will provide the following, upon its deployment is confirmed:

  • 15M USD Funding from Sonic
  • 800k USD stablecoins from Aave
  • Up to 50M $S tokens Supply
  • 20M of USDC Supply

Specification:

Risk Parameters have been provided by Service Providers and this section has been updated 2025-01-30
Risk Parameters have been updated again by Service Providers due to improvements and market conditions, and this section has been updated again 2025-02-20

Parameter
Asset WETH wS USDC.e
Isolation Mode No No No
Enable Borrow Yes Yes Yes
Enable Collateral Yes Yes Yes
Loan To Value 80% 68% 75%
Liquidation Threshold 83% 70% 78%
Liquidation Bonus 6% 10% 5%
Reserve Factor 15% 15% 10%
Liquidation Protocol Fee 10% 10% 10%
Supply Cap 3000 20,000,000 20,000,000
Borrow Cap 2750 10,000,000 19,000,000
Debt Ceiling - - -
UOptimal 90% 45% 90%
Base 0% 0% 0%
Slope1 2.7% 7% 9.5%
Slope2 80% 300% 40%
Stable Borrowing No No No
Flashloanable Yes Yes Yes
Siloed Borrowing No No No
Borrowable in Isolation No No Yes
E-Mode Category N/A N/A N/A

Disclaimer:

This proposal is powered by Skywards. The ACI is not directly affiliated with Fantom or Sonic and did not receive any compensation for creating this proposal.

Useful Links

[TEMP CHECK] Deploy Aave v3 on Sonic

TEMP CHECK Snapshot

Next Steps

  1. Publication of a standard ARFC, collect community & service providers feedback before escalating proposal to ARFC snapshot stage.
  2. If the ARFC snapshot outcome is YAE, publish an AIP vote for final confirmation and enforcement of the proposal.

Copyright:

Copyright and related rights waived under CC0.

7 Likes

Summary

LlamaRisk supports deployment to the Sonic network with low initial supply caps on WETH, USDC, and S. Network TVL is growing rapidly but is still limited. These supply caps may be raised when liquidity is sufficient in the future through risk stewards.

We do not find significant risk stemming from Sonic’s chain infrastructure, though it is notable that there is no clear upgrade management process yet. The network is relatively decentralized, with 36 validators at this developmental stage. This validator count will likely continue to increase, further reducing centralization risk.

The present market infrastructure (e.g., DEXes) is sufficient and growing. While liquidity on the network restraints Aave’s growth, Sonic Labs is implementing thoughtful incentive strategies to improve this situation. It is also important to consider how an Aave deployment may affect network liquidity. Aave DAO should note that all stables are currently bridged, though natively-issued assets should be expected in the next month.

Considering this, we deem Sonic a suitable venue for an Aave deployment conditional to low supply caps on day 1. These supply caps may be increased as liquidity improves on the network, with caps roughly staying in line with a one-to-two times liquidity framework.

We suggest Aave onboards $USDC, $WETH, and $S on launch, with parameters aligned by Risk Providers closer to launch due to the developing liquidity situation. Other assets like $stS should be onboarded through regular governance processes.

1. Network Fundamental Characteristics

1.1 Network Overview

1.1.1 Architecture

Sonic is an EVM-equivalent Layer 1 platform that targets 10,000 TPS. It uses directed acyclic graph (DAG), asynchronous byzantine fault tolerant based proof of stake to reach consensus which is powered by its native $S token.


Source: DAG Visualization, Central Blockchain Council of America

Sonic is worked on by many contributors who also worked on Fantom, an L1 with a conceptually similar EVM-equivalent L1. This network’s consensus mechanism is a “continuation” of Fantom Opera.

Sonic is notable for its database storage techniques, in which validators push historical transactions to archive nodes to reduce storage requirements without going offline. This is known as “live pruning”.

1.1.2 Security

Change management processes are not detailed but will be announced before implementing onchain governance. Network bridges have been audited, and nonpublic consensus mechanism audits have been reviewed by LlamaRisk, which resolved 1 medium and 1 low finding. A $2M bug bounty is documented but does not yet have details relating to scope.


Source: Sonic Labs Audits

The network is new, with transactions reaching ~600K daily after launch on December 18th. This is lower than mainnet (~1.1M daily) and substantially lower than low-fee networks such as BNBChain at ~3.5M daily transactions. This is likely to increase as the network further establishes itself.

The primary network bridge (Sonic Gateway) is managed by a 2/4 Safe owned by Sonic Labs. This introduces significant risk and centralizes critical infrastructure into Labs’ hands. This Safe may change signers and thresholds, change ownership structures, and execute specific transactions. Other network bridges, such as Linea, use similarly permissioned bridges.

1.2 Decentralization and Legal Evaluation
This network is relatively well decentralized for having launched so recently with 36 validators. The amount of S staked to each validator is also well distributed, with 30 of these validators having more than 5M staked with them (versus ~80M for the top validator).


Source: Sonic Genesis Node Details, January 8th, 2025

Only one node client is documented, compared to Ethereum’s 8. This increases risk as a bug in the one-node client may result in the network not functioning as intended and no alternative solution to validate Sonic.

The network emphasizes its unique revenue redistribution system known as FeeM. This system is implemented to help sustain apps that deploy to the network with more regular income paid for by network fees. This may hinder decentralization as the returns for validators will be instead directed towards dApps on the network.

1.3 Legal Evaluation

By accessing and using http://www.soniclabs.com, users enter into a binding agreement with Sonic Labs Ltd, a company based in the Bahamas, and Sonic Foundation, a Cayman Islands-based entity. The Terms and Conditions (T&C) governing this agreement are explicitly limited in their application to activities conducted on http://www.soniclabs.com and the communication channels supported by these Sonic entities. This will not change as the migration from Fantom or Sonic concludes.

Importantly, T&C does not extend to Sonic Chain or any protocols developed on top of it. A distinct Important Notice provides disclosures and information specific to Sonic Chain.

1.4 Activity Benchmarks as of January 7th, 2025

Metrics Description
TVL on Sonic $62M (not including $S, $72M if including)
Market capitalization of $S $1.9B (of FTM, which is 1:1 redeemable for $S)
Stablecoin TVL / dominance USDC 88%
Number and concentration of protocols 5 protocols have >$500K TVL, 2 protocols (Beets and Wagmi) have ~80% of TVL
24 hour DEX volume ~$30M
Perpetuals open interest N/A
Total value borrowed $150,000 (Avalon, $S)
Value at risk for a 15% drawdown N/A
Bad debt accrued N/A
Average supply APY (Stable or Volatile) (9% on $stS / $S on Beets, 2.5% on supplied $S on Avalon)
Average utilization Rates for majors 75% on Avalon

Sources: DeFiLlama, Dune , January 7th, 2025

2. Network Market Outlook

2.1 Market Infrastructure
Sonic has core DeFi building blocks available:

  • CDPs: Rings
  • LSTs: beets.fi
  • DEXs: beets.fi, Wagmi, Metropolis Exchange, Solidly
  • Lending: Avalon - an Aave V3 fork
  • Liquidity management: Stability
  • Bridges: Sonic Gateway
  • Wallets: Major EVM wallets such as Metamask, Rabby, and Frame support Sonic
  • Onramps: None yet available
  • Oracles: Chainlink, Band, API3, Pyth
  • Exchanges: No exchanges currently support Sonic network withdrawals, but many networks will after token migration on January 13th

This network is new, so the diversity of these building blocks is limited. It is nonetheless true that key infrastructure is present in some form, with more options coming onchain every day. While the most critical of infrastructure (DEXs) has many options, liquidity is concentrated (with approximately >80% of network TVL held in two DEXs, Beets and Wagmi).

2.2 Liquidity Landscape
The network’s liquidity landscape is currently developmental and concentrated:


Source: DefiLlama, January 8th, 2025

It is growing at an impressive rate, with 30% daily TVL increases occurring regularly. This is expected given the low base figure from which the TVL grows and the fact that much liquidity will migrate from the Fantom network as Sonic’s migration proceeds.

2.3 Growth Initiatives
Sonic’s ecosystem is carefully designed with sustainable growth and incentives strategy in mind. This network takes its growth strategy as seriously as any other part of its operation.


Source: Sonic’s airdrop strategy vesting schedule

The Sonic Boom program is a targeted bounty program for specific pieces of DeFi infrastructure (e.g. yield aggregators or lending protocols) that should accelerate the development of the network from the onset. Sonic is also airdropping 190M $S tokens to early users of the network (with the earned 25% unlocked, 75% vested). This will go some distance to reinforce the network by attracting liquidity that is looking to benefit from the airdrop. Finally, fee revenue sharing (outlined in section 1) will help this network create a self-sustaining ecosystem.

2.4 Major and Native Asset Outlook
Native tokens are widely available with some 37M wrapped Sonic onchain with 69M staked Sonic available. Liquidity for major tokens is more limited with 15M bridged USDC and 3000 ETH. Sonic Labs has informed LlamaRisk that this is likely to change drastically shortly.

3. Onchain discoverability

An Etherscan-equivalent block explorer, SonicScan, is available. DeFiLlama covers a wide range of active protocols. Dune and theGraph support Sonic.

4. Risk Impact of AAVE Deployment

Sonic’s network architecture presents few risks to Aave. Aave was already deployed to Fantom, a previous version of a DAG-type blockchain developed by the same team. As a newer network, its level of decentralization is already adequate at 36 validators with good staking distribution, making the likelihood of transaction censorship low. One area of risk stemming directly from the network is the lack of established change management. Upgrades to consensus mechanisms may have unintended consequences on Aave user funds if implemented imperfectly, introducing risk. This risk in an important area is reasonably likely to occur as the network develops. This risk is compounded by having only one node client, which results in limited redundancy.

Sonic’s ecosystem possesses key market infrastructure pieces to facilitate an Aave deployment. Aave has met its most basic functional needs with Chainlink oracles, numerous DEXs, a range of assets, major wallet support, and good bridge infrastructure.

However, this network is still new, and liquidity is still limited. With limited liquidity, liquidators may not profitably purchase and sell distressed Aave collateral positions, meaning bad debt may accrue. Risk providers must set limited supply caps to avoid this risk, meaning Aave may not generate meaningful revenue. This is not conducive to a highly successful Aave deployment and results in large costs for the DAO. At the same time, Sonic will incentivize Aave and commit deposits soon until those materialize; while thin liquidity does not present a risk to Aave deployment, it severely constrains its growth.

Onchain discoverability enables sufficient transparency to host an Aave deployment.

5. Asset suggestions

Asset parameters and price feeds will be aligned with Risk Providers before deployment and proposed to the DAO. We recommend the following assets be onboarded on day one:

  • $WETH
  • $wS
  • $USDC

Other ecosystem assets such as $wstS or $USDT may be onboarded suitable for governance processes.

Disclaimer

This review was independently prepared by LlamaRisk, a community-led non-profit decentralized organization funded in part by the Aave DAO. LlamaRisk is not directly affiliated with the protocol(s) reviewed in this assessment and did not receive any compensation from the protocol(s) or their affiliated entities for this work.

The information provided should not be construed as legal, financial, tax, or professional advice.

5 Likes

Overview

Chaos Labs supports the proposal to deploy an Aave V3 instance on Sonic to expand the Aave protocol’s user base.

The following analysis focuses on the initial listing of WETH, USDC.e, and S, as well as an analysis of the Sonic ecosystem.

Technical Architecture

Sonic is an EVM layer-1 blockchain network that advertises 10,000 TPS and sub-second finality. Sonic uses a POS, DAG-based, Asynchronous BFT consensus mechanism in which each validator has its own local block DAG; transactions are batched and added to their DAG as vertices. Validators must lock at least 500,000 of Sonic’s native token S, which is subject to slashing.

Sonic utilizes a native bridge between Ethereum and Sonic called Sonic Gateway. The bridging process requires a user to deposit, wait for finalization on Ethereum, wait for a heartbeat (every 10 minutes from Ethereum to Sonic; this can be expedited by paying a Fast Lane fee, triggering an immediate heartbeat), and claim. Fast Lane heartbeats also process all other queued assets that were waiting for a hearbeat.

Sonic Gateway has a fail-safe mechanism that allows unlocks a user funds on Ethereum if the Sonic chain or Gateway are down for 14 consecutive days. The 14-day period is immutable.

Gateway currently supports USDC, EURC, WETH, and FTM.

Ecosystem and Market

Sonic is still a nascent ecosystem and it is likely that its TVL and volume will continue to grow as the team promotes migration from Fantom using incentive programs. As of this writing, its TVL stands at just under $60M, with somewhat slow growth immediately after launch that has since accelerated.

The maximum number of daily transactions observed on Sonic was 700K; unique addresses has displayed steady growth since the end of December.

Finally, the number of deployed contracts (both verified and unverified) indicates robust activity on the network.

DEXs

There are multiple DEXes already deployed on Sonic. The largest is Beets, which is also available on Fantom and Optimism. Notable DEXes include:

  • Beets
    • TVL: $61.63M
  • WAGMI
    • TVL: $21.26M
  • Equalizer
    • TVL: $8.68M
  • SwapX
    • TVL: $2.52M
  • Shadow Exchange
    • TVL: $2.50M
  • Metropolis Exchange
    • TVL: $2.45M

Tokens

Taking into account the nascency of the network, we initially recommend a strict list of assets that have previously been covered by the Aave Risk Providers (the exception being S, the upgraded version of FTM). The selection aims to provide basic functionality for the new instance, with any additions and successive listings being proposed and approved through standard governance procedures.

Chaos Labs proposes the following assets for the initial listing on the Sonic instance:

Asset Supply on Sonic Market Cap on Sonic 24H DEX Volume on Sonic Sell Liquidity Sonicscan
WETH 3,083 $10.1M $4.3M $1.95M Link
USDC.e 16.35M $16.35M $16.8M $2.72M Link
wS 39.4M $26M $28.5M $1.6M Link

Regarding wS, users are able to migrate their FTM held on Fantom to S held on Sonic using Sonic’s native upgrade interface; this can be done in reverse for the first 90 days after Sonic’s mainnet launch. Upgrading may take up to an hour. As of this writing, there is a 0.1 FTM fee to upgrade, though the interface states that this may be increased if the number of transactions exceeds 2M per day in order to reduce spam. The fee in the other direction is currently 0.5 S. FTM held on Ethereum can be similarly bridged using the Sonic Gateway.

A blog from Sonic Labs indicates that there will likely be changes in the max supply of S compared to FTM over time, potentially causing the prices of the two assets to dislocate. While there is no established timeline, six months is provided as the minimum time during which users will be able to upgrade at a 1:1 ratio, whereas the documentation states that the FTM → S upgrade will be available indefinitely. Temporary price dislocations are possible during the upgrade period if there is transaction spam that causes upgrade fees to be increased.

Given these uncertainties, we recommend listing the asset with somewhat conservative collateral parameters; these parameters can be adjusted following listing and once a clearer view of the network’s liquidity and the token’s volatility is available.

Oracles

There are currently no Chainlink oracles available on Sonic, though Sonic Labs has announced that it joined Chainlink Scale and would be integrating Chainlink’s oracles and CCIP. Thus, this recommendation is contingent on these oracles becoming available.

Listing Parameters

In the case of WETH and USDC.e, we recommend aligning their parameters with their respective parameters on other deployments. As discussed for wS, we recommend setting conservative collateral parameters and aligning its IR curve with other volatile assets.

Supply and Borrow Caps

In line with Chaos Labs’ approach to setting initial supply caps, we recommend a supply cap set to 2x the liquidity available under the a price impact equivalent to the asset’s Liquidation Penalty. We also recommend setting the borrow caps slightly higher than the UOptimal of each asset to allow for a borrow rate increase to follow a surge in demand.

For USDC.e, the supply cap is set to allow full utilization of the other collateral assets within the instance while maintaining it below 75% of the on-chain supply.

Specification

Following the above analysis, we recommend the following initial parameters for the creation of the Sonic deployment:

Parameter
Asset WETH wS USDC.e
Isolation Mode No No No
Enable Borrow Yes Yes Yes
Enable Collateral Yes Yes Yes
Loan To Value 80% 35% 75%
Liquidation Threshold 83% 40% 78%
Liquidation Bonus 6% 10% 5%
Reserve Factor 15% 20% 10%
Liquidation Protocol Fee 10% 10% 10%
Supply Cap 400 3,000,000 2,000,000
Borrow Cap 370 1,500,000 1,900,000
Debt Ceiling - - -
UOptimal 90% 45% 90%
Base 0% 0% 0%
Slope1 2.7% 7% 12.5%
Slope2 80% 300% 40%
Stable Borrowing No No No
Flashloanable Yes Yes Yes
Siloed Borrowing No No No
Borrowable in Isolation No No Yes
E-Mode Category N/A N/A N/A

Disclaimer

Chaos Labs has not been compensated by any third party for publishing this recommendation.

Copyright

Copyright and related rights waived via CC0

4 Likes

when will we have a snapshot?

2 Likes

I’m assuming you mean when will there be the next snapshot? See below for the Governance process & timelines. Don’t forget each step isn’t instantaneous for each proposal.
TEMP CHECK post (5 days) TEMP CHECK snapshot (4 days), ARFC post (5 days), ARFC Snapshot (4days) AIP vote and execution (4 days)

5 Likes

ty, but its been 10 days since ARFC post, shouldn’t ARFC snapshot be up already?

2 Likes

Saucy Block is supportive of deploying Aave V3 on Sonic for the following four reasons:

  • Sonic Labs leverages its experience with Fantom to achieve high decentralization, security, EVM compatibility, and remarkable fast execution.
  • In just about one month, Sonic’s TVL has exceeded $150M, making it currently the most noteworthy emerging market. Furthermore, with Silo exceeding $55M and Avalon Labs surpassing $25M, it can deduce that there is high demand for the lending market.
  • The proposed POL and Deposit Commitments are sufficient for Aave V3 to establish a strategic position.
  • Sonic Ecosystem is rapidly growing, attracting significant attention from developers through its “Sonic Point & Gems” - First season plans a total Airdrop of 200m S until June - and “FeeM” - pays back apps up to 90% of network fees generated by applications - .
1 Like

What is the next step? When update?

3 Likes

Its been 20 days, why there is still no snapshot?

2 Likes

Is the snapshot purposefully being delayed or what is going on here?

1 Like

well, according to your timeline we should have already moved on. What is causing the delay?

You have to take into account, that besides the governance process there are also other dependencies. Security is top notch at Aave thus a review is always needed an important. Also there are incentives that need to be prepared from Sonic side. So it’s not like things happen magically. It’s work that needs to be done by several parties. So things might take time.

4 Likes

As @EzR3aL mention, a proposal to deploy Aave will never escalate to ARFC Snapshot unless Security & Development Service Providers have had all the information to properly assess the proposal. Aave DAO values security above all things, and at ACI, as Growth Service Providers, we work closely with all Service Providers to make sure, quality and security prevails over speed.

When this ARFC and other ARFC will be ready to be escalated, we will notify. Thank you for your understanding.

2 Likes

Thank you @ChaosLabs and @LlamaRisk for providing your feedback, and community for participating in this proposal.

Now that BGD. Aave <> Sonic. Infrastructure/technical evaluation has been posted by @bgdlabs, and as mentioned in our previous comment, the current proposal has been escalated to ARFC Snapshot.

Vote will start tomorrow, thank you for your patience and we encourage everyone to participate.

4 Likes

After Snapshot monitoring, the current ARFC Snapshot ended recently, reaching out both Quorum and YAE as winning option, with 611.7K votes.

Therefore [ARFC] Deploy Aave v3 on Sonic has PASSED. Thank you everyone who voted.

Next step will be the publication of an AIP for final confirmation and enforcement of the proposal.

2 Likes

Hey @ACI ,

I appreciate the efforts put into this proposal, but I strongly believe the suggested Loan-to-Value (LTV) parameters need to be reconsidered. The proposed LTVs are significantly lower than those offered by competitors like Silo v2 and Avalon, which will make it hard for Aave to garner any sizable S liquidity.

Seeing how for example Avax has a LTV of 70% I don’t really see how we couldn’t up this to a 70% as S is the main driver of the Sonic ecosystem.

Higher LTVs attract more borrowers and increase platform utilization, a factor that has contributed to the success of other lending protocols. Platforms like Silo and Avalon have optimized their risk frameworks to allow higher LTVs while maintaining appropriate risk controls. If Aave sets conservative LTV parameters, it risks losing potential users to these competitors and our name alone won’t be enough to bridge that huge gap currently set in place the numbers in this proposal.

To ensure Aave remains competitive in the Sonic ecosystem, I propose re-evaluating the LTV numbers and aligning them more closely with what the market expects. I encourage the community to consider this adjustment before finalizing the deployment.

Looking forward to your reply or someone else at AAVE.

3 Likes

As Michigan Blockchain, we support deploying Aave V3 on Sonic. Sonic is developed by the creators of Fantom, who have a successful track record in blockchain innovation. Fantom achieved a peak TVL of $14.5 billion in 2021 which demonstrates the team’s capability to build and scale blockchain networks effectively. With 10,000 TPS and sub-second finality, Sonic is well-suited for DeFi applications, as transactions are efficient and rapid. Its EVM compatibility allows for seamless integration of Ethereum-based applications like Aave V3, so integration should not be difficult for existing EVM focused developers. Their fee monetization model provides developers with a sustainable revenue stream and this will attract developers that will build the unique apps that are going to attract blockchain users to bridge to Sonic, which can increase the liquidity in the Sonic ecosystem and can make this chain great for DeFi applications like Aave. Additionally, the Sonic Foundation’s commitment of $15 million in funding, $2 million in migration incentives, up to 50 million $S tokens, and $20 million in USDC demonstrates strong support for this deployment. Also, TVL on Sonic has been increasing rapidly, which shows clear user interest in the blockchain and highlights the potential of this blockchain, as TVL increased by a factor of ten in a month.

Sonic TVL Chart

Sonic’s TVL is already higher than some other blockchains onboarded to Aave V3, like ZKsync with $263m, Scroll with $143m and is very close to Gnosis with $335m TVL. We believe these factors make Sonic a strategic choice for Aave’s expansion. For the initial asset deployments, we agree with LlamaRisk on $WETH, $wS, and $USDC as those are all high liquidity assets that are not volatile enough to pose a risk. Other Sonic ecosystem tokens like $WAGMI need to be considered later as the top protocols on Sonic have not been established yet. For example, WAGMI was the top DEX on Sonic in terms of TVL on Jan 15 with $38m TVL but is currently down to $15m TVL on Sonic as of today, clearly losing liquidity to SwapX

WAGMI TVL on Sonic chart

which has a TVL of $24m as of today and the TVL is in an uptrend,

SwapX TVL on Sonic chart

so it is very early to list Sonic ecosystem tokens like WAGMI when there are no clear established protocols.

Written in 2/1/2025
-Kerem Dillice

3 Likes

With the passing of this ARFC, and in an attempt to be proactive and cut down the onboarding time for new collaterals, Origin Protocol has submitted a proposal to support Wrapped Origin Sonic (wOS) to the new Sonic instance on Aave: [TEMP CHECK]: Add support for Wrapped Origin Sonic (wOS) to Aave v3

2 Likes

$S LTV on AAVE: 35%:sob:
$S LTV on SILO: 75%:star_struck:

Better go use SILO instead of AAVE.:unamused_face:


1 Like

Is there a reason why this hasnt gone to AIP yet and Linea has?

1 Like