Hi, Akropolis Community! It’s time for our development update!
In the previous months, we worked on the audit and deployment . You can find the token code in the repository, as well as the results of the audit https://github.com/akropolisio/AkropolisToken/tree/master/audit.
In addition, we are now conducting a vesting contract audit (repo) and in the near future, we will be able to allocate the tokens to the vesting contracts so that the overall process of vesting is transparent and fair.
Our development work on the AkroChain continues. Our efforts are nowadays directed towards the Akropolis node implementation and the implementation of the “cost of service” model. According to this model, there will be a set of different types of transactions in our parachain, and each type of transaction will have a certain “cost of service” fees. The Cost of service will be defined via voting of AKRO tokenholders and its set up to guarantee the best ratio between the security of network and cost of transactions.
Another direction of our work is the implementation of staking. Our research is focused on how to optimally implement the functionality of the selection of validators, delegation of tokens and distribution of remuneration.
Besides working on the node and staking, the work on User Interface implementation so that users can interact with our network has started. In a not so distant future, we’ll reveal the design of the portal for staking and wallet. This means that in Argos (upcoming) release you can make transactions in AkroChain through a simple and convenient web interface, as simple as using most DeFi applications on Ethereum.
While we were working on the Akropolis node, we encountered a problem: the frequent updates to Substrate, changing dependencies led to the fact that maintaining the nodes was rather labor-intensive.
Therefore, we decided to create a tool that would automate DevOps for validators and parachain and dApp developers. As this issue is common to all the parachains, so we decided to make a universal tool for the Polkadot ecosystem. There are 3 possible use cases/users of PolkaHub:
- Parachain developers can use our Solution for building serverless public node infrastructure.
The simplest way to deploy it is with the git command. The parachain developer publishes to PolkaHub information about his parachain — the IP address of the public node, the API specification, and so on, then all the information needed for dApp developers will be in one place, simplifying the onboarding of dApp developers to parachains.
- dApp developers can use the public node infrastructure powered by PolkaHub: find information, connect to public node, call contracts and so on via RPC/API/Sockets.
Currently, Polkadot telemetry shows a large number of testnets. But there is no single hub in which you can find out information about required network version, its specification, ip address to connect to it. If you are a dApp developer, you would have to spend a lot of time gathering all this information.
- Validators can use PolkaHub for easy node deployment.
The buildpack prepared by parachain developers will be loaded into our marketplace. Anyone who wants to become a validator can enter the marketplace, choose an image and deploy it. That way we create an abstraction layer for node deployment for validators.
Below is our updated roadmap, where you can see our Akropolis Chain milestones. As Substrate evolves, this roadmap will do the same. Additionally, as we are currently building a chain to bid for a parachain slot in Polkadot, and the protocol is not launched yet, so our development roadmap will also be changing due to this. Because of that everything is highly dependent on Polkadot roadmap and ecosystem development.
Thank you for your ongoing support — we could not have done this without our community. And stay tuned for more updates!