Identi3

This session presents the results of a six-month proof of concept run by Telefónica Tech, GSMA, Dock Labs, and TMT ID to rebuild call center authentication using mobile network APIs and verifiable credentials. The PoC completed authentications in under 60 seconds on average, with 100% of trialists saying they would prefer it over existing methods.
Guests:
- Glyn Povah, Global Product Development Director at Telefónica Tech
- Helene Vigue, Identity and Data Director at GSMA
Timestamps
(00:00) - Introduction and context
(00:28) - Guest introductions: Glyn Povah (Telefónica Tech) and Helene Vigue (GSMA)
(04:34) - Strategic context: why call center impersonation fraud prompted this PoC
(07:00) - The problems with current authentication: CLI spoofing, SIM swap, knowledge-based checks
(08:32) - PoC goals: speed, security, and privacy
(10:17) - GSMA perspective: scam as a global cross-industry problem
(14:41) - Demo video: how the authentication flow works
(16:26) - PoC results: trialist feedback and quantitative outcomes
(20:32) - Carrier perspective: commercialisation, network APIs, and next steps
(22:09) - The wallet ecosystem: complexity, government-led development, and commercial tension
(30:05) - Identity industry perspective: user experience design choices and distribution challenges
(37:10) - The extensibility of verifiable credentials beyond call center authentication
(44:06) - Audience Q&A
📚 EXPLORE:
Website - https://www.dock.io/
LinkedIn - https://www.linkedin.com/company/docknetwork/

In a recent webinar, Richard Esplin, Head of Product at Dock Labs, and Agne Caunt, Product Owner, walked through a live demo of our new browser-based approach to digital identity.
Through a step-by-step demo, Agne showed how this works in practice, from signing into newly acquired platforms without re-onboarding, to verifying identity with external partners using privacy-preserving credentials. Along the way, they explored the underlying architecture, trade-offs around security and decentralization, and how this model can unlock both better user experiences and new business opportunities.
(00:00) Introduction
(01:47) The problem: fragmented identity across systems
(06:08) The shift: reusable digital identity
(06:40) Demo begins
(15:31) Architectural shift to user-held identity
(16:24) Web and mobile wallet with shared storage
(18:21) Issuance from trusted data
(20:18) Verification with proof requests
(27:17) Fraud model and Dock Labs' role
(43:48) Decentralization trade-offs
(48:08) Business wallets and delegation
Website - https://www.dock.io/
LinkedIn - https://www.linkedin.com/company/docknetwork/

AI agents are quickly moving from experimentation to real-world deployment, but one critical question remains: how do you establish trust when agents start acting on behalf of users?
In a recent webinar, Mike Parkhill (Head of Engineering at Dock Labs) and Agne Caunt (Product Owner at Dock Labs) explored this challenge and demonstrated how identity infrastructure can play a central role in solving it.
The session focused on Truvera’s MCP (Model Context Protocol) server, showing how agents can issue, verify, and eventually hold digital ID credentials, and how this enables more secure, auditable, and constrained agent behavior. Along the way, they walked through a live demo of credential issuance and verification, and shared their perspective on where agent identity, delegation, and agentic commerce are heading next.
(01:08) Why agent identity is becoming a problem
(02:20) What MCP (Model Context Protocol) is
(03:19) Goal: identity infrastructure for AI agents
(04:27) What MCP enables for agents (analogy + capabilities)
(05:56) Demo setup (Claude + web wallet)
(14:27) Roadmap: wallet MCP and agent capabilities
(15:16) Agent-to-agent (A2A) and DIDComm direction
(16:13) Introduction to Agentic Payment Protocol (AP2)
(18:02) AP2 mandates (cart, intent, payment) explained
(19:51) Demo: issuing a cart mandate to an agent wallet
(21:31) End of demo and transition to Q&A
(22:21) What is an agent’s identity?
(25:05) How MCP improves security and limits agent scope
(28:07) Schema flexibility and support for new protocols
(30:03) Ease of implementation and setup
(31:43) How agents get their identity (onboarding)
(33:04) Human-to-agent delegation model
(34:19) EUDI and business wallet discussion
(40:38) What happens when an agent invokes MCP tools
(42:52) Multi-tenant vs one-to-one MCP architecture
(45:36) Why did:cheqd was chosen
(47:41) Real-world use cases (e-commerce, travel)
(49:01) Sensitive use cases (loans, insurance, documents)
(50:23) DID methods (did:key vs cheqd) explained
(52:45) Closing remarks and next steps

