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

EIP-4626: Tokenized Vault Standard #3393

Closed
pcaversaccio opened this issue May 4, 2022 · 1 comment · Fixed by #3171
Closed

EIP-4626: Tokenized Vault Standard #3393

pcaversaccio opened this issue May 4, 2022 · 1 comment · Fixed by #3171

Comments

@pcaversaccio
Copy link
Contributor

pcaversaccio commented May 4, 2022

Motivation

EIP-4626 introduces a standard API for tokenized Vaults representing shares of a single underlying ERC-20 token. This standard is an extension of the ERC-20 token that provides basic functionality for depositing and withdrawing tokens and reading balances.

Reference Implementations

  • See Solmate ERC-4626: a minimal and opinionated implementation of the standard with hooks for developers to easily insert custom logic into deposits and withdrawals.

  • See Vyper ERC-4626: a demo implementation of the standard in Vyper, with hooks for share price manipulation and other testing needs.

@Amxx from OpenZeppelin has already opened a draft PR currently here. I essentially opened this issue in order to track the development for anyone searching for this new ERC-4626.

@Amxx
Copy link
Collaborator

Amxx commented May 4, 2022

Hello @pcaversaccio

Providing an implementation of ERC4626 is in our roadmap for the next release. We want our implementation to be modular/overridable, so we still have tests to do in that regard.

It's one of our priorities right now. Please be a little patient, it's coming!

@frangio frangio mentioned this issue May 4, 2022
4 tasks
@Amxx Amxx closed this as completed in #3171 Jun 2, 2022
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.

2 participants