Skip to content
Tamga Network

Release notes

Release notes

This page lists every release of the network, with the newest at the top. Package versions are listed separately on npm, and Tamga Wallet keeps its own release notes.

  1. v1.0.0

    Latest
    Security

    Suspended issuers, identity credential renewal, future-dated credentials, packages 0.8.6

    Changed

    • While an institution is suspended in the trust list, its credentials are not accepted, including those issued before the suspension. When the suspension is lifted, the earlier credentials are accepted again. Apps should show this as "temporarily not accepted", not "invalid".
    • The wallet now gets the mdoc copy of the identity credential through the standard OpenID4VCI path, and renews the identity credential's short-lived copies regularly.
    • A credential whose validity starts at a later date is kept in the wallet but is not offered for presentation until that date.
    • The @tamga-network/* packages are on npm as the 0.8.6 test release. Credential type hashes changed; issuers and verifiers should use the current catalog and trust list. Apps using the zero-knowledge prover should be rebuilt after updating.

    Security

    • The zero-knowledge prover and verifier are rebuilt with an updated compression library that fixes a known vulnerability (RUSTSEC-2026-0344). The verifier no longer crashes its host when a prover process stops unexpectedly, and a malformed trust list is reported with the same error as any other bad list.
  2. v1.0.0

    Security

    Single-use consent, request fetched by POST, access certificate revocation, packages 0.8.5

    Added

    • The wallet core can fetch a verifier's request with POST and a fresh one-time value from the wallet (OpenID4VP 1.0). The verifier must return the same value in its signed request, so an old request cannot be replayed to the wallet. The existing GET path keeps working.
    • When a verifier's registration is suspended, revoked or expires, its access certificate is put on a revocation list in the same publication. Live in the sandbox today.

    Changed

    • The @tamga-network/* packages are on npm as the 0.8.5 test release. The zero-knowledge prover's Android libraries are rebuilt for 16 KB memory pages (a Google Play requirement); apps using it should be rebuilt after updating.

    Security

    • A consent the person gives in the wallet can be used only once and is bound to that request: the wallet will not send the answer if the request's state or encryption key changed after the consent screen.
  3. v1.0.0

    Feature

    Copies in face-to-face presentation, a final “is this you?” check, packages 0.8.4

    Added

    • Every face-to-face presentation still uses a fresh copy of the document, so two readers cannot link the person. The wallet core now reports how many copies are left and what to do when they run out: refresh first when online, or reuse the last copy only after the person accepts a clear warning when offline. The copy is marked as used before anything is sent.
    • When a document is issued after identity verification, the identity service can show the wallet a masked summary of the verified person (initials and birth year). The wallet asks “is this you?” and the document is issued only after the person confirms. This protects against a verification link that someone else forwarded.
    • Before the consent screen the wallet core can tell which fields the person already shared with this verifier and which are asked for the first time. Only field names and dates are used; values never leave the device.

    Changed

    • The @tamga-network/* packages are on npm as the 0.8.4 test release. All additions are optional; without them the behaviour is that of 0.8.3.
  4. v1.0.0

    Security

    The verifier returns only what was asked for, the wallet core ties registration to the signer, packages 0.8.3

    Changed

    • The @tamga-network/* packages are on npm as the 0.8.3 test release; the stable 1.0.0 comes when everything is ready.

    Security

    • The verifier now returns only the fields the verification policy asks for. The technical fields of a document and anything the wallet disclosed beyond the request are no longer in the result.
    • The verifier limits how far a revocation list may run ahead of its last anchor. When the list is newer than the latest anchor by more than one hour (the default), the result is “undetermined” instead of a decision. A site that verifies on its own server should reload the anchors more often than that.
    • The wallet core can tie a verifier's registration certificate to the certificate that signed the request. A self-signed certificate that copies a registered organisation's identifier no longer counts as that organisation.
    • The wallet core refuses http addresses by default, both in a document offer and in the address it returns to after a presentation. Local development needs an explicit option.
    • The trust list publisher stops when a record of the previously published list is missing from the new one or when a history row was changed. A removal goes through only with an approved entry that is bound to one list version.

    Applications built on the wallet core have to be updated, not only the package. For a local development server pass allowLocalDevHost. To get the registration certificate check pass signerTrust, and do not accept a result that says signerTrusted: false. When a document is issued after an identity presentation and the result comes back to the app's own address, pass that address as callbackUri. The steps are in the package changelog, in the 0.8.3 section.

  5. v1.0.0

    Feature

    The onboarding tool is on npm, the wallet core refuses ambiguous verifiers, packages 0.8.2

    Added

    • The onboarding tool @tamga-network/onboard is on npm for the first time. An institution's IT team uses it to prepare the registration application and check it against the registration rules, to create the institution's keys on its own computer, to check its own setup and, after joining, to check how the institution appears in the signed trust list. It writes nothing to the network or to the list and asks for no personal data.
    • The same tool works as a local MCP server, so the institution's own AI assistant can run the steps. It also has the steps for a state or an operator that will run a node of the shared ledger: creating the node key on its own machine, the declaration sent to the operator and a read-only check of the running node.

    Changed

    • The @tamga-network/* packages are on npm as the 0.8.2 test release, now ten packages; the stable 1.0.0 comes when everything is ready.

    Security

    • In the wallet core, a verifier whose name appears in more than one country's list without a recorded move is now treated as unregistered on every lookup path, also when the request names the verifier by its certificate. The person sees the “not found in the trust list” warning, and a request that needs a registration is refused.

    Install the onboarding tool with npm install -g @tamga-network/onboard. Its first release was published by hand without provenance; later releases come from the automated release workflow. No other package changed its API; details in the package CHANGELOG under “Behaviour changes in 0.8.2”.

  6. v1.0.0

    Security

    A fake answer cannot block the real wallet, ambiguous identities fail closed, packages 0.8.1

    Added

    • The trust lists' anchor log knows new kinds of lines, in preparation for a later mirror of the lists on a ledger. The ledger itself stays switched off.

    Changed

    • The @tamga-network/* packages are on npm as the 0.8.1 test release; the stable 1.0.0 comes when everything is ready.

    Security

    • A site that verifies on its own server now locks each copy of a presentation request separately and accepts an answer in one single step. A slow or fake answer on one copy can no longer hold up the real wallet's answer, and when two answers arrive at the same moment only one of them is accepted.
    • When a presentation comes through the browser (the Digital Credentials API), the intended audience is taken from the page's own address. An answer meant for another site is refused at the very first step, with a clear message.
    • When a wallet receives a document, the package now tells it if the issuing institution's registration status could not be checked, so the wallet can warn the person instead of staying silent.
    • For mdoc documents, what an institution is registered to ask for is checked together with its namespace: a field with the same name in another namespace no longer counts as allowed.
    • When the same identity (a verifier's name or a gate group) appears in more than one country's list, it is treated as unknown and closed. A move from one country to another is accepted only when the old country's signed list records the move in a structured form.

    Some behaviours changed in the safer direction. Developers who verify on their own server should accept an answer with tryConsume(): the old pattern that ended with consume() now throws PresentationAlreadyConsumedError instead of accepting a second answer. On the browser path, pass the page origin and leave aud out. Every change and its migration step are in the package changelog, under “Behaviour changes in 0.8.1”.

  7. v1.0.0

    Feature

    Expanded whitepaper in four languages, revised manifesto, roadmap by conditions

    Added

    • The whitepaper's expanded edition (still version 1.0, November 2026) in English, Turkish, Turkmen and Azerbaijani: twenty-four chapters on how the network works, why each major choice was made and where it is going, with every decision, the declared residual risks and the open questions in one place. The PDFs are on the whitepaper page.

    Changed

    • The manifesto was revised in all four languages and its PDFs were rebuilt.
    • The roadmap now follows the whitepaper: stages tied to conditions rather than dates (list stage, preparation, foundation, ledger, state participation, institutional expansion) plus research directions. The scenarios page says the same: institution credentials reach the real network as the first institutions join.
  8. v1.0.0

    Security

    Safer defaults: a fresh request for every fetch, status checks that fail closed, packages 0.8.0

    Changed

    • The @tamga-network/* packages are on npm as the 0.8.0 test release; the stable 1.0.0 comes when everything is ready.

    Fixed

    • The limit on how often a wallet may answer now applies to each request separately, so someone flooding their own copy of a request can no longer slow down the real person's answer.
    • A request copy is replaced only after the new one has been signed, and several fetches at the same moment can no longer go past the limit.
    • The wallet never swaps a registration-certificate status list for an older one, so a revocation, once seen, cannot disappear.
    • When a registrar moves its status list to a new address, the entries of the old list keep being followed and are closed with the publication.

    Security

    • A site that verifies documents with our packages now gets the safe mode without asking for it: every time a wallet fetches the presentation request, it receives its own fresh request. The old single shared request is produced only when a developer asks for it explicitly, and it will be removed in a later release.
    • A wallet reads the status of its own wallet unit strictly: only a clear “valid” lets it use the unit; a suspended unit is not used but is not deleted either, because suspension is temporary; a revoked unit, or a value the wallet does not recognise, counts as revoked.
    • A gate group is active only while the institution behind it is active. When that institution is suspended, revoked or leaves the trust list, its gates close together with the list.
    • On the real network, Tamga Verify takes the keys of gate terminals only from the signed trust list; a key set in the server's environment stops the service from starting. The sandbox is unchanged.

    0.8.0 has one breaking change for developers who verify on their own server: createPresentationRequest no longer returns one shared request object by default, so requestJwt is empty. Instead, give each presentation a BranchSet and let it serve a fresh request on every fetch; passing initialRequestObject: true keeps the old shape for one more release. Wallet developers should use a wallet unit only when its status is valid and delete it only when it is revoked. Every change and its migration step are in the package changelog, under “Breaking / behaviour changes in 0.8.0”.

  9. v1.0.0

    Security

    Protection against forged declines, registration-certificate status, gate groups, packages 0.7.4

    Added

    • Registration certificates on the real network and in the sandbox now name their policy (a Tamga identifier and the registration certificate policy page on arf.tamga.network) and point to a one-bit status list that is re-signed every hour. A wallet refuses a revoked certificate and warns the person when the status cannot be checked.
    • Gate groups are published in the trust list: each group names the institution that runs the gates and the pass types they may accept. An institution manages the terminal keys of its own gates in the Institution Console, and a gate is refused when its group leaves the list or the list is out of date.
    • The sandbox publishes its Türkiye list also in the ETSI TS 119 612 XML format, signed and with the same version as the signed list (trust.sandbox.tamga.network/tl-tr.xml). The real network's XML list follows once the foundation that will operate the list exists.

    Changed

    • The @tamga-network/* packages are on npm as the 0.7.4 test release; the stable 1.0.0 comes when everything is ready.

    Fixed

    • An independent test with an open-source EU test wallet in strict mode found five defects, all fixed the same day: registration certificates now state the format of each use, the browser path no longer requires a state value, a proof shared from a web page is bound to the page's origin, list signatures carry their signing time in the standard field, and a wrapped registration certificate is read.

    Security

    • Every fetch of a presentation request now gets its own request with a fresh state, nonce and encryption key, and a decline closes only its own branch. Someone who sees the QR code can no longer cancel the real person's presentation with a forged decline.
    • Every Tamga Verify page runs under a strict Content Security Policy with no inline script or style, and the docs site, the ARF site and Tamga Verify serve their fonts from our own servers, so no visitor's address goes to a third-party font host.
    • New property and fuzz tests led to three hardening fixes in the packages: a payload key named __proto__ is rejected, status lists with 4 and 8 bits per entry are read correctly, and a malformed request query is rejected cleanly.

    0.7.4 has breaking changes for developers. The most important: a proof shared over the browser's Digital Credentials API is now bound to the page's origin, so wallets and verifiers that use that path move to 0.7.4 together; registered uses for mdoc and zero-knowledge requests must name their format; the ETSI XML list signer has its own field in the list of lists (xml_signing_keys). Every change and its migration step are in the package changelog, under “Breaking / behaviour changes in 0.7.4”.

  10. v1.0.0

    Fix

    Verifier self-test fixes, packages 0.7.3

    Changed

    • The @tamga-network/* packages are on npm as the 0.7.3 test release; the stable 1.0.0 comes when everything is ready.

    Fixed

    • Fixes from the first verifier round of the OpenID conformance self-test: the signed presentation request no longer carries a non-standard purpose field, because the purpose a wallet shows comes from the verifier's registration certificate; the response endpoint answers with only the redirect address; display language tags in issuer metadata are written in canonical BCP 47 form, one entry per language.
  11. v1.0.0

    Security

    OpenID self-test fixes, gate terminal keys, packages 0.7.2

    Changed

    • Whitepaper and manifesto revised (still version 1.0, edition dated 27 October 2026) and rewritten in plain language in all four languages. The whitepaper now describes the network and Tamga Wallet as separate structures, the ledger code as written and tested but switched off, the OpenID self-test, the two age flags, gate terminal keys and remote signing for hosted issuance; the PDFs were rebuilt.

    Fixed

    • Fixes from the OpenID conformance self-test: the issuer's authorization server metadata, DPoP key binding, standard error codes, and revocation lists of external issuers are now checked as the standards require.

    Security

    • Gate terminals now prove who they are with an operator-issued terminal key; a photographed single-use ticket can no longer be spent by someone else. The packages are on npm as the 0.7.2 test release.
  12. v1.0.0

    Feature

    Browser sharing with ISO mdoc, stable pseudonyms, packages 0.7.1

    Added

    • The wallet core now answers the browser's ISO/IEC 18013-7 Annex C request (org-iso-mdoc) through the Digital Credentials API; the request must be signed by the reader for the calling site and carry a registration certificate.
    • Sandbox: a Digital Credentials API test page on the reference verifier (verify.sandbox.tamga.network/dc-api-test).

    Changed

    • A per-site pseudonym is now always derived from the site's registered domain, never from its access certificate, so renewing a certificate does not change anyone's pseudonym. The packages are on npm as the 0.7.1 test release.
  13. v1.0.0

    Security

    Safe package defaults, packages 0.7.0

    Changed

    • The @tamga-network/* packages are on npm as the 0.7.0 test release; code written for 0.6.0 needs the new inputs.

    Security

    • The @tamga-network/* packages now require every security input that affects the decision (trust anchors, status checks, the relying party's registration, the wallet's approval); a forgotten input is a rejection, and skipping a check has to be written explicitly.
    • Requests without a registration certificate are now refused by the wallet, remotely and in person (the warning period until 2028 is removed).
  14. v1.0.0

    Feature

    Tamga Wallet listed, EU alignment, packages 0.6.0

    Added

    • Tamga Wallet's wallet provider is listed as active in the trust lists of the network and the sandbox, which makes it the first listed wallet. The network lists wallets and runs none of them.
    • Browser verification on iPhone and Mac Safari (ISO/IEC 18013-7 Annex C); on desktop the browser path is the default and the QR code stays as a fallback.

    Changed

    • Identity-service credentials can no longer be suspended, only revoked (EU rule for identity credentials); mdoc credentials use the EU status-list format (CWT).
    • Requests without a registration certificate show a warning and default to "don't share"; from 2028-08-11 they are refused.
    • The @tamga-network/* packages are on npm as the 0.6.0 test release.
  15. v1.0.0

    Security

    EU format alignment and security fixes, packages 0.5.2

    Changed

    • Presentation requests follow the EU profile: issued-at time in the signed header, the certificate chain without the root, and one registration certificate per request.
    • Wallet attestations are read only in the standard EU form.

    Security

    • Revocation-list fetching re-checks every redirect and connects only to the checked address; issuer-controlled addresses can no longer reach internal networks.
  16. v1.0.0

    Feature

    EU PID names, short-lived ZK copies, embedded disclosure policy, packages 0.4.0 and 0.5.0

    Added

    • Institutions can set who may receive a credential type (embedded disclosure policy, ADR-0046). The wallet checks it offline; if it doesn't match, it warns and starts with "don't share".
    • Zero-knowledge over-18 checks use short-lived copies (at most 24 hours, refreshed silently by the wallet); a revoked identity gets no new copies (ADR-0044).
    • The trust packages read the EU's trusted-list format (ETSI TS 119 612, XML) and the Attestation Revocation List; the rulebooks follow the EU attestation rulebook template.

    Changed

    • The identity credential uses the EU PID attribute names: birthdate, and nationalities as a list (ADR-0045).
  17. v1.0.0

    Fix

    OpenID4VCI/VP Final and HAIP alignment, packages 0.3.0 and 0.3.1

    Changed

    • Issuance follows OpenID4VCI 1.0 Final: key attestations use the type key-attestation+jwt, error codes match the standard, and the nonce comes only from the nonce endpoint.
    • Revocation lists stay valid for 6 hours and are republished every 2 minutes: a revocation shows within minutes, and a short server outage does not stop checks. The revocation list endpoints keep no access log.
  18. v1.0.0

    Feature

    Network and wallets separated

    Added

    • New open package @tamga-network/zk: the wallet side of zero-knowledge proofs for mdoc credentials, made on the device (ADR-0032).

    Changed

    • Tamga Network runs no wallet (ADR-0042). It lists wallets in its trust list; Tamga Wallet, the network's first wallet, is a separate product and runs its own wallet provider.
    • One sandbox for everyone: wallet, institution and verifier developers test on sandbox.tamga.network.
  19. v1.0.0

    Feature

    First release

    Added

    • Rules: Tamga ARF 1.0 (the Architecture and Reference Framework), the Trust Framework, the Tamga Rulebook and the credential-type rulebooks (Education, Identity, Event Ticket).
    • Developer documentation in English and Turkish: guides, concepts, specifications, decisions and a glossary.
    • Open packages: @tamga-network/* on npm as test releases (0.x).
    • Services: the trust list publisher, Tamga Verify and the network's reference services.
    • Federation: reading external trust lists (ETSI TS 119 602).