KRNL Platform Guidebook
KRNL Platformkrnl.xyz
  • Introduction
    • Introduction
    • How Does kOS Work?
  • Setup
    • Getting Started with KRNL
    • Quick Start (CLI)
    • Quick Start (Online IDE)
      • Quick Start (Remix IDE)
      • Quick Start (Atlas IDE)
    • create-krnl-app
    • Platform Registration
  • Kernel
    • What are Kernels?
    • Kernel Registration
      • Kernel Registration (on-chain)
      • Kernel Registration (off-chain)
    • Supported OpenAPI (Off-chain Kernel)
    • Staking
  • Smart Contract
    • Steps for Smart Contract Developers
    • Choosing Kernel(s)
    • Token Authority
      • What is a Token Authority?
      • How to Build a Token Authority?
      • Generic Token Authority
      • How to Deploy a Token Authority on Oasis?
    • Decoding Kernel Responses in Solidity
    • How to Integrate Your Smart Contract with kOS?
    • Smart Contract Registration
  • DApp
    • dApp Registration
    • KRNL SDK Installation
    • Usage
    • KRNL Node RPC
  • Miscellaneous
    • Overview
    • What is the KRNL Platform?
    • What are You Trying to BUIDL?
    • Smart Contract Fundamentals
      • Why Do I Have to Register a Smart Contract?
      • How to Deploy a Smart Contract?
    • Recommended Kernels List
  • Helpful Resources
    • New to Web3?
    • Dictionary
    • Testnet Faucets
    • How to Get Etherscan API Key?
  • Litepaper
    • Litepaper
      • Overview
      • Problem Statement
      • Current State Does Not Solve the Problem
      • Introducing Kernels
      • Ecosystem of Kernels
      • The KRNL Operating System (kOS)
      • Decentralization and Security Considerations
      • Use Cases for KRNL
  • Appendices
    • FAQ
    • Bounty Program
    • Social Medias
    • Thank You
  • Workshop
    • KRNL Workshop
    • Speed's Workshop
Powered by GitBook
On this page
  • 1. A dApp sends a request to the KRNL node
  • 2. The KRNL node sends a request to the list of predefined kernels
  • 3. Each kernel will be executed until all selected kernels are completed
  • 4. Responses from kernels will be sent back to the KRNL node
  • 5. The node sends received responses to Token Authority
  • 6. Token Authority examines the responses and passes them back to the node
  • 7. The KRNL node provides responses from Token Authority to a dApp
  • 8. A dApp is able to submit a transaction to a smart contract

Was this helpful?

  1. Introduction

How Does kOS Work?

PreviousIntroductionNextGetting Started with KRNL

Last updated 28 days ago

Was this helpful?

This page is dedicated to illustrating how the KRNL Operating System, kOS, works when a dApp submits a transaction to a smart contract, and how smart contracts receive responses from kernels.

Keep in mind that figures are high-level concepts.


1. A dApp sends a request to the KRNL node

2. The KRNL node sends a request to the list of predefined kernels

3. Each kernel will be executed until all selected kernels are completed

4. Responses from kernels will be sent back to the KRNL node

5. The node sends received responses to Token Authority

6. Token Authority examines the responses and passes them back to the node

7. The KRNL node provides responses from Token Authority to a dApp

8. A dApp is able to submit a transaction to a smart contract

A smart contract will receive the responses from the selected kernels and Token Authority.

It will then make the final decision whether the transaction should go through (succeed) or not (failure).

Step 1: dApp to KRNL node
Step 2: KRNL node to list of kernels
Step 3: Kernels are executing
Step 4: Kernels send responses to the KRNL node
Step 5: The KRNL node sends kernels' responses to TA
Step 6: TA sends back to KRNL node
Step 7: KRNL node to dApp
Step 8: dApp submits transaction to smart contract