Skip to content

Commit 87465f8

Browse files
committed
new image + chapter update
1 parent b813720 commit 87465f8

File tree

1 file changed

+46
-7
lines changed

1 file changed

+46
-7
lines changed

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

Lines changed: 46 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -95,12 +95,46 @@ Transitive trust models — the foundation of any decentralized Web of Trust —
9595
lack global context and require custom trust policies per verifier. Bridging
9696
isolated trust domains without creating new chokepoints is still an open issue.
9797

98-
### Persistent, Symmetric Communication Is Essential
99-
100-
DID-based communication (e.g., via DIDComm) works best when agents can maintain
101-
long-lived, symmetric channels. Interruptions or short-lived agents complicate
102-
authentication, negotiation, and credential exchange, especially in mobile and
103-
IoT environments.
98+
### Why Symmetric Communication Matters
99+
100+
>
101+
> **💡 From Sessions to Relationships**
102+
>
103+
> Traditional web services treat identity as a temporary session.
104+
> SSI flips the model: identity becomes **persistent**, **portable**, and **relational**.
105+
>
106+
> Instead of logging in, users bring their agent.
107+
> Instead of onboarding, services recognize credentials.
108+
> No accounts. No passwords. Just trust — established cryptographically,
109+
> remembered across time and channels.
110+
111+
The Internet was built on the client/server model — efficient, scalable, and
112+
simple. But it also created a core asymmetry: servers are persistent and
113+
authoritative; clients are ephemeral and disposable. This model has made it
114+
nearly impossible for users to maintain continuity across interactions without
115+
depending on centralized platforms.
116+
117+
Each time a client connects, it must authenticate itself from scratch.
118+
Persistent identity lives server-side, and the user is just a temporary session.
119+
This has contributed directly to the rise of **centralized identity silos** and
120+
the dominance of platform-centric Web2 services.
121+
122+
What if clients — or more accurately, **identity agents** — had persistent state
123+
of their own? What if they could maintain ongoing relationships with services,
124+
carry trust context across channels, and even operate across devices or over
125+
time?
126+
127+
**Symmetric, peer-to-peer communication models** like DIDComm make this
128+
possible. Instead of logging in and starting over, agents can resume where they
129+
left off — with **long-lived, secure relationships** that don't require
130+
sign-ups, onboarding flows, or federated logins. Trust becomes transitive,
131+
contextual, and user-controlled.
132+
133+
This model reimagines the client not as a throwaway session but as a
134+
**sovereign, persistent identity**. And it enables a future where servers don’t
135+
need to authenticate every visitor — they can simply recognize known agents,
136+
verify their credentials, and interact accordingly. No password, no registration
137+
— just relationship-based trust.
104138

105139
### Privacy Requires Active Design
106140

@@ -132,7 +166,7 @@ the source of trust for both human-facing and machine-mediated interactions.
132166
IoT use cases — such as identity for machines, devices, or wearables — are real
133167
and growing. These actors often lack screens, keys, or user interfaces,
134168
requiring lightweight agents and trust protocols that work in constrained
135-
environments.
169+
environmentsr
136170

137171
---
138172
### Revocation, Rotation, and Recovery Remain Fragile
@@ -154,6 +188,11 @@ are short-lived, purpose-bound, and easily replaceable**, with **certification
154188
chaining** providing continuity of identity without creating a single point of
155189
fragility.
156190

191+
{{< imgproc key-layers.png Resize "400x" >}}
192+
<em>Key Hierarchies — Key Certification Chaining</em>
193+
{{< /imgproc >}}
194+
195+
157196
A self-sovereign identity system that cannot manage keys in a nuanced and
158197
layered way cannot scale. Identity needs to be **resilient, renewable, and
159198
gracefully degradable**—not brittle or tightly coupled to a single cryptographic

0 commit comments

Comments
 (0)