From 4d674f11cbf3ff2b44a2cb81e0d1754b03cbe76a Mon Sep 17 00:00:00 2001 From: Matthew Reichardt Date: Tue, 19 Dec 2017 20:08:41 -0600 Subject: [PATCH] Update README.md --- README.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 9a3cc4f..28a7e9c 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,13 @@ # HIPs - Hush Improvement Proposals -This is where proposals to improve Hush Core are stored, -following in the footsteps of Bitcoin Improvement Proposals (BIPs) and Zcash Improvement Proposals (ZIPs). +This is the repository for Hush Improvement Proposals, also known as "HIPs". People wishing to submit HIPs, first should propose their idea or document to the `spec-proposals` channel on the [Counterparty Discord](https://discord.io/hush). After discussion and copy-editing and acceptance, it will be published here, normally as a pull request merge. -# Coming Soon +We are fairly liberal with approving CIPs, and try not to be too involved in decision making on behalf of the community. The exception is in very rare cases of dispute resolution when a decision is contentious and cannot be agreed upon. In those cases, the conservative option will always be preferred. + +Having a HIP here does not make it a formally accepted standard until its status becomes Active. For a HIP to become Active requires the mutual consent of the community. + +Those proposing changes should consider that ultimately consent may rest with the consensus of the Hush users. + +Number | Title | Owner | Type | Status | +------------- | -------------------------------------------| ------------------------------------- | ------------- | ------------- | +[1](cip-0001.md) | CIP Purpose and Guidelines | Matthew Reichardt | Process | Planning |