Transaction sequences
The transaction workflows that issue an Andamio credential — and the course↔project symmetry that runs through all of them.
A single Andamio transaction rarely means much on its own. What issues a credential is a sequence of transactions — onboarding, authoring, committing, assessing, claiming. These pages walk each essential sequence step by step: for every step you see who acts, the transaction they submit, its on-chain effect (validator action + token change), and the resulting state. Every step shares the same transaction lifecycle, so that's explained once on the protocol intro and linked from each step rather than repeated.
Start here: onboarding
Everything else assumes the participant already holds an Access Token. Minting one is the protocol's front door:
- Onboarding — Mint Access Token → (
global_state: MintLocalState)
The course ↔ project symmetry
Courses and projects are deliberately symmetric. Both run the same five-beat loop — create → populate → commit → assess → claim — one for learners, one for contributors. Read across a row to see the same beat on each side; follow a cell into its interactive sequence.
The two left-hand sequences cover the operator side of each loop (create + populate); the two right-hand sequences cover the participant side (commit + assess + claim).
The sequences
Course
- Author & operate → — create a course, manage its modules, manage teachers.
- Learn & earn → — commit to an assignment, submit evidence, get assessed, claim the credential.
Project
- Author & operate → — create a project, manage managers, manage tasks, fund the treasury.
- Contribute & earn → — commit to a task, submit work, get assessed, claim the credential.
For what each validator action does, see Validators. To start building these transactions, see the API.