Here the things I would like to see. It might be biased as I am heavily distracted by the old documentation hub and never digged deep into the documentation stuff again. But I think there is still lot of room for improvement.
Docs
- make it as easy as possible for users to find the docs they need
- information about protocol features
- smart contract development, Sophia
- docs + tutorials
- SDKs
- …
- avoid duplication and inconsistencies
- verify that links are working and not broken or pointing to wrong/outdated material
Javascript SDK
- provide examples and always keep them up to date
- also shapes for different frameworks with a sample contract which can communicate with the Superhero extension
- introduce types (Use jsdoc convetions to enable autocompletion for editors · Issue #736 · aeternity/aepp-sdk-js · GitHub)
- cc @icarus
Smart Contract development
- language server to enable syntax highlighting and other features for multiple editors ([Postponed] Language Server + VSCode Plugin for Sophia)
- I saw that somebody already started implementing it but somehow this activity wasn’t continued
- verify compiled contracts against the bytecode of the deployed contract
- is this possible now? haven’t checked for a while
- everything @bruteforce.chain mentioned
State Channels
- Mobile Client ([Withdrawn] State Channel mobile client)
- I personally think that this is crucial in order for state channels to be used
General
- expose internal transactions to avoid having to build a workaround using events to track activities that happen within contract calls
- I think this is now already the case right? https://github.com/aeternity/aeternity/pull/3353
- as we are planning a relaunch of https://aenalytics.org and making use of the new middleware indaex (GitHub - aeternity/ae_mdw: Aeternity Middleware in Elixir) it would be great to have more transparency and updates what’s being worked on there. I opened a bunch of issues on Github and I am actively communicating with @karol.chain when I face problems. most things are already in place but there are some bugs and we also have feature requests (e.g. searching, filtering/sorting, statistics, …)
- I know you are working hard on this but it seems like it takes ages until it’s “feature complete”
- I see that you are working heavily on the AEX-9 topic right now and we are not in the position to influence this but we think there are more basic things that should be covered first
- also I need to know how to make a production release of the aeternity node that should include one or multiple plugins using ae_plugin (GitHub - aeternity/ae_plugin: Simple setup-based AE node bootstrap app for plugin development)
- I asked this already here: Ae-image-builder / node and plugins and I think the current way the Dockerimage of the middleware is handling this is not the best way to do it
Demos
- Oracle Pricefeeds
- Simple Prediction Market
- Generalized Accounts examples
- Usage of PayingForTx as soon as it’s possible
æpps
- token-bridge (ERC20 <-> AEX-9)
- swap-application to trade AEX-9 tokens