Hypercert Improvement Proposals (HIPs) are intended for collaborative community input on what should be improved, tweaked, built, supported, or simply worked on for the hypercerts protocol, marketplace, apps, and it's role in the interconnected impact funding ecosystem.
While we are excited to have a more formal process to hear ideas from the community (roughly inspired by the more decentralized PEP, BIP and EIP processes - and in the case of HIPS mostly DIPS), this is an experiment, and it should be understood that approval of proposals ultimately lies solely with the hypercert team. HIPs focus on collaboration in the ecosystem, so please review HIP-0 and try to collaborate on other proposals before submitting your new HIP. We're excited to see all of your great ideas!
- Post your idea in the discussion forum, publicize it, discuss it there, and gather feedback.
- Once you have feedback and some interest in the idea, proceed with the below steps.
- Review HIP-0. If you have questions or need help with Github, please just ask us — we can help you!
- Fork the repository by clicking "Fork" at the top right.
- Add your HIP to your fork of the repository.
- Submit a Pull Request to this repository
After submitting editors will go through this checklist - it is encouraged that you already went through these points yourself.
- Draft - a HIP that is undergoing rapid iteration and changes.
- Accepted - The hypercerts team has Accepted your HIP.
- Not implemented - The HIP won’t be implemented.
- Changes Requested - The HIP needs modifications conditional to its validation.