Skip to content

Specifications ​

The specifications are the exact rules of Tamga Network: how a belge (credential)Belge verenin imzaladığı ve kişinin cüzdanında duran dijital belge; kişi yalnız istenen alanları gösterir. is written, how it is issued and presented, and the format of the trust listsBir ülkenin kök sertifikalarını, belge verenlerini ve kayıtlı relying party'lerini taşıyan imzalı liste. Bugün Tamga'da güven bu listelere dayanır; ortak defter sonra gelir.. The code follows them; the conformance tests (conformance/) check them.

If you are new, read the Concepts pages and the Get started guides first; come to a specification when you need the exact wording of a rule. Every specification opens with a short "In brief" section; the rules and the detail follow.

Credentials ​

SpecificationWhat it covers
SPEC-CRED-0001The overall frame of the credential format and protocols
SPEC-CRED-0002How an SD-JWT VC credential is written, byte by byte
SPEC-CRED-0003Revocation and the status list

Protocols ​

SpecificationWhat it covers
SPEC-PROTO-0001An issuer issuing a credential to a wallet (OpenID4VCI)
SPEC-PROTO-0002A wallet presenting a credential to a verifier (OpenID4VP)
SPEC-API-0001The verification pipeline and the service API

Trust and identity ​

SpecificationWhat it covers
SPEC-TRUST-0001The format and publication of the trust lists
SPEC-ID-0002Institutional identity: X.509 certificates
SPEC-ID-0003Identity proofing before a credential is issued

Schemas ​

SpecificationWhat it covers
SPEC-SCHEMA-0001The schema catalogue (schemas.tamga.network)
SPEC-SCHEMA-0002Education schemas: student certificate and diploma
SPEC-SCHEMA-0003Skeletons for other sectors and the conditions for opening them

Wallet ​

SpecificationWhat it covers
SPEC-WALLET-0001The internal rules of a compatible wallet

Identifiers (SPEC-…) are permanent: references do not break when a file name or title changes. The single list of all binding rules: Binding rules.

Specifications for the ledger stage (trust-layer contracts, agent delegation) are not used today; they are kept in the repository under docs/ledger/.