Proving that a document is real shouldn't take phone calls, apostilles and weeks. Tamga Network is a set of shared rules and signed lists that lets digital credentials from any institution be verified across borders, in seconds, while protecting the person's privacy.
Every state publishes its own list. Today Tamga runs the Türkiye list provisionally, on behalf of the state.
Schools, hospitals, chambers and companies issue documents every day. Yet proving that a document is real in another country, or even another institution, is still hard.
When an institution in Almaty wants to verify a document issued in Baku, it takes phone calls, emails, apostilles and weeks.
A scanned PDF or a photocopy is easy to alter; telling the real one from a fake takes expertise.
To prove your age you show your whole ID; to prove you graduated you show your whole transcript.
Each country builds its own digital system; they don't recognise each other or speak the same language.
The EU requires every member state to offer its citizens a digital identity wallet by the end of 2026. Without a shared trust structure, Turkic-world credentials stay outside that order.
That a credential issued by any institution in the Turkic world is accepted with the same confidence in another country. We do it with a shared network that no single company or state owns, run by open rules. Credentials stay on the person's phone; the person shows only what is needed; the verifier is sure in seconds, without asking the source.
The credential stays in the person's wallet. The person decides what to show.
The network sells no services and gives no one privileges. The goal: an independent foundation.
Every state owns its trust list and decides whom it recognises.
No personal data in lists, records or logs; not even a hash of it.
Every rule is numbered and public; every package is open source.
The institution that issues, the person who carries, and the party that checks. All three look at the same signed list; nobody has to phone anybody.
Every field is sealed on its own (salted hash); then the institution signs the whole credential with its key.
Tamga Network is not a new invention; it brings together tested techniques from Europe's digital identity framework for the Turkic world.
A document digitally signed by the institution (a credential). Change a single letter and the signature breaks.
Each field of the credential is locked separately. The person opens only the field that is asked for; the rest stay closed.
Proving that something is true without showing the thing itself. For example, that you are over 18 without showing your birth date.
"Sign in with Tamga" gives every site a different identifier for you (a pseudonym). The site recognises you but cannot match you with other sites.
That an institution really is that institution is read from a list signed by the state. The lists in turn are linked to a list of lists.
The list is re-signed on every change and chained to the previous one by hash; the public anchor log gets a new line every hour. No one can change it silently; anyone can verify it.
Tamga ARF, the Trust Framework, the Tamga Rulebook and the credential-type rulebooks.
In forceSigned, versioned national lists and the list of lists that points to them.
In forceSD-JWT VC and ISO mdoc; issuance with OpenID4VCI, presentation with OpenID4VP.
In forceVerification, issuance and wallet core; anyone can run them on their own server.
Pre-releaseWallets and service providers that follow the network's rules. The first wallet is Tamga Wallet.
On topOnce at least two independent operators join, the same records move to a permissioned ledger.
LaterRegister, get your key on the list, issue your first credential.
Join as an institution Wallet providersThe network doesn't pick wallets; it recognises them. Every wallet that follows the rules and passes the conformance tests is listed. Test your wallet in the sandbox first.
Start conformance tests StatesWhen you publish your own trust list, the network points to it; for wallets only the address changes.
Explore the federationTwo ways to check Tamga credentials on your site or app: the hosted verifier with a page kit, or your own server with @tamga-network/verifier.
ReadWhat the EU built with eIDAS 2.0 and its reference framework, when it applies, why alignment matters for states outside the EU, and where its limits are.
Read 8 October 2026 · StandardsWhat HAIP 1.0 fixes and how Tamga applies it, and how Token Status List revokes credentials without telling the issuer where they are used.
ReadTamga runs the network today, but the network is not Tamga's. The path is written down from the start: as states join, governance becomes shared; with two independent operators, the records move to a shared ledger.
Tamga publishes the Türkiye list on behalf of the state, with open rules and a public anchor log.
Lists are handed to their owners; the network's rules change by joint decision.
Records move to a permissioned ledger; no single party can change them alone.
Verify a credential on your own server. With the hosted verifier you don't even need server code.
npm install @tamga-network/verifier @tamga-network/trustThe packages are published on npm as the 0.6.0 test release; the stable 1.0.0 comes when everything is ready. In test releases the API may change.
import { fetchListTrustSource, verifyJws } from "@tamga-network/trust";
import { createPresentationRequest, dcqlFromPolicy } from "@tamga-network/verifier";
// 1. Load the trust lists (root fingerprint: tamga.network/trust-anchor)
const { source: trust } = await fetchListTrustSource("https://trust.tamga.network", http, {
rootFingerprints: [ROOT_FINGERPRINT],
verifyJws,
});
// 2. Create a signed request, show it as a QR code
const req = await createPresentationRequest({
signer,
dcql: dcqlFromPolicy(AGE_OVER_18_POLICY),
responseUri,
requestUriBase,
});
show(req.qrPayload);| European Union | Tamga Network | What it means |
|---|---|---|
| eIDAS 2.0 and implementing acts | Trust Framework | Who joins, who supervises, how it is handed over. |
| EU ARF | Tamga ARF 1.0 | Roles, architecture, trust model. |
| High-level requirements | Tamga Rulebook | Numbered, binding rules for every role. |
| Attestation rulebooks | Education · Identity · Event Ticket | Each credential type's own rules. |
| Trusted lists (LOTL) | Tamga LOTL and national lists | Same format; EU lists are read as external lists. |