Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/push-protocol/pips

Push Improvement Proposals (PIPs) defines the standards in the Push protocol. Anyone can create, amend these proposals by going through the submission life cycle. The goal of the PIP is to document standardised protocols for Push nodes, payload standards, applications and to document them in a high quality and implementable way.
https://github.com/push-protocol/pips

Last synced: 20 days ago
JSON representation

Push Improvement Proposals (PIPs) defines the standards in the Push protocol. Anyone can create, amend these proposals by going through the submission life cycle. The goal of the PIP is to document standardised protocols for Push nodes, payload standards, applications and to document them in a high quality and implementable way.

Awesome Lists containing this project

README 

        
# PUSH Improvement Proposals (PIPs)



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).



## What are PIPs?



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.



## How to submit a PIP?



Before you initiate a pull request, please read the [PIP-1](./PIPs/consideration/pip-1-workflow-index.md) process document. Read  [definitions](./definitions) to understand types, categories, subcategories, and niches. Ideas should be thoroughly discussed on [Push discord](https://discord.gg/YVPB99F9W5) or [Push forum](https://gov.push.org/c/pip/29).



Read this to learn about how to [submit proposal](./pip-lifecycle.md) and [template](./pip-template.md) of standard PIPs.



# Accepted PIPs



| ID  | Desc  |  Type | Category | Subcategory | Niche |  Status |

|---|---|---|---|---|---|---|

[PIP-1](./PIPs/pip-1-workflow-index.md) | Workflow Index | Standard | -- | -- | -- | Living |



# PIPs in consideration



| 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**.



## PIPs Standards Editors



The current editors are:



* Pranshu Rastogi [@pranshurastogii](https://twitter.com/pranshurastogii)

* Harsh Rajat [@harshrajat](https://twitter.com/harshrajat)



## Contact us



Stay in touch! [Website](https://www.push.org), [Twitter](https://twitter.com/pushprotocol), [Discord](https://discord.gg/YVPB99F9W5), [Docs](https://docs.push.org), [Whitepaper](https://whitepaper.push.org/), [Telegram](https://t.me/epnsproject), [Medium](https://medium.com/ethereum-push-notification-service), [YouTube](https://www.youtube.com/c/EthereumPushNotificationService)



## History



This document was derived heavily from [Ethereum's EIP-1](https://eips.ethereum.org/EIPS/eip-1), which was derived from [Bitcoin's BIP-0001](https://github.com/bitcoin/bips) written by Amir Taaki, which in turn was derived from [Python's PEP-0001](https://www.python.org/dev/peps/). 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](https://github.com/ethereum-push-notification-service/PIPs#pips-standards-editors).