kaiachain · praveen-kaia · Jun 24, 2024
@@ -20,7 +20,7 @@ jobs:
           PERSONAL_ACCESS_TOKEN: ${{ secrets.CLA_PERSONAL_ACCESS_TOKEN }}
         with:
           path-to-signatures: "${{ github.event.repository.name }}/signatures/version1/cla.json"
-          path-to-document: "https://gist.github.com/e78f99e1c527225637e269cff1bc7e49" # Klaytn Gist
-          branch: "master"
+          path-to-document: "https://gist.github.com/kaiachain-dev/bbf65cc330275c057463c4c94ce787a6" # Kaia Gist
+          branch: "main"
           allowlist: dependabot[bot]
           remote-repository-name: ${{ secrets.CLA_REPOSITORY }}
@@ -1 +1 @@
-kips.klaytn.foundation
+kips.kaia.io
@@ -1,12 +1,12 @@
 
-ATTENTION! If you would like to submit an KIP and it has already been written as a draft (see the [template](https://github.com/klaytn/KIPs/blob/master/kip-template.md) for an example), please submit it as a [Pull Request](https://github.com/klaytn/kips/pulls).
+ATTENTION! If you would like to submit an KIP and it has already been written as a draft (see the [template](https://github.com/kaiachain/KIPs/blob/main/kip-template.md) for an example), please submit it as a [Pull Request](https://github.com/kaiachain/kips/pulls).
 
 If you are considering a proposal but would like to get some feedback on the idea before submitting a draft, then continue opening an Issue as a thread for discussion.  Note that the more clearly and completely you state your idea the higher the quality of the feedback you are likely to receive.
 
-Keep in mind the following guidelines from [KIP-1](http://kips.klaytn.com/KIPs/kip-1):
+Keep in mind the following guidelines from [KIP-1](http://kips.kaia.io/KIPs/kip-1):
 
 > Each KIP must have a champion - someone who writes the KIP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The KIP champion (a.k.a. Author) should first attempt to ascertain whether the idea is KIP-able. Posting to the the Protocol Discussion forum or opening an Issue is the best way to go about this.
 
-> Vetting an idea publicly before going as far as writing a KIP is meant to save the potential author time. Asking the Klaytn community first if an idea is original helps prevent too much time being spent on something that is guaranteed to be rejected based on prior discussions (searching the Internet does not always do the trick). It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will work for most people in most areas where Klaytn is used.
+> Vetting an idea publicly before going as far as writing a KIP is meant to save the potential author time. Asking the Kaia community first if an idea is original helps prevent too much time being spent on something that is guaranteed to be rejected based on prior discussions (searching the Internet does not always do the trick). It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will work for most people in most areas where Kaia is used.
 
-> Once the champion has asked the Klaytn community as to whether an idea has any chance of acceptance, a draft KIP should be presented as a Pull Request. This gives the author a chance to flesh out the draft KIP to make properly formatted, of high quality, and to address initial concerns about the proposal.
+> Once the champion has asked the Kaia community as to whether an idea has any chance of acceptance, a draft KIP should be presented as a Pull Request. This gives the author a chance to flesh out the draft KIP to make properly formatted, of high quality, and to address initial concerns about the proposal.
@@ -0,0 +1,121 @@
+Creative Commons Legal Code
+
+CC0 1.0 Universal
+
+    CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
+    LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
+    ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
+    INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
+    REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
+    PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
+    THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
+    HEREUNDER.
+
+Statement of Purpose
+
+The laws of most jurisdictions throughout the world automatically confer
+exclusive Copyright and Related Rights (defined below) upon the creator
+and subsequent owner(s) (each and all, an "owner") of an original work of
+authorship and/or a database (each, a "Work").
+
+Certain owners wish to permanently relinquish those rights to a Work for
+the purpose of contributing to a commons of creative, cultural and
+scientific works ("Commons") that the public can reliably and without fear
+of later claims of infringement build upon, modify, incorporate in other
+works, reuse and redistribute as freely as possible in any form whatsoever
+and for any purposes, including without limitation commercial purposes.
+These owners may contribute to the Commons to promote the ideal of a free
+culture and the further production of creative, cultural and scientific
+works, or to gain reputation or greater distribution for their Work in
+part through the use and efforts of others.
+
+For these and/or other purposes and motivations, and without any
+expectation of additional consideration or compensation, the person
+associating CC0 with a Work (the "Affirmer"), to the extent that he or she
+is an owner of Copyright and Related Rights in the Work, voluntarily
+elects to apply CC0 to the Work and publicly distribute the Work under its
+terms, with knowledge of his or her Copyright and Related Rights in the
+Work and the meaning and intended legal effect of CC0 on those rights.
+
+1. Copyright and Related Rights. A Work made available under CC0 may be
+protected by copyright and related or neighboring rights ("Copyright and
+Related Rights"). Copyright and Related Rights include, but are not
+limited to, the following:
+
+  i. the right to reproduce, adapt, distribute, perform, display,
+     communicate, and translate a Work;
+ ii. moral rights retained by the original author(s) and/or performer(s);
+iii. publicity and privacy rights pertaining to a person's image or
+     likeness depicted in a Work;
+ iv. rights protecting against unfair competition in regards to a Work,
+     subject to the limitations in paragraph 4(a), below;
+  v. rights protecting the extraction, dissemination, use and reuse of data
+     in a Work;
+ vi. database rights (such as those arising under Directive 96/9/EC of the
+     European Parliament and of the Council of 11 March 1996 on the legal
+     protection of databases, and under any national implementation
+     thereof, including any amended or successor version of such
+     directive); and
+vii. other similar, equivalent or corresponding rights throughout the
+     world based on applicable law or treaty, and any national
+     implementations thereof.
+
+2. Waiver. To the greatest extent permitted by, but not in contravention
+of, applicable law, Affirmer hereby overtly, fully, permanently,
+irrevocably and unconditionally waives, abandons, and surrenders all of
+Affirmer's Copyright and Related Rights and associated claims and causes
+of action, whether now known or unknown (including existing as well as
+future claims and causes of action), in the Work (i) in all territories
+worldwide, (ii) for the maximum duration provided by applicable law or
+treaty (including future time extensions), (iii) in any current or future
+medium and for any number of copies, and (iv) for any purpose whatsoever,
+including without limitation commercial, advertising or promotional
+purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
+member of the public at large and to the detriment of Affirmer's heirs and
+successors, fully intending that such Waiver shall not be subject to
+revocation, rescission, cancellation, termination, or any other legal or
+equitable action to disrupt the quiet enjoyment of the Work by the public
+as contemplated by Affirmer's express Statement of Purpose.
+
+3. Public License Fallback. Should any part of the Waiver for any reason
+be judged legally invalid or ineffective under applicable law, then the
+Waiver shall be preserved to the maximum extent permitted taking into
+account Affirmer's express Statement of Purpose. In addition, to the
+extent the Waiver is so judged Affirmer hereby grants to each affected
+person a royalty-free, non transferable, non sublicensable, non exclusive,
+irrevocable and unconditional license to exercise Affirmer's Copyright and
+Related Rights in the Work (i) in all territories worldwide, (ii) for the
+maximum duration provided by applicable law or treaty (including future
+time extensions), (iii) in any current or future medium and for any number
+of copies, and (iv) for any purpose whatsoever, including without
+limitation commercial, advertising or promotional purposes (the
+"License"). The License shall be deemed effective as of the date CC0 was
+applied by Affirmer to the Work. Should any part of the License for any
+reason be judged legally invalid or ineffective under applicable law, such
+partial invalidity or ineffectiveness shall not invalidate the remainder
+of the License, and in such case Affirmer hereby affirms that he or she
+will not (i) exercise any of his or her remaining Copyright and Related
+Rights in the Work or (ii) assert any associated claims and causes of
+action with respect to the Work, in either case contrary to Affirmer's
+express Statement of Purpose.
+
+4. Limitations and Disclaimers.
+
+ a. No trademark or patent rights held by Affirmer are waived, abandoned,
+    surrendered, licensed or otherwise affected by this document.
+ b. Affirmer offers the Work as-is and makes no representations or
+    warranties of any kind concerning the Work, express, implied,
+    statutory or otherwise, including without limitation warranties of
+    title, merchantability, fitness for a particular purpose, non
+    infringement, or the absence of latent or other defects, accuracy, or
+    the present or absence of errors, whether or not discoverable, all to
+    the greatest extent permissible under applicable law.
+ c. Affirmer disclaims responsibility for clearing rights of other persons
+    that may apply to the Work or any use thereof, including without
+    limitation any person's Copyright and Related Rights in the Work.
+    Further, Affirmer disclaims responsibility for obtaining any necessary
+    consents, permissions or other rights required for any use of the
+    Work.
+ d. Affirmer understands and acknowledges that Creative Commons is not a
+    party to this document and has no duty or obligation with respect to
+    this CC0 or use of the Work.
@@ -1,4 +1,4 @@
-When opening a pull request to submit a new KIP, please use the suggested template: https://github.com/klaytn/KIPs/blob/master/kip-template.md
+When opening a pull request to submit a new KIP, please use the suggested template: https://github.com/kaiachain/KIPs/blob/main/kip-template.md
 
 We have a GitHub bot that automatically merges some PRs. It will merge yours immediately if certain criteria are met:
 

@@ -1,19 +1,11 @@
-# Klaytn Improvement Proposals (KIPs)
-
-[![No Maintenance Intended](http://unmaintained.tech/badge.svg)](http://unmaintained.tech/)
-
-Klaytn Improvement Proposals (KIPs) describe standards for the Klaytn platform, including core protocol specifications, client APIs, and contract standards.
-
-# NO LONGER MAINTAINED
-
-Since the launch of Kaia Blockchain this repository has been parked in favour of the new open-source projects in [Kaia's Github](https://github.com/kaiachain). Contributors have now moved there continuing with massive open-source contributions to our blockchain ecosystem. A big thank you to everyone who has contributed to this repository. For more information about Klaytn's chain merge with Finschia blockchain please refer to the launching of Kaia blockchain - [kaia.io](http://kaia.io/).
+# Kaia Improvement Proposals (KIPs)
 
 ## Contributing
 
  1. Review [KIP-1](KIPs/kip-1.md).
  2. Fork the repository by clicking "Fork" in the top right.
- 3. Add your KIP to your fork of the repository. There is a [template KIP here](https://github.com/klaytn/kips/blob/master/kip-template.md).
- 4. Submit a Pull Request to Klaytn's [KIPs repository](https://github.com/klaytn/kips).
+ 3. Add your KIP to your fork of the repository. There is a [template KIP here](https://github.com/kaiachain/kips/blob/main/kip-template.md).
+ 4. Submit a Pull Request to Kaia's [KIPs repository](https://github.com/kaiachain/kips).
 
 Your first PR should be a first draft of the final KIP. It must meet the formatting criteria enforced by the build (largely, correct metadata in the header). An editor will manually review the first PR for a new KIP and assign it a number before merging it. Make sure you include a `discussions-to` header with the URL to a discussion forum or open GitHub issue where people can discuss the KIP as a whole.
 
@@ -30,8 +22,8 @@ When you believe your KIP is mature and ready to progress past the draft phase,
 
 * **Draft** - a KIP that is undergoing rapid iteration and changes.
 * **Last Call** - a KIP that is done with its initial iteration and ready for review by a wide audience for two weeks.
-* **Accepted** - a KIP that has been in 'Last Call' for at least 2 weeks, any technical changes that were requested have been addressed by the author, and finally get approved by the Klaytn core developers. 
-* **Final** - a KIP that has been released as a standard specification. If a Core KIP is in 'Final', its implementation has been included in at least one Klaytn client.
+* **Accepted** - a KIP that has been in 'Last Call' for at least 2 weeks, any technical changes that were requested have been addressed by the author, and finally get approved by the Kaia core developers. 
+* **Final** - a KIP that has been released as a standard specification. If a Core KIP is in 'Final', its implementation has been included in at least one Kaia client.
 
 
 {% include types_lastcall.html %} 
@@ -2,11 +2,11 @@
 
 ## 1. Your Use of Open Source Software
 
-We may make (but are not obligated to make) the source code of Klaytn Blockchain Network Platform ("Platform"), the software on the Platform, etc. for download as open source software. If you use this open source software, you agree to be bound by and comply with any license that applies to this open source software. You will not indicate that you are associated with us in connection with your use, modifications or distributions of this open source software.
+We may make (but are not obligated to make) the source code of Kaia Blockchain Network Platform ("Platform"), the software on the Platform, etc. for download as open source software. If you use this open source software, you agree to be bound by and comply with any license that applies to this open source software. You will not indicate that you are associated with us in connection with your use, modifications or distributions of this open source software.
 
 ## 2. Services Provided on the Platform
 
-The Platform is a combination of peer-to-peer subnetworks of nodes transmitting transactions and blocks to execute value transfers and run smart contracts. The Core Cell Network ("CCN"), which is one of the subnetworks that constitute the Platform, verifies and executes transactions that occur on the Platform. The CCN is operated by Klaytn Governance Council, which is a collective group of Core Cell Operators, and Klaytn is not directly involved in any services that are provided in or individual transactions that occur on the Platform.
+The Platform is a combination of peer-to-peer subnetworks of nodes transmitting transactions and blocks to execute value transfers and run smart contracts. The Core Cell Network ("CCN"), which is one of the subnetworks that constitute the Platform, verifies and executes transactions that occur on the Platform. The CCN is operated by Kaia Governance Council, which is a collective group of Core Cell Operators, and Kaia is not directly involved in any services that are provided in or individual transactions that occur on the Platform.
 
 ## 3. Your Installation of BApp on the Platform
 

@@ -13,16 +13,16 @@
 # you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
 # You can create any custom variable you would like, and they will be accessible
 # in the templates via {{ site.myvariable }}.
-title: Klaytn Improvement Proposals
+title: Kaia Improvement Proposals
 description: >-
-  Klaytn Improvement Proposals (KIPs) describe standards for the Klaytn
+  Kaia Improvement Proposals (KIPs) describe standards for the Kaia
   platform, including core protocol specifications, client APIs, and contract
   standards.
-url: "https://kips.klaytn.com"
-twitter_username: klaytn_official
-github_username: klaytn
-facebook_username: klaytn.official
-medium_username: klaytn
+url: "https://kips.kaia.io"
+twitter_username: kaiachain
+github_username: kaiachain
+facebook_username: kaiachain
+medium_username: kaiachain
 header_pages:
  - all.html
  - core.html
@@ -36,9 +36,9 @@ header_pages:
  - informational.html
 twitter:
   card: summary
-  username: klaytn_official
+  username: kaiachain
 facebook:
-  publisher: https://www.facebook.com/klaytn.official
+  publisher: https://www.facebook.com/kaiachain
 
 # Build settings
 markdown: kramdown

@@ -7,13 +7,13 @@
     <meta property="og:title" content="KIP {{ page.kip }}: {{ page.title | escape }}" />
     <meta
       name="description"
-      content="Details on Klaytn Improvement Proposal {{page.kip}} (KIP {{page.kip}}): {{page.title | escape}}"
+      content="Details on Kaia Improvement Proposal {{page.kip}} (KIP {{page.kip}}): {{page.title | escape}}"
     />
     <meta
       property="og:description"
-      content="Details on Klaytn Improvement Proposal {{page.kip}} (KIP {{page.kip}}): {{page.title | escape}}"
+      content="Details on Kaia Improvement Proposal {{page.kip}} (KIP {{page.kip}}): {{page.title | escape}}"
     />
-    <meta name="twitter:description" content="Details on Klaytn Improvement Proposal {{page.kip}} (KIP {{page.kip}}): {{page.title | escape}}" />
+    <meta name="twitter:description" content="Details on Kaia Improvement Proposal {{page.kip}} (KIP {{page.kip}}): {{page.title | escape}}" />
   {% else %}
   <title>{{ page.title | escape }} | {{site.title}}</title>
     <meta

@@ -29,7 +29,7 @@ <h3><a href="{{"meta"|relative_url}}">Meta</a> ({{site.pages|where:"type","Meta"
 
 <h3><a href="{{"informational"|relative_url}}">Informational</a> ({{site.pages|where:"type","Informational"|size}})</h3>
 
-<h2>Klaytn KIPs Last Call Review</h2>
+<h2>Kaia KIPs Last Call Review</h2>
 <p>All KIPs which are in the two-week "last call" status, please help review these and provide your feedback!</p>
 
 {% assign kips = site.pages|where:"status","Last Call"|sort:"kip" %}

@@ -5,7 +5,7 @@
 <div class="home">
   <h1 class="page-heading">
     KIP {{ page.kip | xml_escape }}: {{ page.title | xml_escape }}
-    <a href="{{site.github.repository_url}}/blob/master/{{page.path}}"><svg role="img" aria-label="Source" xmlns="https://www.w3.org/2000/svg" width="14" height="16" viewBox="0 0 14 16"><title>Source</title><path fill-rule="evenodd" d="M9.5 3L8 4.5 11.5 8 8 11.5 9.5 13 14 8 9.5 3zm-5 0L0 8l4.5 5L6 11.5 2.5 8 6 4.5 4.5 3z"/></svg></a>
+    <a href="{{site.github.repository_url}}/blob/main/{{page.path}}"><svg role="img" aria-label="Source" xmlns="https://www.w3.org/2000/svg" width="14" height="16" viewBox="0 0 14 16"><title>Source</title><path fill-rule="evenodd" d="M9.5 3L8 4.5 11.5 8 8 11.5 9.5 13 14 8 9.5 3zm-5 0L0 8l4.5 5L6 11.5 2.5 8 6 4.5 4.5 3z"/></svg></a>
   </h1>
   <table>
     <tr><th>Author</th><td>{% include authorlist.html authors=page.author %}</td></tr>