Skip to content
ADR-0035Architecture decisionAcceptedversion 1.0.04 November 2026

Partly changed by ADR-0037 and ADR-0042 (2026-10-02, 2026-10-06): the services of the third layer moved outside the network, to a separate company; Tamga Network is only a network and sells no services. The base (EU compliance), the federation layer and PO1–PO4 still apply. Tamga Wallet is not part of the network either: the network runs no wallet and knows wallets through the trust list (ADR-0042, 2026-10-06).

Context ​

It emerged that TÜBİTAK BİLGEM has an EU-compatible wallet and a test environment. This information comes from a single source and its official status is unknown. But the direction is clear: a state-backed wallet and person identification data (PID (Person Identification Data)The core identity data a state issues at the highest assurance level. Tamga does not take this role; its identity credential is not a PID.) path is forming in Türkiye. The analysis is in private documents (2026-10-01).

Two misunderstandings needed clearing up:

  1. "EUDI WalletThe European Digital Identity Wallet defined by eIDAS 2.0; Tamga uses the same formats and protocols." is a legal title. It means a wallet provided or recognised by an EU member state and certified under EU rules. A wallet from an organisation outside the EU (Tamga Wallet as well as the TÜBİTAK wallet) cannot hold this title today, nor use the EU Trust Mark. What it can be is EU-compatible: speaking the same standards and proving it through testing.
  2. EU compatibility is not an alternative to the paths but their common ground. There is no choice between "an EU-compatible wallet + services" and "Tamga Network". The network is a layer placed on top of the EU standards.

Three paths were considered:

  • Path 1: an EU-compatible wallet and services only.
  • Path 2: first a heavy, EU-like network and institution.
  • Path 3: a layered structure.

Decision ​

