Dear Community,
with this post we would like to give you "Behind the Scenes" insights into the daily work of the ONINO Development team and share with you how and on which features of the ONINO Blockchain and the ONINO Cloud Platform we are currently working and what is planned.
ONINO Cloud Platform
Cloud IDE for Smart Contract Development
We are currently working on a full-fledged code editor, or, Cloud IDE Integrated Development Environment) for the ONINO Cloud Platform, as known from local development environments such as Visual Studio Code.
This enables users to work with multiple code files at the same time if required and to structure them in folders.
We will also integrate our existing features, the Smart Contract Template Gallery and our AI Development Assistant, into the Cloud IDE so that you can easily create new files from template code and AI-generated code.
In this sprint, we created the necessary databases for saving files and folders, adapted our backend, and built a working first front-end version of the Cloud Code Editor. We also created a user-friendly design, which you can see below and which we are currently implementing.
In the future, we also plan to incorporate collaboration features so that several users can conveniently work together on the code of their project in the cloud IDE at the same time.
With the Cloud IDE feature, we want to make it possible to map the entire blockchain development process on the user-friendly ONINO Cloud Platform and unite all tools in it - including those for smart contract development.
ONINO Smart Contract API
We also worked on the ONINO Smart Contract API during this development sprint. Users will soon be able to create and manage their own API keys.
With this API key, users can then use the ONINO Smart Contract API to easily interact with their smart contracts and, for example, simplify the reading of data from and writing of data to their smart contracts.
In particular, we want to reduce the entry barrier to the blockchain world for Web2 developers, who often find it difficult to interact with smart contracts and are used to simple API integrations from other Web2 tools. In addition, we want to enable a much broader range of individuals and companies to integrate blockchain, as even legacy code systems, possibly written in programming languages that do not allow direct smart contract interaction, can easily interact with smart contracts via API calls using the ONINO API.
In this sprint, we implemented the necessary functionality for the creation and management of API keys and the secure storage of the keys in hashed format in our backend.
In addition, we have already built the fully functional API endpoint for reading data from smart contracts.
Over the next few weeks, we will build the other API endpoints, which will also make it possible to write data to smart contracts, among other things. You might legitimately ask yourself: how can our API write to smart contracts without you having my wallet? We have come up with two clever solutions for this, which we will be implementing in the coming sprints.
1. for test environments, our backend will create test wallets managed by us. This allows every developer to quickly develop prototypes on test networks and get started right away.
2. for production environments, we plan to integrate so-called "backend wallets". Here, users can create wallets via AWS or other cloud providers using so-called KMS (Key Management Systems), which make it possible to securely share and manage different wallets within the entire company with enterprise-grade security. All that remains to be done is to copy a key from this KMS and paste it into the ONINO Cloud Platform, and then you can interact with the ONINO API via professional company wallets.
ONINO Blockchain
The development of Sub-Chain functionality is a cornerstone of our efforts to provide customizable blockchain solutions. This feature allows for the creation of independent blockchains that are still connected to the ONINO Mainnet, ensuring security and integrity through a unique sequencer mechanism.
In the following, we want to give you an overview of what we are working on currently:
Customization and Isolation
Sub-Chains can be customized to meet specific project requirements, including custom consensus mechanisms, governance models, and transaction processing capabilities. This flexibility will allow projects to optimize their blockchain infrastructure for their specific use case without the overhead or congestion of the main network.
Privacy
We believe that a variety of industrial business cases will be implemented on private blockchains, raising the question of whether a private blockchain loses the inherent positive aspects of a public decentralized ledger. To address this, we are working on an implementation that uses zero-knowledge proofs to enable the deployment of private sub-chains on top of our public main chain.
Sequencer Mechanism
The connection between the Sub-Chains and the Main-Chain is facilitated by a sequencer, which can be seen as an additional layer between, ensuring that the state of transactions on Sub-Chains are periodically anchored to the Main-Chain. This mechanism provides an additional layer of security and integrity to the Sub-Chains while maintaining their operational independence in execution, while also allowing flawless interoperability between all Sub-Chains connected to the sequencer.
Network Stats Dashboard
Next to the Subchain functionalities, in this sprint we have developed a web dashboard to get direct insights on current network performance, usage, and costs. At first this dashboard is primarily for internal analytics purposes, but we will later also release it publicly for everyone to analyze ONINO’s network stats.
The team is currently working on implementing the first Sub-Chain directly on the ONINO testnet and improving our framework to enable developers all around the world to customize, deploy, and manage their unique Sub-Chains.
We appreciate your continued support and interest in ONINO! Stay tuned for further updates as we continue to push the boundaries of blockchain development and integration.