Developer tools (SDKs, AEstudio, AEproject & other libraries)
Documentation, including developer tutorials & samples
and all the general activities happening around all that stuff, including bounties!
We know that communication in that regards wasn’t good in the past months so I just decided to open this thread. It can be used from everyone to ask questions, start discussions and maybe even provide information about their self-developed tools or æpplications. The goal is to have liquid conversations with everybody who is interested in helping to improve the developer and user experience on æternity.
The next post will give you a brief overview about what activities have been started, finished and what can be expected in the upcoming weeks and months.
This thread is NOT intended to be used for discussing Hyperchains or other core development related things!
If there are overlaps in several topics in terms of that we need sth. to be improved/changed in the core protocol then we can of course discuss that here. But generally we should focus on everything else here
As many that follow the project closely know we had some trouble around different tools when the Iris hardfork was introduced in June. It definitely wasn’t a smooth process, everybody is aware of that and we will make sure that this kind of trouble will never happen again. There is nothing more to tell you about this and we better forget that as soon as possible and look into the future - which is hopefully bright
Updating & improving examples & documentations
In this area I am mainly involved right now and there is still lot’s of room for improvement where I will continue to work on.
During testing we raised various issues in the JS-SDK. Additionally we want to provide examples how to make use of delegation signatures in smart contracts (this would basically allow to build an AENS marketplace if anybody is interested in that). Unfortunately there are still some enhancements in the SDK required to finally get this working like expected, see following Pull-Request:
There is still work ongoing regarding documentation-hub and tutorials in general. I know it is not where we would like to see it but we constantly improve it. Next week I will shortly update the documentation-hub and link to all important places before I am finally able to introduce a useful submodule structure there that allows to explore anything you need via the documentation-hub. Follow the progress of this here:
When v9.0.0 is finally released you will be able to play around with new new introduced tx-type PayingForTx which allows to easily perform meta-transactions and pay the tx-fee for transactions of other people. We are really excited about that feature as it provides lots of possibilities. Read more about that in the docs:
Some people might have noticed that @karol.chain stopped working on the middleware backend quite some time ago. Meanwhile we are happy to have @cryptodao21ae and @sborrazas as new contributors that constantly improve the software together with @wj2016 and @Arthur. The development in that area is really getting on speed right now. Check out the following repo to follow the progress:
In the middleware frontend (https://explorer.aeternity.io/) we haven’t seen lots of progress during the past months. Most recently @atanaskrondev.chain started to contribute here and already solved some issues. Also I have managed and prioritized the project board which can be seen here:
This is/was kind of a pain for us and for people using the library - we know that! It is definitely a tool that can be used to easily get started. If we further want to improve it we know that there is a big refactoring required and personally I am not sure if it is worth the work - given the minimal benefit it provides right now. I want to hear the opinion of the devs out there! What do you think about AEproject in general?
Any opinions about that?
This is probably the most anticipated topic of every developer out there that wants to build cool æpps with Sophia smart contracts.
We had that discussion already several times in the past. But this time I am confident that it will be addressed in the near future.
In fact we want to provide a devmode for the node. We need developers to be able to have the best experience when developing smart contracts on æternity and therefore we need several features. We probably won’t be able to provide such a smooth experience like you have for example with Ganache in the first place, but we are in active discussions how to solve this in the best way possible.
If anybody has good ideas in that area feel free to join the discussion here or directly on GitHub. We need to get this topic done right (!)
Due to the fact that there is currently no active development of the aepp-sdk-python ongoing we decided to rewrite the faucet in Node.js. The currently deployment is still running the old implementation.
The reason for that is that there is currently activity regarding SRE ongoing. In the foreseeable future we will have a new k8s environment where we can host applications. For everybody interested in that area just have a look hat following repos to see what’s going on there:
I know e.g. that @genievot is working on the token-migration bounty
Since we have new cryptographic primitives included in the virtual machine since Iris we thought about providing a bounty to build a similar application like https://tornado.cash on Ethereum. Any opinions about that?
What does the community want to see? What kind of bounties would you like to see being worked on? Please give us some input here.
Well, for a long time nothing happened here. And I can tell you there is still not much going on right now. BUT I know that @zkvonsnarkenstein.chain is currently working on a proposal for a NFT standard on æternity which I personally am very excited about
I am looking forward to discuss that standard. We will of course also clean up that repository and revive the AEXpansions repository.
More information about the NFT standard here:
Outlook / Roadmap
I can tell you that lot’s of other things are ongoing in the background and we will try to get together in the near future to define a roadmap for improving the developer experience. If we have it we will - of course - share it with you here in this thread!
For example we have a request to get MultiSig support in the Wallet and I personally want to see more improvements in the Sophia section. We need a LSP implementation and introduce syntax highlighting in several tools to make Sophia code e.g. more readable on GitHub and in our docs. There is also a desire to revisit the state channel demo again.
We will try to provide a roadmap in that area as soon as possible. But we want to do it right and take the time needed to define it. We won’t rush in everything at once. We (finally) want to get things done!
if YOU have specific needs please share your thoughts with us!
NOW is the time to do that!
I hope I didn’t forget anything
in the end I want to thank everybody that helps improving the æcosystem! =)
We are thinking about replacing the documentation hub with this website. Any thoughts on this? Would love to get your opinion here. Personally I never really liked the documentation hub and it’s providing me headaches. For docs generally we have dedicated sites, see below.
Also currently all docs that have currently a dedicated documentation are served with the repository name under the official website url, see:
for any update to the documentation it is required to commit on github and open a pull-request.
to be honest I just don’t like the current documentation hub and I think having a definite link-list like in awesome-aeternity is way better and easier to maintain.
we have several components (protocol spec, node, sophia sdk, …) that all have their own dedicated documentation (see above) - so there is no need to maintain everything again in the documentation hub in one place. we could somehow integrate it and we thought about it but it’s in the end IMO not worth the work.
=> these dedicated documentations are meanwhile set up in a way that they are automatically built and published after each merge and for js-sdk and sophia docs we also have versioning in place (from now on)
we generally aim to improve READMEs on various repositories. and in the end - if something is not clear - you can always ask in the forum and you will get an answer and we can improve the README accordingly.
IMO we should take down documentation hub, improve READMEs where needed (proactively and on request basis) and use the awesome-aeternity repo to link to all the important stuff in the ecosystem.