HIPs - Hush Improvement Proposals

This is the repository for Hush Improvement Proposals, also known as "HIPs". People wishing to submit HIPs, first should propose their idea or document as a Pull Request on this repo and discuss on Hush Telegram. After discussion and copy-editing and acceptance, it will be published here, normally as a pull request merge.

We are fairly liberal with approving HIPs, 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
HIP039	Seedphrases (BIP039)	Duke Leto	Standards	Planning
HIP047	Reusable Payment Codes (BIP047)	Duke Leto	Standards	Planning
HIP155	ADDRv2 P2P (BIP155)	Duke Leto	Planning	Planning
HIP208	Block Time Halving	Duke Leto	Standards	Active
HIP210	Sapling Anchor Deduplication within Transactions	Duke Leto	Standards	Planning
HIP212	Allow Recipient to Derive Sapling Ephemeral Secret from Note Plaintext	Duke Leto	Standards	Planning
HIP213	Shielded Coinbase Considered Harmful	Duke Leto	Standards	Active
HIP304	z_signmessage + z_verifymessage	Duke Leto	Standards	Planning
HIP310	Security Properties of Sapling Viewing Keys	Duke Leto	Informational	Planning
HIP400	wallet.dat format	Duke Leto	Informational	Active

Zcash Company Stole HIP400

We have cryptographic evidence that Zcash Company, and specificly Daira Hopwood (author of Zcash Protocol), stole HIP400, deleted all history of contributions from Duke Leto on Github, who researched it and wrote it in it's entirety. More details soon. ZIP400 is the stolen work of Duke Leto, and copyright infringement occured because no attribution was given. Zcash Company doesn't want the world to know they had to steal a technical document from the person who wrote attackingzcash.com