JS-SDK
We finally released v9.0.0 and subsequently v9.0.1 after we identified some unwanted behavior that came up when initializing the Channel Stamp in the Universal Stamp.
Thanks to @icarus this issue was identified very quickly as he updated the aepp-boilerplate-vue template in the aeUnited bounty program.
We encourage everybody to update to the latest version of the JS-SDK!
Highlights
- The latest release finally supports the new tx-type
PayingForTxwhich allows to easily use meta-transactions. If you are a service (e.g. custodian) or a game developer you can make use of this to cover the gas costs of your users in a convenient way. Read more about this here: - Avoid the deposit trap by default:
- If you would have provided a
depositvalue on contract deployment these AE tokens would currently be locked. We now enforce in the SDK that this cannot happen. - The idea behind this deposit value was originally to e.g. require some AE for contract deployments in general and to be able to get those AE back if the contract is destroyed and removed from the state tree if not needed anymore. But this has never been implemented.
- More info: enforce zero value for `deposit` param of ContractCreateTx · Issue #1232 · aeternity/aepp-sdk-js · GitHub
- If you would have provided a
-
Account is not required anymore now for initializing the Universal stamp
- This has unfortunately been introduced in some earlier release and is now fixed.
- Currently there is a console warning for this but we decided to remove that already. This will be reflected in a future release.
- More info: account is required to use the `Universal` Stamp of the SDK · Issue #1224 · aeternity/aepp-sdk-js · GitHub
- We changed the default gas limit value to
25000- Lot of discussions have been ongoing here as the core team was also working on fixing some tx-pool issues.
- More info: reconsider default gas limit / improve docs for contract related tx's · Issue #1267 · aeternity/aepp-sdk-js · GitHub
What’s coming?
- The absolute Number 1 priority right now is to get the calldata-lib integrated into the JS SDK. By finalizing this task we will be able to remove the hard dependency to the http compiler. In theory a developer could completely get rid of the http compiler if he decides to generate the ACI independently (e.g. with the sophia cli). Of course it will still be possible to use the SDK to get the ACI by providing the sourcecode of a contract for everybody that wants to do it this way.
- Next step is to support all Sophia types
- We also aim to simplify the wallet connection and make the life easier for aepp developers (highly desired by @nikitafuchs.chain
):
- If all of this is done we want to think about introducing TypeScript in the whole SDK and get rid of the Stamps:
Sophia development
- We made some update updates to AEstudio:
- Using
v9.0.1of the JS-SDK - Introduced links to the explorer
- Using
- We also updated the old contracts editor which can now be used again:
MDW-Backend
Lot’s of things happening here. It’s best to check GitHub and the recent releases.
There is also a release-please bot now that automatically prepares the releases including release notes for all changes in active development, see:
MDW-Frontend
We finally got some drive here, too. There are already some improvements there - especially the account page and display of AEX-9 tokens. Unfortunately the latest state isn’t released yet. Expect some further news about the explorer in the near future
We also recently introduced release-please here now, see:
AMM / DEX (“Uniswap clone”)
Here we also made a lot of progress on contract development. The repository is still not public but the AMM also has a high priority. The good thing here is that we can analyze and improve our contract development tooling with this project. There are lots of tests that need to be covered and currently it’s very difficult to be productive with the status quo of the devtools. It’s most important for us now to sort the productivity issues out.
Be assured to get some updates here in the near future. On contract level we are almost done but of course we need to investigate what’s needed to do in the frontend to provide the same user experience like people are used to with e.g. Uniswap or other AMMs out there.
Bounties
This is ongoing and we plan to introduce new bounties in the near future. If you think you can help us and there is a missing bounty for that please let us know! 
@VitalJeevanjot migrated the current token-migration backend to Node.js (currently in review) and @icarus finished the bounty to update the aepp-boilerplate-vue (see above).
Bounties we can currently imagine to additionally provide in the near future:
- Introduce Sophia Syntax support
- Implement a Sophia Langague Server Protocol (LSP) and at least one client implementation e.g. for VSCode
Closing words
Not sure if I forgot sth. important. For the Superhero Wallet we will also provide positive news in the near future - stay tuned!
If you have any questions or suggestions let us know and/or create an issue in the corresponding Github repository.
One additional thing:
- We signed up for the new GitHub Issues Feature and plan to use this to better manage our tasks and to be more transparent to the community in general.