Skip to content

Avant savUSD Rate Provider Review on Monad #775

Description

@tiago-hansen

Additional Contract Information

  • Is the rate provider reporting for a stable coin/FX/Yield tracking?
  • Is the rate provider reporting a market rate?
  • Is a combined rate provider needed (i.e. wstETH in aave)?
  • Does this rate provider pertain to an ERC4626 contract?
  • If so, is the intention for this ERC4626 asset to be boosted?
  • If so, is the Buffer already initialized
  • If so, shall the underlying asset be used to add/remove liquidity in a pool if possible? (i.e. add USDC for waUSDC)
  • If so, shall the wrapped asset also be used to add/remove liquidity in a pool? (i.e. add waUSDC directly)

Network

monad

Rate provider contract address

0x55fD2ECa0761400A6e7780b6f333547fEb502Bb1

Asset contract address

0x9648db94f1e6b19e7d755585542981f97dc806c6

audits

Audited by Omniscia and Dedaub, with an ongoing OPSEC audit by Trail of Bits — https://docs.avantprotocol.com/security/contract-and-opsec-audits

Protocol Documentation

savUSD (Staked avUSD) is Avant Protocol's yield-bearing stablecoin. avUSD is backed ~1:1 by USDC and generates no yield on its own; staking avUSD mints savUSD, which accrues value through a continuously increasing savUSD/avUSD exchange rate (there is a 1-day cooldown when unstaking, during which no additional yield accrues). The rate provider (0x55fD2ECa0761400A6e7780b6f333547fEb502Bb1) reports this embedded yield by reading the on-chain "SAVUSD / AVUSD Exchange Rate" feed at 0x9F6ba235CFfFdEB32CfB38E3100D5f775bB1094E (Chainlink AggregatorV3 interface, 18 decimals). getRate() currently returns ~1.1849e18. Docs: https://docs.avantprotocol.com/

ERC4626 Asset contract address

No response

ERC4626 Asset contract audits

No response

ERC4626 Asset contract documentation

No response

Link to passing fork tests

No response

Terms and Conditions

  • The protocol to be integrated has been audited by at least one security firm or independent researcher.
  • If deployed, the contract & all involved downstream contracts are verified on etherscan.
  • The contract does not rely upon an EOA to supply any critical data (e.g., price).
  • If upgradeable, the contract's administrator is not an EOA.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions