On March 26, 2026, the U.S. Patent and Trademark Office published a patent application from Lenovo (Singapore) Pte. Limited titled “Digital Identity Management” (US20260089506A1). A published application is not an issued patent; it is a roughly 18-month-delayed look at where a company chose to direct filing effort. This one is worth reading for what it puts on a distributed ledger and what it pointedly does not. There is no coin here, no token, no settlement rail. What the filing describes is identity machinery — and it runs that machinery on a permissioned distributed ledger.

The abstract lays out the components in standards vocabulary. The system provides permissioned distributed ledger (PDL) services, then layers two registries on top: a decentralized identifier (DID) document registry and a verifiable credential (VC) data registry, each supporting the full lifecycle of its records. The abstract states it directly:

Decentralized identifier (DID) document registry services, for example, are provided to enable management of DIDs, such as for actions including create/store, update, delete/revoke, etc., for DIDs.— Digital identity management, US20260089506A1

The terms are not arbitrary. Decentralized identifiers and verifiable credentials are the building blocks of a specific approach to digital identity — one where a user (or a device) controls an identifier that is not issued by a single central authority, and where claims about that identifier (a credential) can be checked cryptographically by anyone, without phoning the issuer. The “permissioned” qualifier matters too: a permissioned ledger restricts who can run a node and write records, which is the version of distributed-ledger technology that regulated and enterprise actors have consistently filed around. The single classification on the record, the wireless-security class H04W 12/08, situates the filing as access-and-identity infrastructure rather than as a financial-transaction claim.

What the filing points toward

The business reading follows from the architecture and from who Lenovo is. The filing describes the registry plumbing — how DIDs and verifiable credentials are created, stored, updated, and revoked on a controlled ledger — and it reads as network-side infrastructure, the inventor named being a single contributor working in the connectivity-and-identity area. For a device and infrastructure company, identity that a user or device can carry across networks, and that a relying party can verify without a central lookup, is a recurring engineering target: it is the layer that lets a credential issued in one context be trusted in another. The filing documents an intent to build that layer on a permissioned ledger, with the revoke operation called out explicitly — the part any real credential system needs in order to pull back trust after it has been granted.

The directional signal, stated plainly, is this: the document points toward decentralized-identity infrastructure on a controlled distributed ledger, not toward a cryptocurrency or a consumer wallet product. The filing does not say where Lenovo intends to deploy it, whether it is tied to a standards body’s work, or whether it reaches a product at all. It describes a capability — registry services for self-controlled identifiers and verifiable credentials, anchored on a permissioned ledger — and stops there.

The choice of a permissioned ledger over a public one is the detail most worth dwelling on for a business reader. A public chain like the ones underpinning major cryptocurrencies lets anyone run a node and read the data; a permissioned ledger restricts both, which is the configuration enterprises and regulated actors reach for when the records involve identity rather than anonymous value transfer. By building DID and verifiable-credential registries on that controlled foundation, the filing keeps the verifiability properties of a distributed ledger — records that multiple parties can check and that resist silent tampering — while limiting who participates. The revoke and update operations the abstract calls out are the practical hinge: a credential system that cannot withdraw trust once granted is of little use to an issuer, and the filing names those lifecycle actions explicitly rather than leaving them implied. Taken together, the design reads as identity infrastructure intended to be operated by a defined set of participants, not opened to a public network.

A thin week, stated factually

Blockchain publication volume runs lower than in patent-dense sectors, and the U.S. blockchain publication window for March 24 to March 30, 2026 underscored it. The records indexed for the sector keyword set number 117 published applications, but the large majority were unnamed assignees or carried only incidental distributed-ledger mentions inside unrelated filings — hearing aids, vehicle systems, retail surveillance. Among recognizable names, the genuinely ledger-centric identity filings were sparse. This Lenovo application is the clearest of them; the surrounding week’s closest neighbors are infrastructure filings such as a Huawei trust-assessment system that lists a blockchain registry among its evidence stores (US20260089146A1) and a confidential-computing mediation system that uses a permissioned blockchain as policy storage (US20260089141A1). Because the week is thin and Lenovo’s own indexed distributed-ledger publication footprint is a single filing, the directional read here rests on the substance of this one application rather than on a dense Lenovo cluster.

The standard caveats apply with force. This is a published application, not a grant; its claims may narrow or fail before issuance, and a filing discloses an intent to seek coverage, not a deployed system or a market position. No claim about a sustained Lenovo identity-ledger program can be grounded in a single record. What the document does establish is the disclosed direction: a major device maker is documenting decentralized-identifier and verifiable-credential registry services built on a permissioned distributed ledger — identity infrastructure on a controlled chain. For a business reader, that is the practical translation of the filing, and it is the part the record actually supports.