📚 EXPLORE:
Website - https://www.dock.io/
👨‍👩‍👧‍👧 FOLLOW:
LinkedIn - https://www.linkedin.com/company/docknetwork/

Identity fragmentation isn’t usually the result of bad architecture. It’s the natural byproduct of growth. New apps get added. Business units operate independently. Acquisitions bring in new identity stacks. And over time, even well-designed IAM environments start to sprawl.
In our recent masterclass, Richard Esplin (Head of Product) and Agne Caunt (Product Owner) walked through what this looks like in the real world and, more importantly, how organizations can evolve toward a unified identity architecture without ripping out the systems they already rely on. The session explored the limits of traditional federation, the shift toward reusable digital ID credentials, and a practical, phased path teams can use to reduce duplication, improve flexibility, and move closer to a zero trust model.
(00:00) — Welcome and webinar overview
(00:57) — Why identity architectures keep fragmenting
(01:28) — The real-world IAM problem 
(02:52) — Example: a scaled consumer business with identity silos
(04:27) — Typical federation-based IAM architecture
(06:01) — Why federation breaks down in practice
(08:52) — What IAM architects are reporting in the field
(13:09) — The mindset shift: from system integration to identity ecosystems
(17:07) — The generic reusable credential architecture
(18:22) — Wallet integration overview
(18:44) — Flow 1: Onboarding and credential issuance
(20:53) — Flow 2: User-initiated verification from an app
(22:01) — Flow 3: User-initiated verification from a relying party
(23:05) — Flow 4: Call center / relying-party initiated flow
(24:21) — How to evolve a fragmented architecture (phased approach)
(25:41) — Phase 1: Start with one painful use case
(26:02) — Phase 2: Use the IdP as a credential verifier bridge
(28:00) — Phase 3: Direct verifier integrations
(28:36) — Phase 4: Reducing reliance on the IdP
(30:12) — Practical implementation tips
(34:03) — Trade-offs and considerations
(36:06) — Key advantages of the credential model
(37:46) — Q&A begins

📚 EXPLORE:
Website - https://www.dock.io/

👨‍👩‍👧‍👧 FOLLOW: 
LinkedIn - https://www.linkedin.com/company/docknetwork/

AI agents are rapidly changing the shape of the internet. What started as an effort to keep bots out is quickly becoming a much more complex challenge: distinguishing humans from machines, enabling safe automation, and doing all of it without forcing users to overshare their identity.
Against this backdrop, “proof of human” is moving from a niche concept to a foundational requirement for many digital experiences.
To unpack what’s really happening, and what the identity ecosystem needs to do next, we hosted a conversation with Ajay Patel, Head of World ID at Tools for Humanity, and Kim Hamilton Duffy, CEO of a stealth startup and former Executive Director of the Decentralized Identity Foundation.
The discussion explored the rising pressure created by AI-driven abuse, the risks of over-identification, the role biometrics can play when implemented carefully, and why interoperable, narrowly scoped credentials may be the path forward.
(00:00) — Introduction and session overview
(02:57) — Ajay Patel introduces World ID
(09:51) — Urgency of proof of human in the AI era
(10:50) — Why traditional bot defenses are failing
(12:38) — Risks of over-identification and data oversharing
(14:41) — Are we overreacting to the AI/bot problem?
(17:52) — Gaps in current digital identity infrastructure
(21:53) — Privacy by design vs. surveillance risks
(24:48) — Design principles for future identity systems
(31:21) — World ID Orb and biometric approach explained
(37:34) — Role and concerns around biometrics
(41:00) — Centralization risks and self-custody principles
(44:20) — Hardware trust and decentralization challenges
(48:06) — Interoperability with verifiable credentials and mDLs
(53:02) — Why composability and standards matter
(55:34) — Q&A: biometric changes and credential refresh
📚 EXPLORE:
Website - https://www.dock.io/
👨‍👩‍👧‍👧 FOLLOW:
LinkedIn - https://www.linkedin.com/company/docknetwork/