First-time setup
User Verifies identity with national eID (BankID/MitID) → credentials stored in EUDI Wallet on device
User Generates a DID (did:web or did:key) — keys created and held locally. This becomes the canonical identity across all platforms and protocols.
User Joins Inlägg, presents EUDI credential via OpenID4VP → selective disclosure: only "verified human, age ≥ 18"
Inlägg Creates ActivityPub actor linked to user's DID, requests Idun node to issue IdunVerifiedHuman credential
Idun node Issues signed credential anchored to DID → stored in user's EUDI Wallet + discoverable via DID document
Server shutdown recovery
Inlägg Goes offline unexpectedly
Network Federated peers (both AP and AT Proto) still hold follow relationships, replicated social graph data, and cached profiles
User Joins Innlegg, presents EUDI Wallet credential + proves ownership of DID via key signature
Innlegg Verifies DID ownership via Idun protocol, creates new actor linked to same DID
Network Federated peers recognise the DID, automatically redirect follows to new actor URI. All credentials still valid in wallet.
Cross-platform reputation
User Active on Inlägg for 2 years, good standing, no abuse flags
Inlägg Issues IdunReputation attestation signed by Inlägg's Idun node → stored in user's wallet, anchored to DID
User Joins new photography community running on Idun protocol
Community Reads reputation credential from wallet — user gets trusted status immediately instead of starting from zero
Cross-protocol interaction
User A On Inlägg (ActivityPub), verified via Idun with DID did:web:idun.org:alfred
User B On Bluesky (AT Protocol), verified via Idun with DID did:plc:xyz789
Bridge Bridgyfed or similar bridge translates AP ↔ AT Proto interactions. Both users' Idun verification status is visible across the bridge.
User A Sees User B as a verified human with 18 months of reputation — trust signal works regardless of which protocol each user is on