1. Vendor and Product Reality

Yubico, founded in Sweden in 2007 and dual-headquartered in Stockholm and Santa Clara, is the de facto standard-bearer for hardware-rooted authentication. The YubiKey product family, YubiKey 5 series, YubiKey Bio, Security Key, and the YubiHSM hardware security module, has been deployed at Google, Facebook, the U.S. federal civilian executive branch under OMB M-22-09, large financial institutions, and a long tail of enterprises that adopted phishing-resistant MFA after the wave of credential-stuffing and SIM-swap incidents that exposed SMS and TOTP. Yubico co-authored the U2F specification at the FIDO Alliance with Google, and its engineers remain primary contributors to FIDO2, WebAuthn, and the CTAP transport protocols that browsers and operating systems implement.

The architectural shape of the YubiKey is well-understood and impressively engineered. A secure element holds private keys generated on-device; the device exposes USB-A, USB-C, NFC, and Lightning interfaces and presents itself as a CCID smart card, a HID FIDO authenticator, an OATH-HOTP/TOTP generator, an OpenPGP card, and a PIV credential holder simultaneously. When a relying party initiates WebAuthn authentication, the browser passes a challenge to the authenticator, the secure element signs the challenge with the relying-party-bound private key, and the signed assertion returns through the browser to the server. The private key never leaves silicon. Touch presence and, on YubiKey Bio, fingerprint match provide user verification.

Yubico's strengths are real and consequential. The cryptography is sound, the supply chain is auditable, the form factors are durable enough for daily carry, and the ecosystem of relying-party support is unmatched among hardware-authenticator vendors. CISA, NIST SP 800-63-3 AAL3, the U.S. DoD CAC alternative pilots, and the EU eIDAS high-assurance level all converge on hardware authenticators of YubiKey's class as the reference for phishing-resistant MFA. Within its scope, preventing remote credential theft and replay, the product is excellent and continues to be the right answer for the threat model it was designed against.

2. The Architectural Gap

The structural property the YubiKey architecture does not exhibit is identity independence from stored secrets. The YubiKey is a secure container for a private key, and the private key is the identity. Every property the system delivers, phishing resistance, replay resistance, attestation, flows from the assumption that the bound private key exists in exactly one secure element under exactly one user's physical control. When that assumption holds, the model works. When it does not, the identity is gone with the key. The relevant failure modes are not hypothetical. In 2017, the ROCA disclosure (CVE-2017-15361) found that a flawed Infineon RSA key-generation routine produced keys whose private half could be reconstructed from the public key; Yubico addressed the affected YubiKey 4 revisions through security advisory YSA-2017-01. In 2024, the EUCLEAK research (Thomas Roche, NinjaLab) showed that an electromagnetic side channel in Infineon's ECDSA implementation could extract the private key and clone YubiKey 5 series devices running firmware below 5.7, remediated by moving to Yubico's own cryptographic library in 5.7. Both are real, disclosed, patched issues, and both illustrate the same architectural point rather than any deficiency in Yubico's response: when the private key is the identity, any path that recovers or clones that key material recovers or clones the identity. Physical loss, theft with a coerced touch, and a future cryptanalytic break against ECDSA P-256 are the same structural exposure from different directions.

The gap matters because the recovery story for hardware authenticators is not "recover the identity"; it is "register a different stored key." Operational guidance from Yubico, Microsoft, Google, and CISA all converge on the same recommendation: register at least two YubiKeys, store one in a safe deposit box or equivalent, and treat the relying-party account-recovery flow as a fallback. Each of those mitigations is another stored credential with its own loss, theft, and compromise surface. Account-recovery flows that depend on email, SMS, or help-desk identity proofing reintroduce exactly the phishable channels the YubiKey was deployed to eliminate. The hardware solved the wire problem and left the inventory problem unsolved.

