From signed lists to a shared ledger

1. Working

   Phase B — signed trust lists

   The full flow works end to end with real cryptography.

   • issuing and presenting student credentials and diplomas; revocation and suspension
   • identity check and identity credential, also as ISO mdoc
   • campus and event passes, single-use tickets; website sign-up and passkey sign-in
   • Institution Console, signed issuer metadata, registration certificates
   • open-source packages on npm (pre-release 0.1.0)
2. In progress

   Before the pilot

   What an institution needs before real people use it.

   • Tamga Wallet on the App Store and Google Play
   • keys in the phone's secure hardware; device attestation (App Attest / Play Integrity) required
   • the institution's signing key in the institution's own key vault
   • the first connection to an institution's own lookup endpoint
   • showing credentials in person over Bluetooth and from the browser (coded, device testing next)
3. Pilot

   Pilot

   One university, a limited group, success and stop criteria set in advance.

   • issuer key at the university; lists, no ledger
   • student credential and diploma; campus access
   • cross-testing with EU reference wallets and verifiers
4. Later

   Phase 0 and Phase 1

   More operators, more states, more formats.

   • a permissioned Besu / QBFT ledger once at least two independent validator operators sign
   • member-state trust lists; each state registers its own institutions
   • close range over NFC; reader authentication
   • a Europass-compatible representation of education credentials (under evaluation)
5. Research

   Research directions

   Studied, not yet planned; independent security review before any use.

   • zero-knowledge credentials against tracking by the issuer
   • per-site pseudonyms; accountable disclosure
   • institution wallets (organisations as holders)

Details: the whitepaper's “Status and roadmap” and “Known limits” sections.