Students are commitments
A learner appears on chain only as a scoped student_commitment. No name, no identifier, no address that resolves to a person.
04.1Learning management
A learning management system that behaves like every other one. Educators build courses, enrol students, mark work, and issue transcripts. Underneath, identity runs on SUMail, material sits on SNIP, and the academic record settles on SUM Chain as a commitment that carries no personal data.
A surface inside the SUMail product layer rather than a product of its own. It is the proof that the stack is usable: decentralized infrastructure behind a conventional registrar workflow.
A learner appears on chain only as a scoped student_commitment. No name, no identifier, no address that resolves to a person.
Transaction sender is always the institution or its sponsor. A student never needs a balance to hold a transcript.
Raw grades, submissions, and answer keys never reach chain state or the read RPC. Only the commitment does.
Values are taken from the protocol repository and from live chain parameters.
Tadris specification
| Catalog and offering | SRC-817 and SRC-818 |
|---|---|
| Credential subcodes | SRC-810 degrees, SRC-811, SRC-812 |
| Student identity | Scoped commitment only, 32 bytes |
| Transaction sender | Institution or sponsor, never the student |
| On-chain payload | Commitment, public metadata, issuer signature |
| Excluded from chain | Grades, submissions, answer keys, personal data |
| Material storage | SNIP |
| Identity and mail | SUMail |
| Activation height | 8,900,000 |
| Read RPC | src817_*, src818_*, read-only |