Yubico cannot patch this from within the YubiKey architecture because the product is, by definition, a key store. Adding biometrics on the device (YubiKey Bio) hardens user verification but does not change the identity primitive, the fingerprint gates access to the same stored private key. Adding post-quantum algorithms to future firmware will replace one stored secret with another stored secret of a different mathematical family. Adding an attested provisioning ceremony improves the trust in initial enrollment but does not give the identity a way to survive the loss of the artifact carrying it. The chain of trust terminates at a piece of silicon, and silicon is mortal. A regulator or relying party asking "what is the identity if the device is destroyed, and how does the identity prove its own continuity without an out-of-band reset" gets a registration procedure, not an architectural answer.

3. What the Keyless Identity Primitive Provides

The Keyless Identity primitive, disclosed in United States Patent Application 19/388,580, specifies that identity is constituted by a validated continuity of dynamic hashes rather than by any persisted private key. The specification calls the running identity a Dynamic Agent Hash (DAH) for an agent and a Dynamic Device Hash (DDH) for a device. Each step is a successor of the immediately prior trusted step, computed under an update rule that combines the prior hash with at least one unpredictability contribution and a non-repeating volatile salt. The disclosure describes two interchangeable unpredictability sources and a hybrid of them: a keyed derivation from a static hardware anchor (for example a TPM, TEE, or SoC identifier) combined with a per-epoch volatile salt, or an extractor output over a stability-tuned local state vector composed of device-observable signals such as monotonic counters, high-resolution timing deltas, scheduler jitter, and I/O micro-jitter. The sequence of validated successors is what the specification names the trust slope, and continuity means that a presented successor is a valid descendant of a previously trusted state under policy-bounded checks. A relying party validates the successor relationship locally, without a certificate authority, a global registry, or any stored public key.

The structural properties follow from the specification. There is no long-lived secret in the authentication path to exfiltrate, because each DAH or DDH is ephemeral, computed per step, and never reused as a standing credential; observation of any single value does not enable impersonation, because acceptance requires monotonic progression from a prior trusted state. There is no key to clone in the YubiKey sense, because reproducing a valid successor requires the device's local unpredictability (its hardware-anchor derivation or its stability-tuned local state), which is not exported and is not held as a durable copyable secret. Quorum-based recovery is a first-class operation rather than a manual re-registration: a device that has lost its lineage reseeds a new initial identity and gathers signed attestations from previously trusted peers, which aggregate under a configured quorum policy into a recovery token that re-anchors the slope, with the recovery event recorded into lineage for audit. Because security reduces to the unpredictability of the per-step inputs and to hash and extractor preimage resistance rather than to problems Shor's algorithm attacks, the specification characterizes the model as post-quantum aligned; it notes that against Grover-style search a per-step forgery retains only a quadratic speedup, and that 256-bit to 512-bit digests and extractor outputs provide conservative margins.

Continuity is auditable without an external key registry: each identity transition is folded into an append-only, forward-secure lineage with periodic anchors, so omission, reordering, or modification of any entry is detected by divergence of the cumulative chain value. The primitive is agnostic to unpredictability source, hash family, and quorum protocol, and it composes across administrative boundaries through scope tags and cumulative slope validation as an agent migrates between hosts, giving multi-node provenance without a synchronized ledger. Optional biometric-assisted reseeding can contribute additional local unpredictability during anchor rotation, but only through a privacy-preserving fuzzy extractor with liveness verification, and it augments rather than replaces the hardware-anchor and local-state sources. The inventive step is identity-as-validated-continuity-of-locally-derived-hashes rather than identity-as-stored-key.

4. Composition Pathway

The composition is complementary, not a replacement of Yubico's hardware. The YubiKey integrates as the trusted-environment carrier for keyless-identity continuity rather than as the holder of the identity itself. What stays at Yubico: the secure element, the touch sensor, the biometric matcher, the form factors, the FIDO and WebAuthn transport stack, the attested provisioning ceremony, the manufacturing supply chain, and the entire enterprise commercial relationship. Yubico's investment in tamper-resistant hardware, secure firmware update, and FIPS and Common Criteria certification remains its differentiated layer and gains importance, not less, because the secure element becomes an ideal host for a continuity engine that benefits from hardware-grade unpredictability and tamper resistance.

