Hypercerts create shared context—evidence, expert input, and community trust—for better resource allocation. At its core, a hypercert is a living digital record of impactful work: what was done or is planned, by whom, when, and where. As evidence and evaluations accumulate over time, it becomes a shared, evolving picture of work and its value.

Today's impact funding systems are fragmented and inefficient. Hypercerts address this with a simple pattern—record, evaluate, fund—that works across climate and regeneration, open-source software, research and development, and community programs. Built on the AT Protocol as open infrastructure, records are portable, referenceable, and not locked into any single platform.

In many domains, valuable work produces public or shared benefits, but information about that work—what was done, by whom, with what evidence, and how it was evaluated—is fragmented, ephemeral, or locked inside platforms.

This makes it difficult to:

• evaluate work in pluralistic ways,
• coordinate funding across many contributors and evaluators,
• reuse prior information rather than recreating it from scratch.

Hypercerts address this by providing a shared, open data model for describing work and its evaluation as first-class, linkable records.

At a high level, a hypercert:

• describes an activity or scope of work,
• links to evidence and contextual data,
• can be evaluated by multiple parties over time,
• can be referenced by funding and ownership mechanisms.

Hypercerts are not a marketplace or a single application. They are a protocol-level building block that can be used by many different tools, communities, and funding mechanisms.

The design emphasizes: composability, reuse, plural evaluation, and durability of records.

Hypercerts span both social and financial layers:

• Offchain / social data

  • Records for activities, evidence, evaluations, and relationships
  • Built on ATProto as an open data layer
  • Portable identities and durable references

• Onchain (optional)

  • Ownership, fractionalization, and transfer
  • Anchoring records or hashes on public blockchains
  • Used when financial coordination or incentives are required

This separation allows hypercerts to be useful even without tokenization, while still supporting onchain mechanisms where appropriate.

Hypercerts are intended for:

• builders of funding, evaluation, or coordination tools
• evaluators, reviewers, and domain experts producing assessments or judgments
• researchers exploring new institutional or economic mechanisms
• open-source and public-interest projects seeking better funding primitives
• funders experimenting with pluralistic or retrospective allocation models

You do not need to adopt the entire stack to use hypercerts—individual components can be reused independently.

• hypercerts-lexicon — ATProto lexicons (data schema) for hypercerts
• hyperindex — query hypercert data across the network
• ePDS — extended Personal Data Server for hypercerts
• certified-group-service — group coordination service for managing a PDS
• documentation — docs.hypercerts.org

• hypercerts-org — the hypercerts.org website
• certified-app — portable impact profiles at certified.app
• hypercerts-cli — create and manage hypercerts programmatically
• hypercerts-scaffold-atproto — quickstart scaffold app for building on hypercerts

• hypercerts-protocol — smart contracts and the contracts NPM package
• hypercerts-app — the original app.hypercerts.org application
• hypercerts-sdk — SDK with contract methods, helpers, and tooling
• marketplace-sdk — marketplace SDK (built on Looksrare)
• hypercerts-indexer — custom indexer for rapid data access
• hypercerts-api — OpenAPI and GraphQL instance for querying data
• ecocerts — discussion and development of hypercerts for ecological impact

Contributing

• CONTRIBUTING.md for how to get involved
• CODE_OF_CONDUCT.md for community standards

General information

• Website: https://hypercerts.org
• Documentation: https://docs.hypercerts.org
• Blog: https://hypercerts.org/blog

Contact

• Bluesky
• Twitter
• Telegram
• Telegram Support

The hypercerts project is supported by organizations and individuals who believe in building open, interoperable infrastructure for recognizing and coordinating around real-world work. These include: Protocol Labs, Ma Earth, GainForest, Optimism, Octant, Gitcoin, Silvi, Regen Foundation, and Funding the Commons.

Their support—through funding, collaboration, feedback, and shared experimentation—helps advance the development of hypercerts as a public-good primitive. Support does not imply endorsement of specific design decisions or applications.

We're grateful to all supporters who contribute time, resources, and trust to this ongoing effort.