Skip to content

Commit ad75acf

Browse files
committed
move image place, add PKI, EUDI and mDL
1 parent 561a2bc commit ad75acf

File tree

1 file changed

+25
-10
lines changed

1 file changed

+25
-10
lines changed

content/en/blog/ssi-learnings/index.md

Lines changed: 25 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,11 @@ date: 2025-04-15
33
title: "Rethinking SSI"
44
linkTitle: "Rethinking SSI"
55
description: "
6-
Most of us are familiar with the concept of fast and slow thinking. But fewer
7-
may have noticed the other side of that same coin — how our intuition evolves
8-
over long periods of reflection. This post is a summary of thoughts that
9-
surfaced more than a year after we actively explored SSI technologies.
6+
Most of us are familiar with the concept of [fast and slow
7+
thinking](https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow). But fewer may
8+
have noticed the other side of that same coin — how our intuition evolves over
9+
long periods of reflection. This post is a summary of thoughts that surfaced
10+
more than a year after we actively explored SSI technologies.
1011
"
1112
author: Harri Lainio
1213
resources:
@@ -32,6 +33,10 @@ In the SSI space, three roots of trust have emerged:
3233
3. **Self-certifying trust**, where entities define and prove trust
3334
relationships without requiring centralized or consensus-based validation.
3435

36+
{{< imgproc trust-layers.png Resize "600x" >}}
37+
<em>Root of Trust Models — Foundations for Security & Sovereignty</em>
38+
{{< /imgproc >}}
39+
3540
This last model—**self-certifying trust**—is both the most ambitious and the
3641
most necessary if we are to realize the full potential of self-sovereign
3742
identity. From our experience, SSI will never become truly decentralized or
@@ -42,6 +47,19 @@ This raises an important question: Should we approach identity-related use cases
4247
through an **algorithmic zero-trust** lens, or should we aim for a
4348
**decentralized trust model based on self-certification**?
4449

50+
Or should we simply **build identity around PKI**, as seen in current
51+
government-led approaches like the **mobile Driver’s License (ISO mDL)** or the
52+
**EUDI Wallet**? These systems rely on administrative trust models — and while
53+
they may not be decentralized, they offer well-understood security, strong
54+
governance, and user familiarity.
55+
56+
What seems increasingly clear is that **these approaches are not mutually
57+
exclusive**. To build inclusive, resilient, and user-friendly identity systems,
58+
we may need to **combine the reliability of PKI, the resilience of algorithmic
59+
trust, and the sovereignty of self-certification**. The future of identity
60+
likely lies in how well we can bridge and blend these trust models — not in
61+
picking one over the others.
62+
4563
## Algorithmic Zero-Trust
4664

4765
Algorithmic zero-trust is a model where **no actor is implicitly trusted**, and
@@ -82,10 +100,6 @@ chains**. It enables **privacy, sovereignty, and interoperability**—but also
82100
requires new tooling to reason about trust, detect fraud, and handle revocation
83101
and rotation.
84102

85-
{{< imgproc cover.png Resize "600x" >}}
86-
<em>Root of Trust Models — Foundation for Sovereignty</em>
87-
{{< /imgproc >}}
88-
89103
## Key Learnings from Real-World SSI Projects with Hyperledger Indy
90104

91105
These aren’t just technical findings — they’re observations about what truly
@@ -121,7 +135,8 @@ depending on centralized platforms.
121135
Each time a client connects, it must authenticate itself from scratch.
122136
Persistent identity lives server-side, and the user is just a temporary session.
123137
This has contributed directly to the rise of **centralized identity silos** and
124-
the dominance of platform-centric Web2 services.
138+
the dominance of platform-centric [Web2](https://en.wikipedia.org/wiki/Web_2.0)
139+
services.
125140

126141
What if clients — or more accurately, **identity agents** — had persistent state
127142
of their own? What if they could maintain ongoing relationships with services,
@@ -171,7 +186,7 @@ the source of trust for both human-facing and machine-mediated interactions.
171186
IoT use cases — such as identity for machines, devices, or wearables — are real
172187
and growing. These actors often lack screens, keys, or user interfaces,
173188
requiring lightweight agents and trust protocols that work in constrained
174-
environmentsr
189+
environments.
175190

176191
### Revocation, Rotation, and Recovery Remain Fragile
177192

0 commit comments

Comments
 (0)