A new credential model, not a minor file update
Open Badges 2.0 commonly represents an achievement as a hosted or baked JSON-LD assertion whose verification follows issuer-controlled URLs. Open Badges 3.0 adopts the W3C Verifiable Credentials model: the achievement, recipient, issuer, and cryptographic proof travel together as a credential the recipient can hold and present.
The signature and credential integrity can be checked offline when the verifier has the issuer's public verification material. A current revocation or expiry decision still requires an online status check.
What training teams need to plan
- Preserve legacy records — keep existing OB2 URLs, assertions, images, and revocation records available.
- Issue new credentials in 3.0 — GrokCred signs new Open Badges 3.0 credentials while continuing to serve historical OB2 records.
- Support recipient-held copies — learners can download the complete credential and use compatible wallets as adoption grows.
- Separate proof from status — cryptographic proof detects changed data; a live status check answers whether the credential is currently valid.
A practical migration sequence
- Inventory OB2 credentials — identify every record and public URL that must remain available.
- Move new issuance to signed OB3 — avoid rewriting historical achievements merely to change their format.
- Document verification — tell recipients and employers how to inspect the proof and where to check current status.
Frequently asked questions
Is GrokCred Open Badges 3.0 compliant?
Yes. New GrokCred credentials use the Open Badges 3.0 format and are cryptographically signed so their integrity can be checked.
Are my legacy Open Badges 2.0 credentials still valid?
Yes. Existing Open Badges 2.0 credentials remain valid and available at their original public links. GrokCred continues to preserve their status pages and JSON-LD records.
What is Open Badges 2.0?
Open Badges 2.0 is the open standard for portable digital credentials. A badge is a verifiable, machine-readable JSON-LD record that links the recipient, the achievement, the issuer, and the criteria — so anyone can confirm it is genuine without contacting you.
Are GrokCred badges actually verifiable?
Yes. Each issued credential has a public verification page and a machine-readable JSON-LD assertion. The recipient's email address is always stored as a salted hash and never exposed publicly.
Do recipients need an account?
No. Recipients receive their badge by email and can view, verify, download, and share it without ever signing up.
Can I revoke a credential later?
Yes. Revoked credentials display a clear revocation notice on their public page and are removed from the sitemap so search engines stop surfacing them.