Digital Trust Infrastructure

The shared infrastructure of trust in the digital world

Tamga Network is a Digital Trust Infrastructure where individuals, organizations and digital assets can be reliably identified and build verifiable relationships. Not a new blockchain — we turn the identity and verification problem that every application solves again and again into a shared service.

  • Open standards
  • SD-JWT VC
  • ISO mdoc
  • OpenID4VC
  • eIDAS 2.0 compatible

The problem

The world is leaving the “document copy” era behind

For decades we proved our identity by handing over copies of documents. This model has three fundamental problems — and the world is moving to a model that reverses it.

Data piles up everywhere

To prove your identity you hand a copy to an institution; that copy is stored on servers, duplicated, and slips out of your control. Privacy and security risk grows.

Everyone repeats the same work

Every bank, hospital and university builds the same verification from scratch. With no shared trust layer, each application reinvents the wheel.

Authenticity is left to the “copy”

A document’s validity is often left to how convincing a photocopy looks. We need a proof that can be verified cryptographically, without going back to the source.

The new model reverses this: data stays under the user’s control, only the necessary proof is shared, and verification happens cryptographically without contacting the source.

What we are

Not a new blockchain, but a shared trust layer

Tamga Network builds a world where digital trust is provided by a shared infrastructure rather than by each application alone. Four principles define this approach.

Digital identity is the starting point

Trust is the real value the infrastructure produces. Every entity is first represented by an identity: identity first, transaction second.

Signed trust lists today, a shared ledger later

Trust is anchored in signed, versioned trust lists — the model the EU itself uses. A permissioned ledger is added only when at least two independent operators join. Personal data is never written to either.

Users never see the plumbing

They only use their wallet. Trust lists, certificates and revocation checks run in the background — no fees, no technical steps.

Open standards are essential

SD-JWT VC and ISO 18013-5 mdoc, OpenID4VCI/VP, X.509 — the EUDI profiles. Commitment to shared standards, not to a specific vendor.

The platform

One credential, verified anywhere — no integration

The issuer signs a credential into the holder's wallet; the holder presents it to any verifier, who checks it against the signed trust lists without ever contacting the issuer. Personal data never enters the lists.

ISSUEsigns a credentialPRESENTshows only what's neededREGISTERpublishes its public keyVERIFYchecks issuer & revocationTRUSTno integration neededISSUERUniversity · X.509HOLDERCitizen · TamgaIDVERIFIEREmployer · RPTRUST LISTSDigital TrustInfrastructure
Personal data never in lists or logsX.509 institutions · a separate copy per verifierUnreachable infrastructure → never a false “rejected”

Where our name comes from

Tamga — an ancient seal, a modern proof

Tamga is the ancient seal of the Turkic tribes — a mark that proved ownership, belonging and authority. A tribe’s tamga proved to whom a good belonged and from whom a document came.

A verifiable digital document (Verifiable Credential) is precisely its modern counterpart: a digital seal. A shared tradition of the seal is the strongest symbol of a shared digital trust network.

What Europe is doing

eIDAS 2.0 and the EUDI Wallet

This is not just a European regulation; it is a de-facto standard for how identity and trust are established in the digital world.

The European Union, through the eIDAS 2.0 framework, requires every member state to offer its citizens a European Digital Identity Wallet (EUDI Wallet). Citizens carry their identity, diplomas, driving licence and health documents on their own phone and present them selectively.

SD-JWT VC, ISO mdoc, OpenID4VC and selective disclosure are no longer academic concepts but continent-scale requirements. The question is no longer “will this transformation happen” but “who will be a producer in it.”

The goal

Uniting the Turkic world on a shared foundation of trust

Digital trust need not stay within national borders. A diploma issued in one country should be verifiable in another; a company’s identity should be trusted across borders.

Sharing a common language, culture and history, the Turkic world of ~300 million people is a natural and vast foundation for cross-border verifiable identity. In the long run this vision takes shape as a Trust Mesh: each country keeps its own trust network while connecting to others through shared standards.

~300M

Common ground: population of the Turkic world

6+

Organization of Turkic States members/observers

1

Shared, interoperable trust standard

0

Personal data written to trust lists, logs or ledger

How it works

The Issuer — Holder — Verifier trust triangle

The standard model of eIDAS 2.0 and the EUDI Wallet. The source of authority is always an institution listed in a signed trust list.

Issues

Issuer

The organization that issues a verifiable credential (university, government, hospital).

Carries

Holder

The party that stores and presents the credential in their wallet (TamgaID) — usually the individual.

Verifies

Verifier

The party that verifies the presented credential cryptographically, without going back to the source.

Selective disclosure — proof of “over 18” without revealing the birth date

Credential Verified
issuerIdentity provider · X.509 (TR)
holderp:8f2a…c19

claims

age_over_18 disclosed
birth_date hidden
full_name hidden
signature: validrevocation: active