What changes is the identity primitive that runs inside that hardware. The specification's static hardware anchor embodiment maps directly onto the secure element: the update rule can derive its per-epoch unpredictability from a keyed function of the secure element's device identifier combined with a fresh volatile salt, and richer platforms can additionally fold in a stability-tuned local state vector where device-observable signals are available. At each authentication event the device advances the DAH or DDH under the published update rule, and the relying party validates that the presented successor is an on-slope descendant of its last trusted state rather than verifying an ECDSA signature against a stored public key. A WebAuthn-compatible assertion can carry the successor and the bounded continuity evidence in place of a signature over the challenge, and the specification's legacy-bridge adapter keeps interoperability with signature-based relying parties without hashing any PKI material into the slope. Quorum-based recovery operates over the existing population of enrolled YubiKeys bound to the same identity, which turns the multi-device registration practice into a structural continuity property rather than an operational workaround.

The new commercial surface is identity continuity as a substrate for Yubico customers in regulated sectors, including the federal civilian executive branch, defense, financial services, and healthcare, that face simultaneous post-quantum migration pressure (NIST PQC, CNSA 2.0) and account-recovery audit pressure. The slope belongs to the identity, not to any single secure element, so a customer's identity history is portable across device generations and survives any single device's loss, which paradoxically makes the hardware stickier because secure-element quality is what differentiates its hosting of the substrate.

5. Commercial and Licensing Implication

The fitting arrangement is an embedded substrate license: the keyless-identity primitive is embedded into the YubiKey 5 successor line and YubiHSM, shipping continuity firmware as a mode alongside legacy FIDO2 for backward compatibility through the specification's legacy-bridge adapter. Pricing on the customer side can shift from per-device-sold toward per-identity-under-continuity, which aligns with how regulated customers actually consume identity assurance and which monetizes the recurring quorum and slope-validation services that the substrate enables.

What Yubico gains: a structural answer to the "what happens when the key is lost or broken" problem that current multi-device registration only addresses procedurally; a defensible position against in-platform passkey implementations from Apple, Google, and Microsoft by elevating the architectural floor above stored-key parity; and a forward-compatible posture toward the post-quantum migration that will otherwise force a wholesale change of every deployed YubiKey's asymmetric primitive. What the customer gains: portable identity that survives device loss without out-of-band recovery, post-quantum-aligned assurance whose floor is preimage resistance rather than a specific signature algorithm, and a single continuity slope spanning workforce, contractor, and machine identities under one published continuity rule. The honest framing is that this primitive does not replace the YubiKey. It gives the secure element an identity model that no longer terminates at a single copyable key.

6. Disclosure Scope

This article is a public technical disclosure of the Keyless Identity inventive step as described in United States Patent Application 19/388,580. All statements in this article about what the invention does, including the Dynamic Agent Hash and Dynamic Device Hash update rules, the two interchangeable unpredictability sources (a hardware-anchor derivation with a volatile salt, and an extractor over a stability-tuned local state vector) and their hybrid, the trust-slope continuity and two-stage validation model, append-only lineage with periodic anchors, delayed and sparse verification, predictive drift detection, entropy-anchor rotation, quorum-based recovery, and the post-quantum-aligned security argument, are grounded in that application. A skilled implementer can build the described approach from the update rules, validation procedures, and recovery mechanisms disclosed there, and the embodiments above (hardware-anchored, local-state, and hybrid; connected, intermittent, and stateless deployments; agent and device identities) are enumerated to indicate the intended breadth.

References to Yubico, the YubiKey product family, YubiHSM, FIDO2, WebAuthn, CTAP, the ROCA and EUCLEAK disclosures, and any other named company, product, standard, or vulnerability are external market and technical context. They are provided for accurate comparison and are not claims of United States Patent Application 19/388,580. Each named product is described at the architecture level as it is publicly documented; nothing here asserts a defect in Yubico's engineering or in its response to the referenced disclosures, both of which were patched by Yubico.