LearnCard Documentation
GithubStatusSupportLaunch App
  • 🚀Introduction
    • What is LearnCard?
    • Use Cases & Possibilities
    • Ecosystem Architecture
  • ⚡Quick Start
    • Setup & Prerequisites
    • Your First Integration
  • 📚Tutorials
    • Create a Credential
    • Create a Boost
    • Create a ConsentFlow
    • Create a Connected Website
    • Send xAPI Statements
    • Listen to Webhooks
  • ✅How-To Guides
    • Verify My Issuer
    • Connect Systems
      • Connect a Website
      • Connect a Game
    • Implement Flows
      • Claim Data after Guardian Consent
      • Connect via CHAPI
        • ⭐CHAPI Wallet Setup Guide
        • ↔️Translating to CHAPI documentation
        • 🖥️Demo Application
        • 🔰Using LearnCard to Interact with a CHAPI Wallet
        • 📝Cheat Sheets
          • Issuers
          • Wallets
    • Deploy Infrastructure
      • Remote Key Management
      • Generate API Tokens
      • Signing Authority
      • Connect to Independent Network
      • Build a Plugin
  • 🛠️SDKs & API Reference
    • LearnCard Wallet SDK
      • Authentication
      • Usage Examples
      • SDK Reference
      • Plugin API Reference
      • Integration Strategies
      • Deployment
      • Troubleshooting
      • Changelog
    • LearnCloud Network API
      • Authentication
      • Usage Examples
      • Architecture
      • Notifications & Webhooks
      • Profiles
      • Profile Managers
      • Credentials
      • Boosts
      • Presentations
      • Storage
      • Contracts
      • DID Metadata
      • Claim Hooks
      • Auth Grants
      • Utilities
      • Models
      • OpenAPI
    • LearnCloud Storage API
      • Authentication
      • Usage Examples
      • Architecture
      • Storage
      • Index
      • User
      • Custom Storage
      • Utilities
      • Models
      • xAPI Reference
    • Plugins
      • Crypto
      • DIDKit
      • DID Key
      • Dynamic Loader
      • VC
        • Expiration Sub-Plugin
      • VC-Templates
      • VC-API
      • Ceramic
      • IDX
      • VPQR
      • Ethereum
      • CHAPI
      • LearnCard Network
      • LearnCloud
      • LearnCard
      • Simple Signing
      • Claimable Boosts
    • LearnCard CLI
  • 🧠Core Concepts
    • Identities & Keys
      • Decentralized Identifiers (DIDs)
      • Seed Phrases
      • Network Profiles
      • Signing Authorities
      • Trust Registries
    • Credentials & Data
      • Verifiable Credentials (VCs)
      • Credential Lifecycle
      • Schemas, Types, & Categories
      • Building Verifiable Credentials
      • Boost Credentials
      • Getting Started with Boosts
      • Credential URIs
      • xAPI Data
      • General Best Practices & Troubleshooting
    • Consent & Permissions
      • ConsentFlow Overview
      • Consent Contracts
      • User Consent & Terms
      • Consent Transactions
      • Auto-Boosts
      • Writing Consented Data
      • Accessing Consented Data
      • GameFlow Overview
    • Network & Interactions
      • Network Vision & Principles
      • Key Network Procedures
      • Core Interaction Workflows
    • Architecture & Principles
      • Control Planes
      • Plugin System
      • Auth Grants and API Tokens
  • 🔗Development
    • Contributing
Powered by GitBook
On this page
  • What is this section about?
  • Why is this important for you to understand?
  • What you'll learn:
  • 🎓 Verifiable Credentials (VCs)
  • 📦 Verifiable Presentations (VPs)
  • 🔓 Open Standards
  • ⚡ Boosts

Was this helpful?

  1. Core Concepts

Credentials & Data

Verifiable Credential structure, Schemas, Data Models, Boosts

PreviousTrust RegistriesNextVerifiable Credentials (VCs)

Last updated 10 days ago

Was this helpful?

What is this section about?

This section focuses on the information itself—the digital records that are created, shared, and verified within the LearnCard system. We'll look closely at the structure of Verifiable Credentials (VCs), how their format is defined using Schemas, other important Data Models, and unique constructs like "Boosts."

Why is this important for you to understand?

The core value of LearnCard revolves around its ability to manage and exchange trustworthy, verifiable information. To build meaningful applications, you need to know how this information is structured, what it represents, and how to interpret it. Understanding VCs, Schemas, and concepts like "Boosts" is essential for creating, issuing, presenting, and verifying these digital assets correctly. This is like understanding the layout and content of an official certificate or a detailed project portfolio.

What you'll learn:

You'll explore the anatomy of a Verifiable Credential, how Schemas ensure consistency, how different pieces of data relate to each other through Data Models, and the specific role and structure of "Boosts."


🎓 Verifiable Credentials (VCs)

Verifiable Credentials are portable digital statements—like a diploma, badge, or license—that anyone can issue and anyone can verify.

  • Issuer: The party who creates the credential (e.g. a school, platform, employer).

  • Holder: The person or agent who owns the credential.

  • Verifier: Anyone who needs to check that the credential is legit.

LearnCard uses the to ensure global interoperability and verification.


📦 Verifiable Presentations (VPs)

A Verifiable Presentation (VP) is a bundle of one or more credentials that a user shares with another party.

  • Think of it as a "credential folder" you can pass around

  • Can be generated dynamically with selective fields

  • Fully verifiable using DIDs and cryptographic proofs


🔓 Open Standards

Interoperability is built-in. LearnCard supports:

  • Open Badges v3 (OBv3)

  • Comprehensive Learner Record (CLR)

  • Learning Tools Interoperability (LTI)

  • Learning and Employment Records (LER)

  • Learner Information Framework (LIF)


⚡ Boosts

A Boost is a superpowered VC. It follows OBv3 and W3C standards but adds:

  • Display metadata: Control how credentials appear in wallets

  • Governance rules: Enforce who can issue what

  • Network validation: Confirm issuance rules were followed

  • Attachments: Include files, PDFs, or resources

Think of Boosts as VC+—fully standards-compliant but better for real-world apps.

🧠
W3C VC standard