Andamio Glossary
A reference guide for key terms, concepts, and acronyms used throughout Andamio documentation.
Core Components
Andamio is infrastructure for verifiable work and portable credentials on Cardano. It consists of four interconnected components: the Protocol (on-chain smart contracts), the SDK (developer tools), the API (serving coherent data), and the App (reference implementation). Together, these enable anyone to create learning experiences, coordinate projects, and build trust networks—all anchored in self-sovereign on-chain identity and local solutions.
Andamio Protocol
On-chain smart contracts on Cardano that enable decentralized identity (SSOI), credential management, and global coordination of local work. Defines how Access Tokens, Global State, and Local States interact for skills verification and contribution tracking. Version 2 is permissionless and open for integration.
Andamio SDK
Pre-built libraries and developer tools (JavaScript, Python, Go, Rust) for simple Andamio integration. Abstracts blockchain complexity, enabling developers to build on Andamio in days rather than months. Handles transaction building, signing, and protocol interactions.
Andamio API
Backend service serving coherent data from the Andamio Protocol. Provides query endpoints for SSoIs, Local State instances, credentials, and trust relationships. Enables applications to read protocol state without direct blockchain queries.
Andamio App
Open-source Next.js reference application demonstrating full protocol integration using the SDK and API. Provides interfaces for managing SSoIs, participating in Courses, contributing to Projects, and viewing trust relationships. Organizations can build custom applications following this implementation pattern.
Core Concepts
Access Token (Andamio Access Token)
Primary authentication mechanism using CIP68 standard. Each user has a token pair: 222 token (in wallet as proof of ownership) and 100 token (at Global State Validator containing SSOI data). Enables portable identity, credentials, and reputation across applications via a unique alias.
Self-Sovereign On-chain Identity (SSOI)
Decentralized identity framework enabling portable, self-controlled records of participation, achievements, and credentials across Andamio organizations. Uses CIP68 with 222 token (wallet ownership) and 100 token (data at Global State). Stores minimal on-chain data: alias and PolicyId → Hash pairs for local state participation. Detailed credentials live off-chain with on-chain hashes ensuring integrity. Organizations can recognize other organizations' credentials, creating a trust network. Only the 222 token holder can authorize identity updates.
Credentials
Cryptographically verified attestations of skills, achievements, or qualifications issued through the protocol and attached to a user's SSOI. On-chain verifiable, portable across platforms, and irrevocable once earned. Organizations can recognize other organizations' credentials as prerequisites, enabling permissionless trust networks.
Local State
Implementations of specific work scopes (courses, projects, future types) containing granular data and business logic. Each System (Course, Project) can have multiple Instances owned by Access Token Holders. Owners manage requirements and approvals; data represents work scope. Local states report to Global State as policy ID + hash pairs. Enables custom validator types while maintaining protocol interoperability through standardized SSOI format.
Instance Ownership
On-chain ownership of a specific Local State instance by a single Access Token holder with sole administrative control. Uses parameterized validators to create distinct instances from the same base code. Owner sets requirements, approves completions, and manages participants. One Access Token can own multiple instances. Ownership is instance-specific and currently non-transferable.
Global State
Protocol-level registry and index for all local states. Holds all users' 100 tokens (SSOI data) at a single validator address; users own via 222 tokens. Stores local state participation as policy ID + hash pairs. Instance Registry tracks authorized Local States that can write to SSoIs, preventing identity pollution. Creates trusted network where credentials come from registered sources.
Validators
Smart contracts enforcing protocol rules. Includes Global State Validators (protocol-wide) and Local State Validators (instance-specific).
Contributors
Access Token Holders participating in Local States. Called "students" in Courses, "contributors" in Projects. Earn Credentials from Courses (used as prerequisites for Projects). In Projects, commit to tasks defined by Project Owners and earn rewards upon completion.
Course System
Course Owner
Instance-specific role for Access Token Holders in Course Local States. Initial Course Owner is assigned at instance creation. Manages teacher access, course governance, and course lifecycle within their specific instance.
Course Teacher
An Access Token Holder assigned to assess student work within a specific Course Local State instance. Reviews and accepts or denies student assignment submissions.
Student
Contributor participating in a Course Local State. Earns Credentials by completing course requirements, used as prerequisites for Project access. Protocol treats Students and Contributors identically—both are Access Token Holders.
Course Module
A structured learning unit within a Course containing Student Learning Targets (SLTs), lessons, an assignment, and an introduction. Each module defines a scope of learning with its own content and assessments.
Student Learning Target (SLT)
An individual learning objective within a Course Module, formatted as an "I can..." statement. Each SLT is content-addressed by its blake2b-256 hash, making it a unique, verifiable identifier. SLTs define what students should be able to demonstrate upon completion.
Lesson
Instructional content tied to a specific Student Learning Target within a Course Module. Lessons deliver the learning material that prepares students to meet the SLT.
Assignment
Assessment activity within a Course Module. Students submit evidence of completion; Course Teachers review and accept or refuse submissions.
Project System
Project
Local State type with multiple on-chain validators (treasury, escrow). Coordinates work, manages funds, and tracks contributions through multi-validator architecture.
Project Owner
Instance-specific role for Access Token Holders in Project Local States. Initial Project Owner is assigned at instance creation and can add additional Project Owners or Project Managers. Manage treasury, approve commitments, and define task requirements within their specific instance. Can also participate as Contributors.
Project Manager
An Access Token Holder assigned to manage day-to-day operations within a specific Project Local State instance. Reviews contributor task submissions and manages contributor workflow.
Task
A discrete unit of work within a Project, content-addressed by its blake2b-256 hash. Contributors commit to tasks, submit evidence of completion, and Project Managers assess the work. Tasks have associated rewards from the Project Treasury.
Project Treasury
On-chain validator holding project funds and tracking approved work. Locks funds into escrow validators when contributors commit to tasks, enabling transparent management and automated disbursements.
Prerequisites (Prereqs)
Role-specific requirements contributors must meet to participate in project activities. Each role has its own escrow validator for managing commitments and rewards.
Escrow Validator
Smart contract locking tasks and rewards from Project Treasury when contributors commit to work. Each prerequisite set has its own escrow validator, ensuring payment upon completion.
Workflow
Commitment
A participant's on-chain pledge to complete work—an Assignment Commitment (student in a Course) or a Task Commitment (contributor in a Project). Commitments track lifecycle from enrollment through submission and assessment.
Assessment
Evaluation of submitted work by an authorized reviewer. Course Teachers assess Assignment Commitments; Project Managers assess Task Commitments. Decisions are accept or refuse.
Evidence
Proof of work submitted by students (for assignments) or contributors (for tasks). Evidence is hashed on-chain for integrity verification while detailed content is stored off-chain.
Credential Claim
Transaction to mint a credential NFT after meeting all requirements in a Course or Project. The credential becomes part of the user's SSOI and is portable across applications.
Technical Architecture
Protocol V2
Second major version of Andamio Protocol smart contracts, currently in audit. Improvements in scalability, security, and features.
Transaction API (Tx API)
RESTful API enabling protocol interaction without deep blockchain knowledge. Handles transaction building, signing, and submission.
Transaction Sponsorship (Tx Sponsorship)
Feature allowing organizations to pay blockchain transaction fees on behalf of users, removing Web3 adoption barriers.
Service Fees
Protocol fees charged for certain operations, creating sustainable revenue for Andamio Inc.
SDK (Software Development Kit)
Pre-built libraries (JavaScript, Python, Go, Rust) for simple Andamio integration. Target: days, not months.
Content Addressing
Technical pattern using blake2b-256 hashes as unique identifiers for protocol entities (SLT hashes, task hashes, evidence hashes). Ensures content integrity and enables verifiable references between on-chain and off-chain data.
Acronyms & Abbreviations
- API: Application Programming Interface
- CIP: Cardano Improvement Proposal
- CF: Cardano Foundation
- DAO: Decentralized Autonomous Organization
- RBAC: Role-Based Access Control
- SDK: Software Development Kit
- SLT: Student Learning Target
- SSOI: Self-Sovereign On-chain Identity
- TVL: Total Value Locked
This glossary is a living document. Terms are added and refined as the Andamio ecosystem evolves.