forked from pactus-project/PIPs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
24 lines (21 loc) · 1.78 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
---
layout: default
title: Home
---
<h1 class="page-heading">PIPs
<a href="https://discord.gg/H5vZkNnXCu"><img src="https://dcbadge.vercel.app/api/server/H5vZkNnXCu?style=flat" alt="Discord channel Pactus"></a>
<a href="https://twitter.com/pactuschain/"><img alt="Twitter URL" src="https://img.shields.io/twitter/url?url=https%3A%2F%2Ftwitter.com%2Fpactuschain%2F&label=pactus%20on%20twitter"></a>
<a href="rss/all.xml"><img src="https://img.shields.io/badge/rss-Everything-red.svg" alt="RSS"></a>
</h1>
<p>Pactus Improvement Proposals (PIPs) describe standards for the Pactus platform, including core protocol specifications, client APIs, and contract standards. Network upgrades are discussed separately in the <a target="_blank" href="https://github.com/pactus-project/pactus">Pactus Project</a> repository.</p>
<h2>Contributing</h2>
<p>First review <a href="PIPs/pip-1">PIP-1</a>. Then clone the repository and add your PIP to it. There is a <a href="https://github.com/pactus-project/PIPs/blob/main/pip-template.md?plain=1">template PIP here</a>. Then submit a Pull Request to Pactus's <a href="https://github.com/pactus-project/PIPs">PIPs repository</a>.</p>
<h2>PIP status terms</h2>
<ul>
<li><strong>Draft</strong> - Proposal under active discussion and revision.</li>
<li><strong>Accepted</strong> - Normative proposal accepted for implementation</li>
<li><strong>Final</strong> - Accepted and implementation complete, or no longer active.</li>
<li><strong>Rejected</strong> - Formally declined and will not be accepted.</li>
<li><strong>Withdrawn</strong> - Removed from consideration by sponsor or authors.</li>
<li><strong>Living</strong> - A special status for PIPs that are designed to be continually updated and not reach a state of finality. This includes most notably PIP-1.</li>
</ul>