Karma GAP is best categorized as grant-accountability and reporting infrastructure rather than as a normal grants frontend. The docs repeatedly focus on standardized progress reporting, portable reputation, and permissionless access to structured grant data.
The core mechanism is an EAS-backed grant-memory layer: project profiles, grants, milestones, milestone updates, regular grant updates, and impact attestations become structured onchain records.
The split between one long-lived project profile and many linked grants is the key analytical move. It turns grant history into a portable public identity rather than a collection of isolated application records.
The docs explicitly say communities do not have to use Karma’s own interface, which means the protocol aims to be an underlying data substrate that third parties can build on.
Practical authority still sits with evaluators, grant managers, and communities that review proof of work and decide whether milestone or impact claims are persuasive.
Karma is multi-network and explicitly supports communities using one or more supported chains, reinforcing that its goal is cross-ecosystem reputation portability.
The official gap-contracts repo README is minimal but still confirms the core onchain architecture claim: GAP uses contracts and EAS schema resolvers rather than being a purely offchain SaaS workflow.
Specific source signals worth retaining
Why Karma: strongest problem statement around scattered reporting, weak reputation portability, lack of structured permissionless data, and the use of EAS schemas tailored to reporting needs.
How does it work?: clearest object model — project, grant, milestone, milestone update, grant update, impact.
Builder docs: emphasize transparent onchain reporting, milestone criteria, proof of work, and reputation-building.
Grant-manager docs: show the protocol’s intended evaluator workflow around reviewing grant details and milestone updates.
FAQs + supported-networks pages: confirm anyone with a compatible wallet can create a project profile and that Karma is deployed across multiple L2 / EVM networks.
Add-grant flow: shows grants from multiple communities/networks are meant to accumulate under the same project identity.
Doc-query answer about EAS + onchain data: helpful compact summary that the onchain record set includes grant details, milestones, milestone updates, grant updates, and impact attestations.
gap-contracts README: confirms the repository contains GAP contracts and EAS schema resolvers.
Why this entry belongs in the corpus
Karma GAP is a strong addition because it makes a usually messy governance surface legible: how grant work is reported, verified, remembered, and reused in later funding decisions.
It complements Hypercerts and OSO nicely: Hypercerts emphasizes portable impact/evaluation graphs, OSO emphasizes project identity and metrics, while Karma GAP emphasizes grant execution history and proof-of-work reporting.
The reusable insight is that public-goods funding power often sits upstream of any final allocation vote — in the schemas, profiles, update formats, verification norms, and interfaces that decide what counts as evidence of progress in the first place.