Push Improvement Proposals (PIPs) enable Push protocol to form standardized, community-driven improvements, specs and standards with the mission to create a seamless, standardized, community-built communication protocol of web3 to be used by all web3 actors (protocols, dapps, smart contracts, wallets, backend and users).
PIPs define the standards in the Push protocol ecosystem in which anyone can create, amend these proposals by submitting them. The goal of the PIP project is to document standardized protocols for Push nodes, payload standards, applications and to document them in a high quality and implementable way.
Before you initiate a pull request, please read the PIP-1 process document. Read definitions to understand types, categories, subcategories, and niches. Ideas should be thoroughly discussed on Push discord or Push forum.
Read this to learn about how to submit proposal and template of standard PIPs.
| ID | Desc | Type | Category | Subcategory | Niche | Status |
|---|---|---|---|---|---|---|
| PIP-1 | Workflow Index | Standard | -- | -- | -- | Living |
| ID | Desc | Type | Category | Subcategory | Niche | Status |
|---|
Note: Finalized PIPs will be listed in Accepted PIPs, while PIPs that are going through the lifecycle but are not stale or withdrawn will appear in PIPs in consideration.
The current editors are:
- Pranshu Rastogi @pranshurastogii
- Harsh Rajat @harshrajat
Stay in touch! Website, Twitter, Discord, Docs, Whitepaper, Telegram, Medium, YouTube
This document was derived heavily from Ethereum's EIP-1, which was derived from Bitcoin's BIP-0001 written by Amir Taaki, which in turn was derived from Python's PEP-0001. In many places text was simply copied and modified.
Although the PEP-0001 text was written by Barry Warsaw, Jeremy Hylton, and David Goodger, they are not responsible for its use in the PUSH Improvement Process, and should not be bothered with technical questions specific to Push or the PIP. Please direct all comments to the PIP editors.