> For the complete documentation index, see [llms.txt](https://docs.learncard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.learncard.com/start-here/glossary.md). # Glossary Plain-English definitions of every LearnCard term. | Term | Definition | | -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Verifiable Credential (VC)** | A digital certificate or badge — like a diploma or skill badge — that is cryptographically signed so anyone can verify it's authentic, and owned by the person who earned it. Based on the [W3C standard](https://www.w3.org/TR/vc-data-model-2.0/). | | **DID (Decentralized Identifier)** | A user-owned identifier (like `did:key:z6Mk...`) that works across systems without a central registry. Every LearnCard user and issuer has one. | | **Boost** | A LearnCard credential template. Define a badge once, then issue copies of it to many recipients — with optional dynamic fields per recipient. | | **Universal Inbox** | LearnCard's delivery system for sending credentials by email or phone to people without an account. Recipients get a claim link, and the credential waits for them to sign up. | | **ConsentFlow** | A contract-based permission system: users explicitly consent to what data an app can read or write, and can withdraw consent at any time. | | **GameFlow** | A ConsentFlow variant for games and apps used by minors, with built-in guardian approval. | | **Auth Grant / API Token** | A scoped, static credential for server-to-server API calls (e.g. scope `inbox:write` to send credentials). Created once, then used as a Bearer token. | | **Seed phrase** | The random secret that deterministically generates your keys and DID. Whoever holds the seed controls the identity. | | **SSS (Shamir Secret Sharing)** | Splits a private key into shares (2-of-4) so that at rest no single device or server stores the whole key. At sign-in, two shares are combined in memory to reconstruct the key for use. Powers LearnCard's passwordless key management. | | **Signing Authority** | A service that holds a key and signs credentials on an issuer's behalf for claim links and server-side issuance without the issuer's seed. LearnCard can host one. | | **Profile** | An issuer's or user's public identity on the LearnCard Network (profile ID, display name, avatar). | | **Presentation (VP)** | A signed bundle of one or more credentials that a holder shares with a verifier, proving the credentials belong to them. | | **OBv3 (Open Badges 3.0)** | The 1EdTech standard for achievement badges, built on Verifiable Credentials. LearnCard's default badge format. | | **CLR (Comprehensive Learner Record)** | A 1EdTech standard for bundling many achievements (courses, degrees, skills) into one verifiable record. | | **xAPI** | A standard for recording learning activity statements ("Alice completed Lesson 3"). LearnCloud stores xAPI data tied to user DIDs. | | **CHAPI** | The Credential Handler API — a browser protocol for wallet-to-site credential exchange. LearnCard is CHAPI-compatible. | | **Trust Registry** | A list of recognized issuers used to show whether a credential comes from a known, trusted source. | | **Template (Boost)** | A reusable definition of a credential. Send from a template and LearnCard fills in each recipient's copy and signs it for you. Every `send` creates one; its address looks like `lc:network:…:boost:…`. | | **Integration** | Your project's identity in the Developer Portal. It owns your API tokens, templates, and app listings. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.learncard.com/start-here/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.