Tamga Network

Chapter 6 · 7/8

Open source

Packages, licences and conformance tests: everyone can use the same code and get the same result.

4 min

However open a trust network’s rules are, if the software that applies them is closed, nobody can be sure of the outcome. That is why Tamga Network keeps its code open: anyone can read it, run it and audit it.

Packages

The network’s software is split into small, separate packages. A verifier can use just the verification package, a wallet developer just the wallet core:

  • trust: reads and verifies the signed trust lists.
  • verifier: end-to-end verification of a credential; building requests.
  • issuer: issuance and status-list publishing.
  • wallet-core: the core of a wallet: keys, receiving and presenting credentials.
  • sd-jwt, mdoc, schemas, core: credential formats, the credential-type catalogue and shared building blocks.

Licences

The code is licensed under Apache-2.0, the documents under CC BY 4.0. Institutions and companies can freely use and change the code in their own products and share the documents with attribution.

Conformance tests

Two different pieces of software applying the same rules must reach the same result. For that the network has conformance testsA ready-made test set anyone can run to check whether software follows the network's rules.: sample credentials and their expected results. A wallet, verifier or issuer shows that it follows the network’s rules by passing them. Using Tamga’s packages is not required to pass; any implementation that follows the specification can.

Summary

  • The network’s software is open-source, in small packages; anyone can read, run and audit it.
  • Code is Apache-2.0, documents are CC BY 4.0.
  • Conformance tests show that any software following the specification reaches the same result.

Go deeper

Technical details and binding rules: