RiskProtocol / core-protocol

2 stars 0 forks source link

Find EIP-4626-expecting assets management apps and make sure they can work with our tokens #27

Closed mz7mz7mz7 closed 1 year ago

mz7mz7mz7 commented 1 year ago

Develop proof of concepts demonstrating it

jiokeokwuosa commented 1 year ago

Our dev tokens won't be fully compatible with platforms expecting only EIP 4626 tokens because ERC 4626 standard supports only one dev token(the token of the token factory contract) which is the what is given in exchange for the underlying token during deposit but in our use case we are working with two different dev tokens that are not the ERC 4626 token. -->https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/extensions/ERC4626.sol and https://eips.ethereum.org/EIPS/eip-4626

mz7mz7mz7 commented 1 year ago

https://ethereum-magicians.org/t/eip-4626-yield-bearing-vault-standard/7900

mz7mz7mz7 commented 1 year ago

We addressed the same requirements by implementing compliance tests for 4626 standard.