The result: higher trust by sharing less data.

Verifiable Credentials

Verify once. Present anywhere.

A credential is issued and signed once. You reveal only the fields you choose — the rest stay hidden as salted hashes — and any verifier checks the signature cryptographically, without ever going back to the issuer.

How selective disclosure works
Credential Verified
typeUniversity diploma
issuerExample University · X.509 (TR)
issuerId0x9f2a…c1
holderdevice key · this verifier’s copy
discloseddegree · graduation_year ✓
withheldgpa · student_no · birth_date
proofSD-JWT VC · selective disclosure
Example: a university diploma. The issuer is an X.509 institution listed in the national trust list; each verifier receives a different copy, so verifiers cannot link the holder.

Sign in

Sign in with TamgaID

Like “Sign in with Google”, but the identity is yours. A website asks for only the fields it needs; you approve each one on a consent screen; it never sees a password or a pool of your data.

Sign up once, then a passkey

No new password for every site. You sign up once with your wallet; after that, daily sign-in is a passkey on your device and no fields are shared again.

You choose what is shared

Prove you are over 18 without revealing your birth date; share a name without an address.

Phishing-resistant

There is no password to steal or leak — sign-in is a cryptographic proof from your device.

Verified when it matters

When a service must, it can know you are a real person whose identity document was checked — not an anonymous account.

Sign in to example.com

Continue with Google
Continue with Apple
or
Sign in with TamgaID
TamgaID

example.com wants to access:

Full name shared
Over 18 proven
Email shared
Home address hidden
Allow
Deny

No password shared · you control every field

Ecosystem

Starts with TamgaID, grows with vertical platforms

The infrastructure’s first end-user product is TamgaID — the wallet where a user creates their digital identity. On top of it, sector-specific platforms are built, all using the same trust layer. Education runs today; health, logistics and payments show where the same layer leads.

TamgaID

The wallet where a user keeps and presents their credentials. Like an EUDI Wallet: identity and diplomas, selective disclosure, a pass for turnstiles and event gates, and passwordless sign-in to websites. Free for individuals. Qualified e-signature is on the roadmap. TamgaID is not Tamga Network itself — it is the first door that opens onto it.

Education

Diplomas, transcripts and academic titles produced as internationally verifiable credentials.

Health

Physician credentials, patient consents and digital health records.

Logistics

From a customer confirming last-mile receipt in their wallet to international freight — trucks, drivers, cargo and customs verified end-to-end, with payment released on proof of delivery.

Payments

Authorizing payments between verified parties — settlement stays on regulated bank/CBDC rails, not on Tamga.

Where we are

Working today — and honest about the rest

Tamga is not a slide deck. The full flow runs end to end with real cryptography, and has been tested on a phone.

Today

Working today

  • Diplomas and student cards issued into the wallet (OpenID4VCI)
  • Only the requested fields are shared; verified in seconds (OpenID4VP)
  • Revocation and institution suspension reach every verifier
  • Remote identity check (document + liveness) → identity credential, also as ISO mdoc for age checks
  • Turnstile and event-gate pass; single-use tickets
  • Website sign-up with the wallet, daily sign-in with a passkey
  • Open-source packages @tamga-network/* (npm release pending)

Next

Pilot

  • One foundation university: diplomas and student cards
  • 30–100 volunteer graduates and 2–5 verifiers
  • The signing key held by the university, not by Tamga
  • Signed trust lists — no ledger yet

Later

Network

  • A permissioned ledger (Besu/QBFT) once at least two independent operators join
  • Trust lists run by the member states themselves
  • Close-range presentation (ISO 18013-5 over NFC/BLE) and the browser Digital Credentials API

Every first-release shortcut — sample records, software keys, a single operator — is listed openly in our deviation log and is closed before the pilot.

The EBSI of the Turkic world

If Europe’s infrastructure layer is EBSI, then Tamga Network is its counterpart for Türkiye and the Turkic world. Not a competitor, but interoperable. The same standards, our own sovereign network.

Layered model

Infrastructure = Tamga Network (like EBSI) · Application = TamgaID (like the EUDI Wallet).

States with equal power

Target: the states of the Organization of Turkic States run the network with equal votes. Today Tamga operates the trust lists provisionally, on behalf of the states — every structure already has a slot for each member state.

Sovereignty-first governance

Network membership by 2/3 validator vote · national registries governed only by their own state · cross-border recognition set unilaterally.

Accountable privacy

Today: each verifier receives a different copy of your credential, so verifiers cannot link you to each other. Design goal (research): identity resolvable only by a court plus a multi-institution threshold — never by any single actor.

Compatible yet independent

Built on the eIDAS 2.0 / EUDI profiles; data and governance stay in-country, in a sovereign architecture.

The modern counterpart of the ancient seal

We turn digital trust from a problem into an infrastructure

Read the documentation that explains the project from scratch, review the technical whitepaper, or take a look at our manifesto.