Proposal: Add Support for STASIS EURO (EURS)

Governance New Asset
23

Hey Michael,

You are welcome.

The actual published contract code is documented. Check it out by the link (we use delegate calls from the main contract to route calls to it):

All interactions, in this case, must occur through the main token contract.

24

As a fellow European I also feel the need for a EURO-backed stablecoin (didn’t do my homeworks yet about EURS specifically but will take a look soon).

1 Like
25

Hi, sorry but your reply didn’t answer my questions, also your token contract looks very basic.

What are the fees parameters for and and and!
Thx for providing more information

26

Hey, no problem. The current implementation is located at the address above and there are no fees in it at all, you can see for yourself.

Next, the fact that the contract seems basis is okay. Apart from delegatedTransfer, our token does not need any special features, so everything is done as simply as possible to exclude the possibility of problems and vulnerabilities (reduce the attack surface). Hope it answers your question.

1 Like
27

Hi @STASISTeam

Thanks for this proposal

Could you please make sure your ARC covers all the important information as explicit in New Asset Listing - Governance

28

Hope to see this happen soon. No reason to let USD be the king of town. IIRC, a chainlink oracle reflecting the price of EURS in ETH is necessary for an AAVE listing. Is there one available?

29

Hello. We’re thrilled to get back to being fully armed!

Hey, Alex_BertoG.

STASIS team has checked the link you shared (New Asset Listing - Governance). Taking this into account, we have:

1. Created a Pull Request in AAVE protocol V2 to add token parameters:

in accordance with the following instruction:

Creating an asset listing proposal - Developers.

  1. We launched the deployment script and created 4 smart contracts:
  • Interest bearing aEURS: 0x7481238c3e812965DA1C04e396a31b81D904F29B
  • Variable Debt variableDebtEURS: 0x4637C6134516a5Ceb212F81CA396f99B03B00037
  • Stable Debt stableDebtEURS: 0x11c02A5c0A39485A1ecED23e19509fE75131da9c
  • Strategy Implementation for EURS: 0xDB163D7eb7850a015e4872551BE7A384ce901062.

3. Created an AIP Pull Request:

Add EURS to AAVE v2 by stasiscto · Pull Request #116 · aave/aip · GitHub.

With all the hard work done - our team wants to know the next steps to proceed.

Moreover, I would also like to clarify the following questions:

  1. According to the procedure (New Asset Listing - Governance), we need to upload the AIP to Snapshot to conduct the on-chain vote. Do we need to do this right now, before the actual AIP review took place?

  2. Following the specific instructions (New Asset Listing - Governance), we must have a Price Feed directly from Chainlink. Our team is currently negotiating with Chainlink, but it’s not available at the moment.

What should our team do next, given that we have not specified the Chainlink price feed addresses in the current token parameters?

Thanks. Looking forward to your answers.

1 Like
30

Hi @STASISTeam

Thanks for the update

It seems premature to work on the smart contracts before completing the ARC which is currently lacking key information. Please follow the template, which details the required information expliciting 10 questions to answer on the Template ARC Asset Onboarding - Governance

Furthermore, you need to follow the New Asset Listing - Governance, starting at the first step:

1) Proposing the asset via ARC process with 1.1) Risk Analysis of the token you’d like to see listed, with a link to a risk analysis methodology. Without risk analysis, it’s impossible to judge whether a token is fit for integration

Then continue with parameter suggestion as described in the guide. Only then does it make sense to proceed to the Snapshot and use it as a tool to understand which parameter configuration the Aave DAO prefers.

If the Snapshot is approved, it is time to implement the smart contracts following the community’s sentiment.

Aave smart contracts only operate with Chainlink’s price feed at the moment so you will need to continue working with Chainlink. If Chainlink cannot provide an oracle it may be that there isn’t sufficient liquidity to prevent price manipulation and that is problematic for integration into Aave

2 Likes
32

Hey @Alex_BertoG

Thanks for the detailed answer.

I want to clarify something: if we modify the ARC proposal, should we modify the original post as well or re-submit it?

33

Either work. I personally think it could be better to just modify it to avoid diluting information