JellySwap - AE Stablecoin Progress

[LiuYang.chain]

Nice works!

Is there a contract address of AES token?

So we can list AES token on aeknow.org.

[kraykov]

Not yet, only a testnet contract. Once there is a mainnet contract I will let you know.

[kraykov]

Update:

Here is the first? AEX9 token to ERC20 token transaction on the testnet. This is the stepping stone for launcing AES.

æternity Explorer

Thanks to @philipp.chain and @bruteforce.chain for helping on the way.

I guess, we’ll all be able to do this on Jelly Swap really soon.

[Albert]

This is a great idea. I am looking forward to the breakthrough of the aeternity blockchain in the field of DeFi.

[murt9000]

Very exciting project. I think a stablecoin on AE is really important for adoption. I’ll be following the teams progress!

[kraykov]

Update:

• The AEX9 packages are updated and are integrated in both JellySwap and Butler (the market making software). Internal testing is ongoing to swap AES to DAI/AE/ETH back and forth.
• The branding for AES is in progress - that includes logo, website and slogan

Two new issues are reported:

Internal server error when decoding result (RESOLVED)

Hey, I have an internal server error that’s coming from the compiler and I can’t identify. I’m using the JS SDK version 7.1.1 I’m broadcasting a transaction that makes a call to a contract on the testnet. The transaction is mined successfully, however the error is there. Error: Http request for https://latest.compiler.aepps.com/decode-call-result failed with status code 500. Status: Internal Server Error. Error data: "" Axios config: config: { url: 'https://latest.compiler.aepps.com/d…

Aeternal middleware concurrency?

I’m using the Aeternal Middleware to get past events and subscribe for new ones. The following case is so confusing and annoying. Broadcast a transaction with waitMined flag set to false - this will resolve the promise and give me as a result the transaction hash. Once the transaction is mined, the Aeternal emits a websocket event that the transaction is mined giving all the data, EXCEPT the one that’s needed to get the event data. In order to get the event data from the transaction I have to …

@AE TEAM - please help and fix those two from above for us

[tima_t]

You can check this medium post to see the big picture:
https://medium.com/jelly-market/aes-stablecoin-91bac074a4b3

[kraykov]

Hey guys.

Update on the progress:

• We have launched the multisig contract on the Ethereum Network: https://etherscan.io/address/0x6b7D6B1eaC0Ad801d225755F73cAFfF1FFeb8675

• We have launched the AES token on the AE mainnet: æternity Explorer

• Brand new logo:
  

• We have created a web page (desktop only for now) to track the total amount of AES tokens and total amount of holders of the token. The data is extracted from both the AE and Ethereum networks:
  https://ae-stablecoin-stats.herokuapp.com/ - cool domain will be given soon. Source of the webpage can be found here: GitHub - jelly-swap/ae-stablecoin-stats-page

• Currently there are 110 AES tokens backed by 110 DAI

Next steps:

• Integration in Jelly Swap and enabling AE/AES and DAI/AES trading.
• The stats page will be updated soon and you’ll be able to deposit DAI into the multisig contract and receive freshly minted AES tokens.
• AES integration in different apps? @lukaskywalker.chain @bruteforce.chain @CryptoTask @stoyan.chain @YaniUnchained ?

[CryptoTask]

awesome! btw i don’t understand the DAI/AES trading pair? Isn’t the idea that AES is pegged to DAI 1 to 1? Or i missed something?

[kraykov]

Due to the fact that getting DAI out of the multisig will require some time (multiple confirmations from multiple entities) then it will be faster and more convenient to just swap the AES for DAI instead of burning and waiting to receive the DAI from the multisig

[bruteforce.chain]

Nice work!

The issues you’ve reported in waellet are fixed and we will roll a quick release with those.

Regarding token integration I guess this really depends on the apps creators themselves and their business logic if any.

If you mean native support across different wallets - I guess this can be discussed/proposed and probably implemented.

[tima_t]

Here is the contract address:
ct_pqfbS94uUpE8reSwgtaAy5odGi7cPRMAxbjMyEzpTGqwTWyn5

Symbol AES

Decimals 18

[tima_t]

Link to the AES statistics.

Currently we have 110 AES in circulation backed by 110 DAI.

If someone wants to mint some AES you can contact me or @kraykov.

[kraykov]

Hey, you all can mint fresh AES by depositing DAI here: https://aes.jelly.market/ - you have to specify your AE address and the amount of DAI you want to deposit.

[tima_t]

Super, can we expect to have the update soon at least on firefox (I know that it takes some time for chrome :)).

Can’t wait to use my AES with waellet!

[bruteforce.chain]

Hey,

waellet v0.5.3 is already in the firefox store.

[tima_t]

I’ve tried it, works now on version 0.5.3
Thanks @bruteforce.chain

[tima_t]

Hey @bruteforce.chain are we expecting update on the waellet extension for the AE tokens support next week?

We still have some issues with AES - most important AES transfers and other small things added in github as issues.

People that have minted some AES cannot transfer them to other addresses.

Thank you in advance

[bruteforce.chain]

Yes, we are investigating the issues on waellet side.

[tima_t]

Hey, guys.

Here we have a brief intro video to AES.
How does it work, Why are we building it and potential use cases.

You can share it with everyone in the AE community who is interested and mint some AES