Curvance AUSD 4626 and Rate Provider Review - Monad

[zekraken-bot]

Additional Contract Information

• 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

0x019002b4479a614a15e855c57fb1d7da8fc4a049

Asset contract address

0x8E94704607E857eB3E10Bd21D90bf8C1Ecba0452

audits

https://docs.curvance.com/cve/security/bug-bounty-and-audits

Protocol Documentation

The rate provider tracks the embedded yield within the Curvance 4626 vault

ERC4626 Asset contract address

0x8E94704607E857eB3E10Bd21D90bf8C1Ecba0452

ERC4626 Asset contract audits

https://docs.curvance.com/cve/security/bug-bounty-and-audits

ERC4626 Asset contract documentation

Curvance structures assets into isolated markets based on risk profile and liquidity depth. Each market operates with its own collateral caps and configuration parameters, allowing us to safely support leverage on assets like WETH, WBTC, and Monad LSTs without exposing the broader system to concentrated risk.

Link to passing fork tests

balancer/balancer-v3-erc4626-tests#111

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.