Kaia Improvement Proposals (KIPs)

The goal of the KIP project is to standardize and provide high-quality documentation for Kaia itself and conventions built upon it. This repository tracks past and ongoing improvements to Kaia in the form of Kaia Improvement Proposals (KIPs). KIP-1 governs how KIPs are published.

The status page tracks and lists KIPs, which can be divided into the following categories:

• Core KIPs are improvements to the Kaia consensus protocol.
• Networking KIPs specify the peer-to-peer networking layer of Kaia.
• Interface KIPs standardize interfaces to Kaia, which determine how users and applications interact with the blockchain.
• KCTs specify the various token standards in Kaia.
• SDKs specify software developer kits and its architecture to support Kaia.
• Application specify application layer standards, which determine how applications running on Kaia can interact with each other.
• Meta KIPs are miscellaneous improvements that nonetheless require some sort of consensus.
• Informational KIPs are non-standard improvements that do not require any form of consensus.

Before you write a KIP, ideas MUST be thoroughly discussed on Kaia Research - TBD. Once consensus is reached, thoroughly read and review KIP-1, which describes the KIP process.

Please note that this repository is for documenting standards and not for help implementing them. These types of inquiries should be directed to the Kaia DevForum - TBD. For specific questions and concerns regarding KIPs, it's best to comment on the relevant discussion thread of the KIP in https://github.com/kaiachain/kips/issues.

Preferred Citation Format

The canonical URL for a KIP that has achieved draft status at any point is at https://kips.kaia.io/. For example, the canonical URL for KIP-1 is https://kips.kaia.io/KIPS/kip-1.

Consider any document not published at https://kips.kaia.io/ as a working paper. Additionally, consider published KIPs with a status of "draft" or "last call" to be incomplete drafts, and note that their specification is likely to be subject to change.

Build the status page locally

Install prerequisites

1. Open Terminal.

2. Check whether you have Ruby 3.1.4 installed. Later versions are not supported.

   ruby --version

3. If you don't have Ruby installed, install Ruby 3.1.4.

4. Install Bundler:

   gem install bundler

5. Install dependencies:

   bundle install

Build your local Jekyll site

1. Bundle assets and start the server:

   bundle exec jekyll serve

2. Preview your local Jekyll site in your web browser at http://localhost:4000.

More information on Jekyll and GitHub Pages here.