Okay, so we're going to talk a little bit about continuous trust minimal data. So Ditto, like many, is on a journey with our customers and partners to transition the identity shift. Our foundation is cryptographic authentication and our legacy will be in rebuilding digital trust and privacy. As an industry it's easy to confuse access with trust. It's something that we've been doing for a long time. It's a very important part of what trust is, but it is a gateway, a pass-through.
One-time passwords, single sign-on, KYC results, a federated assertion, they're all points of access within a trust journey. The cost of this confusion is visible. Account takeover after clean MFA, successful fraud after valid KYC, and data exfiltration through authenticated channels and sessions is real. Trust is a property of the relationship between a user agent, a device, the application, and a transaction held continuously, not stamped once. To understand what trust is, we need to go and think about what it is in the premise of the real world.
For us, we like to think that if an identity stack cannot continuously verify and authenticate the user agent, device, application, and the transaction, while preserving privacy, minimizing data, and ultimately preparing to solve the quantum transition, then we're not solving the next problem. We're protecting the last one, the one that is present today. So if we consider what real-world trust and digital trust are, they're foundationally the same property. Trust in the real world accumulates over years of shared moments.
It's continuous, it's contextual, and it's linked to recognizing a person over time. The digital world has tried to replicate this, and in many cases has been successful, but not entirely. We often use point-in-time proofing, KYC, point-in-time factors, MFA, and point-in-time recovery, KBA, as proof points for this trust. The challenge is how do you create the linkage between today's customer and tomorrow? This is not trust if it breaks in the moment.
What we're working towards is a redesigned model that deliberately engineers real-world trust into digital substrate, where wallet credentials persist linkage, zero-trust architecture presents and enforces proof, signal intelligence carries real-time context, and post-quantum cryptography ensures that those properties are durable. If we consider then a journey as it is today, there are many failing doctrines, and there are siloed moments that occur. In the principle of the static identity journey, the customer arrives for the first time, they're asked to prove who they are.
Much of this is done through document scanning, selfie, biometrics, AML, watchlist checks, even a credit pull. This is the harvesting of data at a point of need and necessity, but most of that data is retained beyond its purpose, and often by third-party vendors. The trust failure is this is a one snapshot of proofing. After the moment, the customer record is treated as a self-evident truth, and synthetic identities powered by AI and mule accounts are passing at scale. Deploying MFA is a good strategy. It is a good principle. It's there for the routine use when the customer comes back.
They log in, they share a password, MFA, passkey, or whatever the factor might be that's requested, and they start using the service. Much of that data is shared with downstream fraud systems and fraud engines, necessarily or unnecessarily. The trust failure is this only proves possession at one moment. The session that follows is treated as fact. An account takeover is landing inside securely authenticated sessions every day, and often the security stack rarely knows it happened. Workflow is not verification.
In a high-stakes event occurring all the time, payments, transfers, sensitive data changes, loan applications, prescription requests, tax filings, property transactions, all of these details and signals are collected and passed across partner networks. Each one has a chance to store that information. The trust failure in this moment is that the workflow is not the verification. The action is a risk-scored orchestration layer making probabilistic guesses which are never cryptographically proven. Friction or fraud is the question, and many false declines climb in parallel with fraud losses.
What's absent as we move through that towards re-verification and recovery is the signal-blind event. Something goes wrong.
A dispute, a fraud claim, a device is lost, a password is forgotten or reset, a chargeback is raised. The customer service path is in almost every industry the largest fraud surface on net. The trust failure again injects KBA, MFA. They simply prove possession of secondary channels, email, phone. They're not a proof of identity. Without a real-time signal layer, every verification is again a simple snapshot of what came before. The moment a device is compromised, a credential is revoked, a session is hijacked. Relying systems learn about it too late or not at all.
And across every step, two cross-cutting failures compound data. The data is overshared, it's retained, and it's harvested across actors, and this creates privacy without minimization. And trust at every handoff between systems creates fragmentation, not progress. We like to reconsider this as a continuous trust framework. In this model, we're using multiple axes, adaptive orchestration, all connected by moments through shared signal intelligence that deploy zero trust at the request level with PQC underneath to ensure that the artifacts are durable against future attack.
So in this model, if we replay the last scenario, the first encounter with the customer is no longer a one-shot moment of high-friction proofing followed by nothing. It becomes a credential issuance where we accept an existing wallet credential, could be a UD, it could be a sector-specific verifiable credential, it could be an operator-issued credential, or it could even be a credential that we issue on behalf of our customers. That customer credential is then hybrid signed and wallet portable across products, services, and industry.
The same identity is now recognized whether the user shows up at the bank, a retailer, a healthcare provider, or a government service. In the routine use application, this becomes a continuous property. Every request carries a fresh wallet verifiable presentation protected by mobile threat detection and RASP device and runtime posture sharing signals that propagate every state in real time between identity providers and relying parties. This ensures that not only do what we see is protection but we share that with other parties who need to ensure they are also protecting the same entity.
Zero trust is enforced per request rather than per session and the high stakes moments become cryptographically bound intent where the amount, the destination, and the action are re-signed by the user's wallet and authorization signatures have become PQC durable so the chain of evidence holds across the multi-year audit and dispute window. In a recovery event, the continuation sorry the security becomes cryptographically continuous rather than a rupture. A dispute or a recovery replays the signed verifiable proof. The signal trail confirms legitimacy.
The mobile threat detection confirms the device is the same we have seen and PQC keeps everything verifiable for as long as it needs to be. The customer service desk stops being the fraud service because there is nothing for the desk to guess that. These are the tests we are carrying into every architecture conversation with our customers built on continuous trust engineered in the digital world. Privacy preserved through data minimization and unlinkable presentations and bounded telemetry.
Wallet-based identity integrated rather than bolted on and cryptographically that survives the quantum transition. A stack that does all of this we believe is contributing to solving the next problem. If we've reflected a little bit on what that next problem is the reason we're we believe that a continuous proof-based trust transitions into the post-quantum survivability is based on these assessments of recent analyst results. If we consider the first one harvest now decrypt later. Captured authentication traffic becomes credential theft the moment a quantum computer ships.
The mitigation in this design per request verifiable presentations over PQC hybrid wallet credentials ensuring a captured session carries ensuring a captured session carries nothing replay valuable because every request is a fresh proof signed under a hybrid signature. If we consider the PKI mitigation and migration loop certificate chains were never built for a primitive swap at this scale. The mitigation by moving user authenticity and identity off the PKI trust spine and onto wallet verifiable credentials it shrinks back to DLS and code sharing and signing.
Domains where mitigation and tractability rather than impossibility. Long-lived authentication tokens machine IDs issued today become quantum debt. Hybrid signatures from issuance plus the continuous trust framework eliminate the need for long-lived bearer tokens and every request is freshly authenticated. Non-human identity at scale IP API keys services and agent identities outnumber humans 40 to one at present and this is accelerating. The proposed architecture treats humans and non-human identity uniformly. Wallet credentials and continuous verification extend to APIs services and agents.
The same framework is shared and in crypto agility hybrid by default at the wallet layer the wallet abstracts the user primitives and and this becomes an algorithmic change at the issuer and that becomes a configuration update and not a multi-year program of change. So as a summary sorry we believe in order to solve the next problem and not the last one we need to retire seven identity playbook principles and we need to rebuild seven in their place. This is the architecture that Ditto is building around.
Continuous trust, minimal data, wallet-bound, signal-driven, post-quantum ready and we're excited to be working with our customers and partners and hopefully many of you to make that transition. Thank you very much. Thank you Matthew. We have around five minutes for questions. I open the floor to the audience. Don't be shy. No questions? Yeah give me a second. Thank you. Thank you Matt for the presentation. I would like to ask you about the EUDI wallet space and signal. So how do you see that one going? Just some thoughts on that. Thank you.
So through CAEP frameworks and others are the important landscape for us to follow. And because these are being defined, it's hard for us to commit to what's the right journey, except to follow them as many as we can.
