Skip to content

Credentials and Certifications

A paper certificate proves something happened once, in one place, to whoever’s holding it. You can lose it, someone can copy it, and a hiring manager in Nairobi or Dubai has no reliable way to verify it. Web3 credentials solve a different problem: they make your achievements independently verifiable by anyone, anywhere, without needing to trust the piece of paper - or you.

A credential is a record tied to your wallet address, issued by an organization, and written to a blockchain or a linked data system. The issuer signs it with their private key. You hold it. Anyone with the issuer’s public key can confirm it’s real without calling anyone or checking a database.

The most common standard right now is Verifiable Credentials (VCs) - an open format that works across different platforms. You might also encounter Soulbound Tokens (SBTs), which are NFTs that can’t be transferred. Unlike a regular token, you can’t sell or give away an SBT - it stays with the wallet that earned it. That non-transferability is the point: it represents something about you, not something you own.

Both formats do the same job: they create proof of achievement that doesn’t depend on an institution being reachable or trustworthy to verify.

Think about how credentials work in Somaliland right now. You complete a training at a local NGO or a skills program. You receive a certificate. If you later apply for a job in another city, or want to contribute to a global DAO, or apply for a grant from an international organization - you have to rely on the issuer being contactable, your paper not being lost or damaged, and whoever is reviewing your application trusting the organization that issued it.

Web3 credentials remove each of those dependencies. The issuer cryptographically signs your credential when they issue it. After that, no one needs to contact them to verify it’s real - the math does that. You carry your record in your wallet, not in a filing cabinet.

Several platforms are actively issuing verifiable credentials:

  • Gitcoin Passport - aggregates your web3 activity (contributions to projects, protocol usage, identity verification) into a score used by grants programs and DAOs to confirm you’re a real, active participant rather than a bot or sybil
  • Karma - used in the DAO ecosystem to track governance participation and contribution history
  • Lens Protocol - your social graph and activity on Lens creates a portable reputation record
  • Galxe - issues on-chain credentials tied to completing specific tasks (campaigns, learning modules, testing protocols)
  • Open Badges (via various issuers) - the older but still-active standard, widely used by educational organizations

Sarreya itself issues credentials on completion of path milestones. By the time you’re reading this, you’ve already accumulated some.

The most direct use is in grant and funding applications. Gitcoin Grants, for example, uses Passport scores to weight quadratic funding - higher passport score means your donation has more matching power. If you’re applying for a fellowship or residency through a web3-native organization, your on-chain credential history often matters more than a CV.

DAOs increasingly gate governance participation and contributor roles behind credentials. To vote on a proposal in some communities, you need to hold an SBT showing you’ve completed an orientation or contributed to a specific project. This isn’t gatekeeping for its own sake - it’s an attempt to ensure that people making decisions have skin in the game.

For job applications, the picture is more mixed. Traditional employers outside the web3 ecosystem won’t know what a Soulbound Token is. But this is changing, and it’s changing fast in tech hiring. More practically: when you apply for remote work through platforms that serve web3 companies, your on-chain reputation is immediately legible to people doing the hiring.

Not all credentials are worth pursuing. Some are issued just to drive engagement with a platform - the on-chain equivalent of a pop-up notification asking you to rate your experience. The ones worth collecting have a few characteristics:

  • Issued by a recognized organization - either one with an established reputation in web3 (Gitcoin, major DAOs) or one your specific target audience will recognize
  • Tied to verifiable activity - completing a real course, making a contribution, passing an assessment, attending a specific event
  • Held in a wallet you control - not a custodial platform that could shut down and take your credentials with it

Be selective. A wallet holding 50 irrelevant credentials from engagement farming campaigns tells a different story than one holding 8 credentials from meaningful programs.

Your credentials live in your wallet - but you need a way to present them. A few tools worth knowing:

Metamask stores credentials associated with your address. Ceramic Network and IDX allow you to build a decentralized identity profile linked to your wallet. Disco.xyz is specifically built for managing and sharing your web3 identity and credentials in a readable format - think of it as a CV layer on top of your wallet.

If you’re presenting credentials to an organization that uses Gitcoin Passport, connect your wallet to passport.gitcoin.co and add your stamps (verifications). The more legitimate stamps you hold - linked GitHub account, proof of on-chain activity, verified identity - the higher your score.

Keep your credentials tied to a wallet address you intend to use long-term. If you rotate wallets often, your credential history fragments across addresses, which weakens the signal.

Credentials solve a trust problem. In contexts where institutions are weak, paper is unreliable, and long-distance verification is difficult - which describes a lot of East Africa’s employment and opportunity space - on-chain credentials create an alternative track record. One that doesn’t depend on geography, paper, or institutional continuity.

That’s the actual utility. Not that your achievements are somehow more real, but that they’re more portable and more verifiable in the contexts where it matters.


Next: Managing your digital identity - what you share, with whom, and how to keep it consistent across platforms.