Certificates

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

It's not a PDF that says "Aaron completed this course." It's 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's actually in it, why the blockchain anchor matters, and what your recruiter will see 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, 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 hasn't 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

Here's the part that's 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 doesn't 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 — domain expires, company goes under, anything — your credential is still verifiable forever. The cryptographic evidence is on a public chain. Anyone can run a verifier.
• It's tamper-evident. If someone tries to alter the credential — change a name, change 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, 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/c/{credentialId}

When a recruiter opens that URL, they see:

1. Your name and the challenge you completed.
2. The discipline, the deliverable type, 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 URL to your CV — it's link-friendly.
• Add it to LinkedIn under the "Licenses & Certifications" section. LinkedIn's verifier-link field handles it natively.
• 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 couldn't 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; we issue the credential. The cryptography happens automatically.

Next

The other big practical question for any submission you make: who actually owns the work? Covered next: Who owns your work?.