Architecture decision records (ADR)
An ADR is the permanent record of a decision that has been taken in Tamga Network and has become binding: what the problem was, which options were considered, what was decided and what follows from it. A closed decision changes only through a new ADR; the old record is not deleted but marked as superseded.
Trust
| No | Decision | Date | Status |
|---|---|---|---|
| 0001 | Besu QBFT ledger | 2026-07-29 | Accepted |
| 0004 | Institutional identity: X.509 | 2026-08-06 | Accepted |
| 0009 | Chainless beta and chain threshold | 2026-09-24 | Accepted |
| 0015 | Single trust interface | 2026-09-27 | Accepted |
| 0024 | Participant registration data | 2026-09-29 | Accepted |
| 0026 | Registration certificates | 2026-09-29 | Accepted |
| 0034 | HAIP 1.0 conformance | 2026-10-01 | Accepted |
| 0036 | Trust federation | 2026-10-01 | Accepted |
| 0038 | Sandbox: the test network | 2026-10-03 | Accepted |
Credentials
| No | Decision | Date | Status |
|---|---|---|---|
| 0006 | Credential format: SD-JWT VC | 2026-09-03 | Accepted |
| 0007 | Schema registry | 2026-09-09 | Accepted |
| 0008 | Where the status list lives | 2026-09-09 | Accepted |
| 0010 | Credential type identifier (URN) | 2026-09-24 | Accepted |
| 0014 | Events category | 2026-09-27 | Accepted |
| 0021 | E-mail and phone credentials | 2026-09-29 | Accepted |
| 0028 | Health credentials | 2026-09-29 | Proposed |
| 0029 | Schemas in the development stage | 2026-09-30 | Accepted |
Identity and privacy
| No | Decision | Date | Status |
|---|---|---|---|
| 0005 | Assurance model and stateless bootstrap | 2026-09-03 | Accepted |
| 0011 | Provisional identity attestation provider | 2026-09-25 | Accepted |
| 0013 | mdoc for the identity credential | 2026-09-26 | Accepted |
| 0022 | Class of the identity service | 2026-09-29 | Accepted |
| 0031 | Per-site pseudonyms | 2026-10-01 | Accepted |
| 0032 | Zero-knowledge proofs (ZK) | 2026-10-01 | Accepted |
Wallet
| No | Decision | Date | Status |
|---|---|---|---|
| 0012 | Proximity presentation | 2026-09-25 | Accepted |
| 0023 | Automatic copy refresh | 2026-09-29 | Accepted |
| 0025 | Wallet and key attestations | 2026-09-29 | Accepted |
| 0027 | Exporting the transaction log | 2026-09-29 | Accepted |
Services
| No | Decision | Date | Status |
|---|---|---|---|
| 0016 | Access to hosted issuance | 2026-09-27 | Accepted |
| 0017 | Access to verification results | 2026-09-27 | Accepted |
| 0019 | Institution Console | 2026-09-28 | Accepted |
| 0020 | The authentic source is the institution | 2026-09-29 | Accepted |
| 0033 | App store review code | 2026-10-01 | Accepted |
Governance
| No | Decision | Date | Status |
|---|---|---|---|
| 0002 | Sovereignty-first governance | 2026-08-05 | Accepted |
| 0003 | Value layer hooks | 2026-08-06 | Accepted |
| 0018 | Three doors to the documentation | 2026-09-27 | Accepted |
| 0030 | Product names | 2026-09-30 | Accepted |
| 0035 | Positioning | 2026-10-01 | Accepted |
| 0037 | Tamga Network is only a network | 2026-10-02 | Accepted |
Structure of an ADR
| Section | Content |
|---|---|
| Context | The situation and constraints that call for the decision |
| Decision | Numbered decision items (K1, K2, …) |
| Options considered | Alternatives, their pros and cons, why they were not chosen |
| Consequences | Affected documents, code and operations |
| Invariants | Binding rules that follow from the decision (e.g. ADR-0017/HV1); collected on the binding rules page |
| Status | Proposed → Accepted → (if needed) Superseded; date of acceptance |
Process
- It is written as a proposal (status: Proposed).
- Project management accepts it; the date is recorded and the decision is entered in the decision register under a
D-*code. - The affected specifications and Tamga ARF documents are updated in the same piece of work.