# Certificates

> Your Ewance certificate is a verifiable, blockchain-anchored credential, not a PDF. Anyone can confirm it without trusting Ewance.

Your Ewance **certificate** is the thing your work was for. It is also probably different from any certificate you have earned before.

It is not a PDF that says "Alex completed this course". It is a **verifiable credential**, a signed, standards-compliant document anchored on a public blockchain, that recruiters can confirm without ever contacting Ewance.

This page explains what is in it, why the blockchain anchor matters and what a recruiter sees when they verify it.

## What a certificate is, technically

Under the hood, an Ewance certificate is a **W3C Verifiable Credential 2.0** document, also conformant with **Blockcerts v3** and **Open Badges 3.0**. Those are the three open standards that govern portable, verifiable academic and professional credentials.

The certificate contains, in machine-readable form:

- **Your identity**: your name and a stable identifier.
- **The achievement**: the challenge title, the discipline, the deliverable and the rubric you were evaluated against.
- **The issuer**: Ewance, with a cryptographic public key anyone can use to verify our signature.
- **The submission reference**: a cryptographic hash of the deliverable you submitted. The submission itself stays private. The hash proves it has not been tampered with.
- **The issuance date**: exactly when the credential was issued.
- **The team composition**: solo, pair or squad, with your role if relevant.

The entire document is cryptographically signed by Ewance.

## Why a blockchain anchor matters

This is the part that is different from a typical online certificate.

Once your credential is issued, the cryptographic hash of it is **anchored on the Base blockchain**, a public, low-cost Ethereum L2. The anchor is permanent. It cannot be deleted. It cannot be backdated. It cannot be tampered with without leaving cryptographic evidence.

This means:

- **A recruiter does not have to trust Ewance.** They verify the credential client-side in their browser. The signature, the issuer key and the on-chain anchor speak for themselves.
- **Your credential outlives the platform.** If Ewance disappears tomorrow, your credential is still verifiable forever. The cryptographic evidence is on a public chain. Anyone can run a verifier.
- **It is tamper-evident.** If someone tries to alter the credential, such as changing a name or a date, verification fails immediately.

This is the difference between a certificate of watching a video and a credential a working employer can act on.

The blockchain anchoring is provided by [LearnCoin](https://learncoin.me), the open credentialing infrastructure layer that issues credentials on behalf of platforms like Ewance.

## What recruiters see

Every credential has a public verification URL of the shape:

```
https://verify.ewance.com/credentials/{credentialId}
```

When a recruiter opens that URL, they see:

1. Your name and the challenge you completed.
2. The discipline, the deliverable type and the team format.
3. The rubric you were evaluated against.
4. A live verification result, five cryptographic checks (schema, signature, issuer, revocation, anchor), that runs in their browser.

The verification is **independent of Ewance**. The recruiter's browser does the work. We never see that they checked.

## What if you want to share it?

You can:

- **Add the link to your CV.** It is link-friendly.
- **Add it to LinkedIn** under "Licenses and certifications". See [Share on LinkedIn](/docs/students/share-on-linkedin.md).
- **Drop it into an email.** Recruiters can verify in one click.
- **Export the signed JSON-LD document** for offline verification by tools like the Blockcerts verifier.

## What about revocation?

If a credential is later found to have been issued in error, for example plagiarism is discovered or the submission turns out to be a fabrication, Ewance can revoke it. Revocation marks the credential as no longer valid in the verification check. The credential is *not* deleted. The verifier returns a "revoked" result instead of "valid".

Revocation is rare. We mention it because the existence of a revocation mechanism is what gives the certificate its weight. Without it, the credential could not be trusted in the first place.

## Common questions

**Can someone fake my certificate?** Forging the cryptographic signature requires Ewance's private key, which lives in an HSM-protected key management system. Forging the on-chain anchor requires rewriting Ethereum's history. Neither is realistic.

**What if I change my name later?** The credential records your name as it was at issuance. You can request a re-issuance with the updated name. Both versions remain verifiable, and recruiters see both.

**Does it expire?** No. Credentials are permanent unless revoked for cause.

**Do I have to understand any of this to earn one?** No. You ship a challenge and we issue the credential. The cryptography happens automatically.

## Next

The other big practical question for any submission: who owns the work? See [Who owns your work?](/docs/students/who-owns-your-work.md).
