What is the KRNL Platform?
Last updated
Was this helpful?
Last updated
Was this helpful?
In short, the KRNL Platform is a dApp which connects to smart contract registries so that users can register more easily. It helps users to connect their wallets through interactive interfaces, browse kernels, and explore.
From the figure above, this is how the KRNL Platform works in a nut shell. It is a dApp that can call to smart contract registries from each category.
The first example would be when Tom and Jerry, an on-chain kernel provider and off-chain kernel provider respectively, try to register on the KRNL Platform. Metadata, like OpenAPI Specifications, function return types, and more, will all be registered on the Kernel Registry smart contract.
The next example is when Bob, who is a smart contract developer, has already deployed both his Token Authority and his ABCcoin minting smart contract. When Bob registers his smart contract on the KRNL Platform, his smart contract details will also be registered on the Smart Contract Registry smart contract.
Here's another example. A dApp developer, such as Alice, can register her dApp on the KRNL Platform. Similar to the above examples, metadata from her dApp registration gets stored on the dApp Registry smart contract.
At this current stage, all registries are on the Sepolia network.
The addresses of registry contracts can be found in the bottom-left corner of the KRNL Platform.
The reason why we are using registry smart contracts with kOS is because we aim for the goal of being a decentralized platform where users can easily register their kernels, smart contracts, or dApp via on-chain smart contracts.
It also leads to an architectural position for kOS where the KRNL node can access and use the metadata from calling the registry smart contracts. Read more in the following section for more details.
The following steps will occur:
The node receives an entry ID from the KRNL SDK
The KRNL node will get information of that entry ID from the dApp Registry
The fetched information from point 2 contains the smart contract ID
Comparing the smart contract ID in the Smart Contract Registry will give out the kernel ID(s)
At this point, the node will know the details of the kernel(s) from the kernel ID(s)
On the right side, we can see that the diagram looks similar to what you probably have seen on the page. It shows that when a user submits the executeKernels(...) request to the KRNL node, the node will fetch the metadata from registry smart contracts.
It is important to note here that the above process of a KRNL node fetching metadata from registries could be considered "step 1.5" on the page.
