The Polkadot architecture is becoming explicit and complete, which should allow us, as parachain developers, to shift our focus from maintaining improvements in Polkadot dependencies (the substrate framework, cumulus and other), and move on to increasing the functionality of our parachain.
Starting with this article, I would like to share the tasks that the core project development team are ready to share with the community today.
In total, we have counted about 20 tasks that we are willing to implement this year. Some of them are full-fledged tasks, while the second part rather reflects the fact that the core developers devote time to this area, for example, supporting the academic community, conducting dev camps and developing Internet resources around the project.
Today I will share the development team plans related to task #1 - launching parachain on the Kusama network.
Leads: @ensrationis, @akru
Earlier, we presented a general vision of development in the Polkadot ecosystem - Robonomics Parachain on Kusama first, Robonomics Relay Chain on Polkadot is a vision. Now let's add more details.
On December 31, 2020, the Robonomics release "Rococo V1 support" for testing the parachain in the main Polkadot testnet Rococo v1 was published. During January - February 2021, we continue to improve the Robonomics code merging new commits associated with the restarts of Rococo Relay Chain. To test the operation of the Robonomics parachain, the developers keep our own fork of Rococo Relay Chain up to date, so the issue of connecting our parachain to the public network is rather a question of (1) public proof of the project's compatibility with the ecosystem, (2) the possibility of conducting tests with other projects from the ecosystem - Phala, Acala, Moonbeam, Darwinia etc - to search for collaborative implementations using the now available XCMP in Rococo v1.
Ahead of us are tasks related to participation in the auction of slots of the Kusama network. First, we need to figure out the implementation of this mechanism. Of course, we have been studying the theory for a long time, but the practice of participating in the auction will open up new tasks for the team. In any case, we will try to rehearse the auction and share the results with the community through a blog post.
In addition to participating in the auction, the developers are in the discussion of the following issues regarding the launch of the parachain on the Kusama network:
Of course, there are more questions, but these ones will most likely be interesting for the community in the first place and we think about them as a priority.
While speaking about the launch of the parachain, we must understand its main and special functions, which open up new possibilities of the Polkadot network to a certain group of users. Robonomics will provide the ability to manage smart devices connected to the Internet using the Robonomics Web Services (short: RWS) functionality, and we will also implement the functionality already tested on the Ethereum network for the emerging robot economy - smart contracts for the provision of automated services. Thus, Robonomics aims to help the entire Polkadot ecosystem increase the capabilities of each project separately towards deep integration with the IoT market.
To date, the possibility has already been implemented (1) to enable, disable and transfer the IoT task to the device / robot through the Robonomics parachain; (2) to receive device telemetry directly through the parachain or in a combination of IPFS + parachain for big data, and (3) a parachain subscription mechanism with guaranteed bandwidth.
Ahead of us is the implementation of such functionality as:
As you can see, tasks such as (3), (4), (6), (7) are of particular interest, since they imply integration with other parachains in order to utilize their useful functions in Robonomics.
Let us see the power of a common ecosystem of many specific projects!
The Polkadot architecture is becoming explicit and complete, which should allow us, as parachain developers, to shift our focus from maintaining improvements in Polkadot dependencies (the substrate framework, cumulus and other), and move on to increasing the functionality of our parachain.
It is important not to forget that the process of racing for a parachain slot is an internal development process, but most importantly - a specific functionality of a parachain; the main thing is to provide Robonomics functions to other parachains and implement the use of other parachains in your code. Then the entire ecosystem will be able to provide interesting functionality to users; functionality that will be extremely difficult to find outside of Polkadot.
In the next article I will talk about the Robobank project, the improvements of the Substrate based client of the Robonomics Network, as well as our plans for the development of Robonomics dapp and Robonomics Web Services.
ensrationis