In the week of issued U.S. patents dated April 14, 2026, the blockchain grant column was thin — 70 blockchain-tagged grants, the volume leader being Toyota with four, and a large share carrying no named assignee. Among the recognizable names was Microsoft Technology Licensing, LLC, with a grant that does not concern tokens or cryptocurrency at all, but rather the data-integrity machinery that sits underneath distributed-ledger systems. A granted patent is enforceable coverage of the claimed method, distinct from a published application; Microsoft's entry shows what it just locked in at the ledger-database layer.

The grant is US12602497B2, “Verifiable attribute maps,” naming inventors Ramarathnam Venkatesan, Srinath T. V. Setty, Nishanth Chandran, and Panagiotis Antonopoulos, and classified in G06F 21/62 and the blockchain-specific class H04L 9/50. It covers a map of identities and their attributes maintained by a ledger database whose tables are tamper-evident, where a client validates the database state against a cryptographic digest before being granted access. The abstract describes the verification loop:

When the database receives a request from a device to access the map, the digest is received along therewith. The database is validated based on the digest to determine whether the database has been tampered with since the provision of the digest.— Verifiable attribute maps, US12602497B2

For a general reader: this is a way to store identity-and-attribute data such that any reader can mathematically check the store has not been altered since a known checkpoint, with the tamper-evidence built into the database tables themselves. It is the same trust property that public blockchains provide — an immutable, independently verifiable record — applied to an enterprise ledger database rather than a token network.

A multi-year verifiable-ledger cluster

The grant is not isolated. A search of issued Microsoft grants referencing verifiable ledgers and blockchain returns a tight cluster of at least eight records, several sharing the same inventors and concept. US12265522B2 (“Confidential blockchain database with a distributed ledger,” issued April 2025) covers a consortium blockchain run inside a trusted execution environment that issues a universally verifiable receipt with a Merkle-tree proof for each transaction. US11601439B2 and US10587628B2 (both “Verifiable outsourced ledgers”) describe a digital ledger on a blockchain that distrustful parties can replicate locally to verify the ledger's integrity.

Two more fill out the consensus and lightweight-deployment angles. US11615410B2 and US11403631B2 (“Heartbeats and consensus in verifiable outsourced ledgers”) add a heartbeat-based consensus that lets clients confirm ledger state and recover it after a fault, and US11405181B2 (“Lightweight blockchain based on split-trust”) covers a blockchain split between low-resource and untrusted high-resource devices. The cluster spans issue dates from 2019 through 2026 and is consistently authored by a small set of researchers including Setty, Venkatesan, and Chandran.

How the claim actually works

The independent system claim turns the abstract's verification loop into a sequence of concrete operations, and the detail is where the grant's scope lives. Claim 1 describes receiving a request from a first computing device, on behalf of a first entity, to update the attribute map maintained by a first ledger database. That request carries three things: an identifier of the entity, a digest representing the current state of the ledger database, and an attribute of a user that has been "signed with a first signature of a first private key associated with the first entity." The map itself holds "a reference to an identity of the user" rather than the raw identity data — a layer of indirection that keeps the map compact.

Before any write happens, the system performs two checks that operate against two separate ledgers. It obtains the entity's public key from "a first identity map maintained by a second ledger database" — a directory that pairs identifiers with public keys — and verifies the supplied signature against it. Only then does it validate the ledger database against the supplied digest. The grant makes both steps gating conditions: the attribute is associated with the user's identity reference "in response to said verifying and said validating," and the database then "generat[es] a second digest representative of the state of the ledger database" after the write. That second digest is what the next reader will check against, so each update advances the checkpoint. The structure is a two-ledger design — one mapping identities to keys, one holding the attributes — with a fresh digest minted on every change, which is the mechanism that makes the store independently auditable rather than merely access-controlled.

The classification reflects that split focus. The grant carries G06F 21/62, the class for restricting access to data, alongside H04L 9/50, the blockchain-specific cryptography subclass — a pairing that places the record at the intersection of access control and ledger integrity rather than in either alone. Across the patent's twenty claims, the same elements recur as the building blocks: the signed attribute, the public-key lookup on a second ledger, the digest-based validation, and the regeneration of a digest after each update.

What the coverage maps to

Mapped together, the records describe a single line of work: making a ledger or database verifiable and tamper-evident without requiring a public token network — verifiable attribute maps (US12602497B2), confidential blockchain databases (US12265522B2), outsourced ledgers parties can independently audit (US11601439B2), and the consensus to keep them honest (US11615410B2). For a business reader, that maps to infrastructure aimed at enterprises and cloud customers that want blockchain-style auditability over their own data, a different position than the consumer-token or payments footprints visible elsewhere in the same weekly column.

The caveats are the usual ones. The week's blockchain field is thin and skewed to unassigned records, so a single week is a narrow window. And a grant establishes that a claim issued, not how broadly it reads or whether the technology ships in a named product. What the records do show is the direction of Microsoft's coverage — verifiable, tamper-evident ledger databases and the consensus around them — with the April grant extending a cluster that the same inventors have been building for years.