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

Create a specification and a base implementation for CW-4626 #22

Open
aesmonty opened this issue May 24, 2022 · 3 comments
Open

Create a specification and a base implementation for CW-4626 #22

aesmonty opened this issue May 24, 2022 · 3 comments

Comments

@aesmonty
Copy link

TLDR

The goal is to adapt the EIP-4626 standard for vaults and interest-bearing tokens to CosmWasm

Background

The EIP-4626 (https://eips.ethereum.org/EIPS/eip-4626) is a standard for tokenized vaults, with the goal of increasing composability between DeFi apps, while providing a more secure and standardized interface.

Motivation

Vaults are commonly implemented in a wide range of Defi applications such as lending markets, yields aggregators, etc. These vaults are normally implemented as yield-bearing tokens and should conform with the CW20 as well. Given how widespread their use is, it would be very helpful to adopt a shared interface of this "Defi lego", to improve developer experience, forward compatibility, and security.

Next steps

If this CW standard is deemed to be useful and we agree on a high-level spec, I can bootstrap the efforts and lead the implementation. It'd be great to do this collaboratively, so any help or contributor is more than welcome :)

@Jammyaa
Copy link

Jammyaa commented Jun 8, 2022

Hi, I think it is interesting and necessary to bring DeFi smart contract standards to Cosmwasm. So, we should start at CW4626.

@ethanfrey
Copy link
Member

ethanfrey commented Jun 17, 2022

I see the purpose of a standard reference for such logic.

cw-plus is defined for a basic set of contracts that are production ready and serve as references for common actions. But is not intended to implement every use case.

We also created the cw-tokens repo for many more extensions and that would be a great place for such a token contract. If you make a PR for an implementation, I am happy to get it reviewed.

@ethanfrey
Copy link
Member

Again, I would move this issue to the other repo. Happy to see contributions from the community there

@ethanfrey ethanfrey transferred this issue from CosmWasm/cw-plus Aug 15, 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

No branches or pull requests

3 participants