Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anzem sUSDz Rate Provider #271

Open
4 of 7 tasks
Zen-Maxi opened this issue Feb 10, 2025 · 0 comments · May be fixed by #278
Open
4 of 7 tasks

Anzem sUSDz Rate Provider #271

Zen-Maxi opened this issue Feb 10, 2025 · 0 comments · May be fixed by #278
Assignees

Comments

@Zen-Maxi
Copy link
Collaborator

Type of Smart Contract

Rate Provider

Additional Contract Information

  • Does this rate provider pertain to an ERC4626 contract?
  • Is the intention for this rate provider and ERC4626 asset to be utilized as in a buffer for a boosted pool?
  • If the asset uses an ERC4626 interface, are there any known withdraw timelocks or fees related to entry or exit to the underlying asset?

Type of Smart Contract (if Other)

No response

Contract Source Code

https://basescan.org/address/0x6f2c300878ac028bc0Bc2cF38217396DF163fF42#readContract

Asset Contract Source Code

https://basescan.org/address/0xe31ee12bdfdd0573d634124611e85338e2cbf0cf#code

Additional Links

No response

Protocol Documentation

https://docs.anzen.finance/

Protocol Audits

https://docs.anzen.finance/developer-resources/audits

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.

Additional Comments & Clarifications

No response

@brunoguerios brunoguerios linked a pull request Feb 12, 2025 that will close this issue
@brunoguerios brunoguerios linked a pull request Feb 12, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants