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

Represent Pool Proxy as ERC4626 #46

Open
gabririgo opened this issue Mar 12, 2024 · 0 comments
Open

Represent Pool Proxy as ERC4626 #46

gabririgo opened this issue Mar 12, 2024 · 0 comments

Comments

@gabririgo
Copy link
Contributor

gabririgo commented Mar 12, 2024

Summary

Pool Proxy inherits ERC4626 public methods and implements them according to Rigoblock specs.

Motivation

ERC2646 provides a standard for vaults that hold tokens. While it is designed for interest-bearing vaults using one token, we could amend the Rigoblock Pool Proxy API to allow easier tracking by blockchain scanners, and possibly stats platforms. Not a top priority as its impact is limited. An interesting advantage is that we could use pre-audited code, therefore reducing the attack surface at the core protocol level.

Specification

TBD.

Rationale

To facilitate exposing smart pools' data on stats platforms, frontends, and blockchain scanners according to broadly accepted standards. To make use of more pre-audited code. the ERC-4626 standard also exposes some methods to withdraw and deposit a specific token in addition to burning and minting with the base token, which would make this RBIP a good complement to RBIP-36.

Notes

ERC-4626 standard
A sample implementation
Openzeppelin's ERC-4626

On ERC-4626 inflation attacks

A project using ERC-4626: website github

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

1 participant