Skip to content
This repository was archived by the owner on Oct 25, 2026. It is now read-only.
This repository was archived by the owner on Oct 25, 2026. It is now read-only.

Blueberry (Curvance) blbAUSD RP & ERC4626 Review on Monad #802

Closed

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

0x497BDBc39B9f70b7CE781cc74e45E1cB897843C0

Asset contract address

0xC2ddc1004CA0d6cC4bFd1dCD03Dcf855bED8E670

audits

https://docs.blueberry.garden/advanced/contracts-and-audits

Protocol Documentation

https://docs.blueberry.garden/ — Blueberry ERC4626 vault on Monad; yield comes from the underlying Curvance AUSD market.

ERC4626 Asset contract address

0xC2ddc1004CA0d6cC4bFd1dCD03Dcf855bED8E670

ERC4626 Asset contract audits

Blueberry: https://docs.blueberry.garden/advanced/contracts-and-audits · Curvance (yield source): https://docs.curvance.com/cve/security/bug-bounty-and-audits

ERC4626 Asset contract documentation

https://docs.blueberry.garden/

Link to passing fork tests

balancer/balancer-v3-erc4626-tests#149

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.

Activity

  1. added a commit that references this issue on Sep 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions