2024 March Update

[holkexyz]

New developments

• HIP: Introduction of the public Hypercerts Improvement Process (HIP) in order to become more transparent in our work at the Hypercerts Foundation and to allow the community to propose improvement and contribute: https://github.com/hypercerts-org/HIPs
• Hypercerts Ecosystem: Organization of a funding round for the Hypercerts Ecosystem along the Gitcoin Grants Round 20. We want to enable more projects to integrate and build with hypercerts to realize the vision of an interconnected, dynamic funding network: GG20 Proposal: https://gov.gitcoin.co/t/gg20-proposal-hypercerts-ecosystem/18319
• Evaluations: Implementation of EAS evaluations for hypercerts - currently in QA: https://github.com/hypercerts-org/HIPs/discussions/1
• VoiceDeck: Support of VoiceDeck to build their funding mechanism for decentralized journalism on the hypercerts marketplace – currently in QA
• Hyperboards: Hyperboards functionality and design were updated and pilots run with libp2p, SciOS 2024, and ZuConnect Istanbul
• Retroactive funding: Conceptual refinement of retroactive funding with hypercerts: https://github.com/hypercerts-org/HIPs/discussions/6
• Redesign: Brand and website redesign in progress

Roadmap

• EasyRetroPGF: We plan to integrate hypercerts with EasyRetroPGF to enable projects to apply for retroactive funding with hypercerts and funders to be recognized by receiving hypercerts. Ultimately, we aim to allow rewarding early financial and non-financial contributors by later retroactive funding and use hypercerts to make this process transparent.
• Multi-chain support: Implementation of full multi-chain support - currently work in progress: https://github.com/hypercerts-org/HIPs/discussions/2
• Marketplace features: VoiceDeck release in the coming weeks
• Evaluations: Extending the evaluations as described in HIP 1 above to allow evaluators to submit data based on specified templates for their impact domain.
• Flexible metadata: We plan to allow any EAS attestation to serve as the metadata for a hypercert, such that the metadata is more flexible, EAS tooling can be used, and integrations become simpler: https://github.com/hypercerts-org/HIPs/discussions/4
• Revamp front-end: We are updating the website and split the general hypercert content from the web3 app: https://github.com/hypercerts-org/HIPs/discussions/5
• Integrations: We’ll support funding platforms to integrate hypercerts. If you are interested in using hypercerts, please write us at team [at] hypercerts.org