Path 3: three layers, each able to stand on its own.

  1. Base: EU compatibility. Credential formats (SD-JWT VC (Selective Disclosure JWT Verifiable Credential)The JSON-based credential format with selective disclosure, used for online presentation in the EUDI Wallet and in Tamga., ISO mdocThe ISO/IEC 18013-5 mobile document format, encoded in CBOR; used for in-person presentation and for the mobile driving licence.), protocols (OpenID4VCI (OpenID for Verifiable Credential Issuance)The protocol an issuer uses to deliver a credential to a wallet./VP, HAIP (High Assurance Interoperability Profile)The OpenID4VC profile that fixes the choices for high-assurance use, as in the EUDI Wallet.), the trust model (LOTL (List of Trusted Lists)The signed list that points to the countries' trust lists, their signers and their recognition status. → country lists, ETSI (European Telecommunications Standards Institute)The European standards body that writes the technical standards for trust lists, signatures and trust services. formats) and the registration model follow EU standards. Even if the network never grows, this layer is valuable on its own.
  2. Tamga Network: a light federationA model in which each country runs its own trust list and a list of trusted lists brings them together; Tamga can also show external lists..
    • The network does not select wallets, it recognises them. Any wallet providerThe organisation that offers a wallet, registers its wallet units and signs wallet and key attestations. Each wallet runs its own provider; the network does not run one, it lists them in the trusted list. that follows the published rules (ARF (Architecture and Reference Framework)The document set that describes roles, architecture, trust model and rules. Tamga ARF follows the structure of the EU ARF., rulebookA set of binding rules. The Tamga Rulebook holds the rules for all participants; each credential type has its own rulebook that branches from it.s) and passes the conformance tests can be listed.
    • The network's real job is to collect country lists and introduce them to each other. Today Tamga operates the Türkiye list on an interim basis. When the state, or an institution it authorises, publishes its own list, the Tamga LOTL points to that list's address and signer. For wallets and verifierThe party that checks a presented credential: signature, issuer in the trust list, status and policy. Also called relying party.s only the address changes (the ADR-0009 hand-over goal). The same applies to every Turkic state.
    • No heavy institution is set up on day one. Today Tamga is the interim operator. When one or two states are willing to join, a governance body (council or foundation) is formed, the lists are handed over and the ledger arrives (ADR-0009: at least two independent operators).
  3. Products and services.
    • Tamga Wallet: the network's first and reference wallet, but not locked to the network; it works in any EU-compatible environment. It makes no claim to be a national identity wallet. Its strengths are pseudonymA stable account identifier the wallet derives separately for each website; two sites cannot link the same person.s, zero-knowledge proofs (ZK (Zero-Knowledge proof)A proof that a statement is true without revealing the underlying data, for example "over 18" without the birth date.), tickets and credentials of the Turkic world.
    • Services (Institution Console, Tamga Verify, institutions' self-registration, a test environment, integration and SDK support, consulting, the provisional identity service) are offered on top of the standards. An institution issues its credential to whichever compatible wallet the person chooses; verification works whichever compatible wallet it comes from.
    • The services are not separate software: they are the running services offered to institutions. The separation is at the level of brand, contract and responsibility.

Invariants ​

CodeRule
PO1Tamga's credential, protocol and trust list formats do not depart from EU standards; every Tamga-specific addition uses a standard extension point and does not break standard clients.
PO2Tamga Network recognises a wallet not by its name but by the published rules and conformance tests; any wallet provider that follows the rules can be listed.
PO3The state roles Tamga holds on an interim basis (list operator, registrar, root CA, provisional identity provider) are designed to be handed over; on hand-over only the address and signer change on the credential, wallet and verifier side.
PO4In public texts Tamga Wallet is not presented as an "EUDI Wallet" or a "national wallet"; the correct wording is "EU-compatible wallet", backed by conformance test results.

Rationale / alternatives ​

OptionResultWhy
Path 1: EU-compatible wallet + services onlyrejected (as the main direction)Fastest start, but little distinctive value, and it shrinks when the state wallet arrives. Path 3 already includes it.
Path 2: heavy network and institution firstrejectedWithout states the network stays unused for years; high early institution cost, no basis.
Path 3: layeredacceptedMatches the architecture exactly; services and the wallet are usable now, the network grows over time, and when the state wallet and lists arrive the value is not lost — the federation's value grows.

Known tension: the EU deliberately separates roles. An institution that runs the list and also sells services has a conflict of interest. One team is enough today, but later the network's governance (council or foundation) and the service company must separate. Public communication already shows this separation through names and documents.

Consequences ​

  • Federation gate. Country lists with external signers, reading the ETSI format and recognising external wallet providers are opened by a separate ADR (ADR-0036).
  • EU identity. Verification of EU identity (PID) and driving licence (mDL (mobile Driving Licence)A driving licence held in a wallet in the mdoc format (ISO/IEC 18013-5).) types is added (ADR-0036).
  • Wallet and console. A "institutions I shared with" screen is added to the wallet; self-registration for verifying institutions comes to the Institution Console (design now, build after the store release).
  • Public communication. The site, whitepaper and presentations are organised around the three layers. The ARF and the developer docs are simplified according to this positioning.

Legal note — recognition in the EU (2026-10-13) ​

This note does not change the decision; it records the position that became clear in EU law during the first EU alignment review (2026-10-13).

  • Article 5f is not third-country recognition. Article 5f of eIDAS 2.0 (Regulation (EU) 910/2014 as amended by Regulation (EU) 2024/1183) is the obligation of public bodies and the private sector inside the EU to accept EU wallets. It is not a way to recognise a wallet or a trusted list from outside the EU.
  • For countries outside the EU the only open basis is Article 14. Article 14 makes the services of trust service providers established in a third country equivalent in the EU through an agreement between the Union and that country (Article 218 TFEU) or through implementing acts of the Commission; reciprocity and the other side's trusted list are required. Its scope is trust services (for example qualified e-signatures, e-seals, qualified EAAs). The parties are states: Türkiye or another Turkic state; Tamga Network cannot be a party to such an agreement.
  • The regulation has no path for a non-EU wallet to count as an "EUDI Wallet". This is why PO4 applies.
  • The network's role is technical preparation: trusted lists in ETSI formats (ADR-0036), certificates with ETSI profiles (ADR-0050), state roles that can be handed over (PO3). When a state takes the agreement route, the technical ground is ready.
  • In the short term a relying party in the EU can accept Tamga credentials only of its own accord (by adding our trusted list to its own trust source); this is not legal recognition and is not presented as such.

Public material (site, ARF, presentations) follows this note: phrases such as "mutual recognition with the EU" or "valid in the EU" are not used; the correct wording is "built on EU standards, EU-compatible" and "legal recognition requires an agreement between states".

Status ​

Accepted — 2026-10-01 (project management approval; the verbatim quote is in the private approval record). The third layer ("products and services") was changed by ADR-0037: Tamga Network is only a network and sells no services; commercial services sit outside the network. PO1–PO4 remain in force.

Legal note (2026-10-13): Article 5f is not third-country recognition; for countries outside the EU the only open basis is Article 14 (trust services only, an agreement between states). The decision does not change. Approved by project management (first EU alignment review, decision 13).

Note (2026-11-04): the revenue wording in the rationale table was replaced by the technical rationale ("little distinctive value", "high early institution cost, no basis"); the decision content is unchanged (project management).