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
  • Prerequisites
  • What's Next?

Was this helpful?

  1. DApp

dApp Registration

PreviousSmart Contract RegistrationNextKRNL SDK Installation

Last updated 8 days ago

Was this helpful?

Prerequisites

  • Read more about smart contract .


In order for dApp developers to be able to use kernels, they have to register through our platform dApp registry page.

Once you entering this page, you can choose the registered smart contract which you like to do the transaction within your dApp.

After selecting the registered smart contract, the list of selected kernel(s) will be shown in the picture above. It also shows the cost per query that users of your dApp will have to pay per one transaction. Press Activate if you wish to continue.

The screen will be loading and this successful window will be shown in the figure below.


After registering, you can see the details of parameters which need to be used within your dApp.

Entry ID and Access Token will be used in your dApp through KRNL SDK, as well as kernel Payload.

The below attached picture is the example of kernel Payload which will have to be filled on dApp. This payload is the parameters which will be sent to kernels when your dApp makes transaction to the selected smart contract. It is recommended to explore more about the details of the payload for each kernel through their website or documents.


What's Next?

You may visit this page for bootstrapping dApp template.

You may deploy your own smart contract. Follow this guide to deploy your smart contract.

here
create-krnl-app
here
Cover

Register Your dApp