Nvidia · Filed May 8, 2025 · Published Nov 12, 2026

A New Nvidia Patent Lets Chip Buyers Claim Control of What Software Runs

Chips only have so many burn-once switches, so Nvidia's patent application turns a simple count of how many have been flipped into a record of who owns the chip.

A computer locks a chip to a new owner so it only boots software approved by that owner. Drawing from patent filing US 2026/0359441 A1.
A computer locks a chip to a new owner so it only boots software approved by that owner.
See all 12 drawings from this filing ↓
Publication number US 2026/0359441 A1 US20260359441A1
Applicant NVIDIA Corporation
Filing date May 8, 2025
Publication date Nov 12, 2026
Inventors James Zhang, Varun Sampath, Christopher Hillier, Alexey Vorobey
US classification 713/2
Examiner ALSIP, MICHAEL (Art Unit 2139)
Status when we published Examiner raised objections; the company can respond (Aug 13, 2026)
Document 20 claims

What Nvidia's chip-ownership handoff actually does

Imagine your company buys a rack of Nvidia chips and wants only its own software to run on them. One way to do that is to burn your approval key permanently into each chip, but the space for burned-in data is limited and can never be erased, so every handoff to a new owner uses some of it up.

Nvidia's filing describes a workaround. Your key goes into a small sealed package kept in ordinary outside memory, stamped with a code that only that exact chip can recreate, so nobody can slip in a fake. A tally of tiny one-time switches on the chip, odd for owned and even for free, records whether someone has claimed it.

At startup, the chip checks the seal, pulls out your key, and runs only software that carries your signature.

From the filing · THE ABSTRACT
… a data object (e.g., a binary large object (blob)) may be bound cryptographically to a device (e.g., a silicon chip, a processor, a system, etc.), and data (e.g., keys) stored by the data object may be used to authenticate a command, firmware, and/or software.

Translation: A digital data package locks securely to a specific piece of hardware so its stored keys can verify commands and software.

How the blown-fuse counter and sealed blob work

The claims cover a chip (or a system, or a method) that, during startup, uses a value permanently written into the chip to check a key stored outside the chip. It then uses that key to check firmware (the low-level software that runs a chip's basics) or other software before startup finishes.

The permanent value is a count of blown fuses: tiny one-time switches that can be flipped once and never undone. In the filing's example, an odd count means the chip is owned (locked) and an even count means it is free. Claiming ownership blows one fuse and releasing it blows another, so the count only moves forward.

The key sits in a data object, or blob (just a chunk of data), in outside memory. To seal it to one chip, the chip builds a Message Authentication Code (MAC, a short tamper-evident stamp) from the blob, the fuse count and a chip-unique identifier. At boot:

  • The chip recomputes the stamp and compares it with the stored one.
  • If they match, it pulls out the owner's keys.
  • It uses them to check the signatures on firmware or commands.

Because the fuse count feeds the stamp, releasing ownership makes older blobs fail the check. The filing also describes a lock key for approving ownership changes and a vendor-signed recovery command for a lost blob.

What this means for Nvidia's data center chips

If you run servers, this is about who gets the final say over what starts up on hardware you bought. A chip that can pass cleanly to a new owner, without using up its limited one-time storage, makes reselling or reassigning expensive processors less risky. Claim 12 names data centers directly, and the description also lists autonomous machines, medical devices and financial systems as possible homes.

For everyday readers the effect would be indirect: it is plumbing that helps keep tampered code off the machines behind the services you use. It is also an application, not a granted patent. The examiner's first review rejected the claims as filed, which is routine at this stage and usually followed by amendments.

Nvidia's 66th filing we've tracked in our AI chip wars watchlist since July builds on earlier applications like the chip traffic jam fix and the faster chatbot chip.

Editorial take

Moving the owner's key out of the chip and into ordinary memory saves scarce one-time switches, and it puts the chip's safety on a tamper seal that has to hold up. The seal looks sound, since only that exact chip at that exact switch count can recreate it.

The cost shows up when something goes wrong. Lose or corrupt the key package and the chip cannot boot your software until the manufacturer sends a signed recovery command, so ownership always has the maker standing behind it.

The switch count is the other limit. Each claim and release burns one, so a chip can change hands only a limited number of times, a fair price for hardware that gets resold.

Get our take in your Top Stories

Liked this breakdown? Add Patentlyze as a preferred source on Google, and our plain-English take shows up more often in your Top Stories the next time Nvidia patent news breaks.

There are more where this came from

We read every patent application Big Tech publishes and send you the ones worth knowing. Plain English, free, every week.

The drawings

12 drawing sheets from US 2026/0359441 A1 · click any drawing to enlarge

Connecting a main processor to lock down a chip, drawing sheet 1 from US 2026/0359441 A1
Sheet 1 Connecting a main processor to lock down a chip
Creating the secret keys used to protect chip data, drawing sheet 2 from US 2026/0359441 A1
Sheet 2 Creating the secret keys used to protect chip data
Switching a chip between locked and unlocked security states, drawing sheet 3 from US 2026/0359441 A1
Sheet 3 Switching a chip between locked and unlocked security states
Claiming permanent control of a newly installed chip, drawing sheet 4 from US 2026/0359441 A1
Sheet 4 Claiming permanent control of a newly installed chip
Verifying approved software every time the chip starts up, drawing sheet 5 from US 2026/0359441 A1
Sheet 5 Verifying approved software every time the chip starts up
Releasing chip control to restore original factory software, drawing sheet 6 from US 2026/0359441 A1
Sheet 6 Releasing chip control to restore original factory software
Inputs and outputs for requesting a chip state change, drawing sheet 7 from US 2026/0359441 A1
Sheet 7 Inputs and outputs for requesting a chip state change
Software tools that create security keys from chip hardware, drawing sheet 8 from US 2026/0359441 A1
Sheet 8 Software tools that create security keys from chip hardware
Show the other 4 sheets
Hardware circuits verifying signatures and generating security keys, drawing sheet 9 from US 2026/0359441 A1
Sheet 9 Hardware circuits verifying signatures and generating security keys
Specialized circuits used to train and run AI models, drawing sheet 10 from US 2026/0359441 A1
Sheet 10 Specialized circuits used to train and run AI models
Cloud data center layout managing computing resources and apps, drawing sheet 11 from US 2026/0359441 A1
Sheet 11 Cloud data center layout managing computing resources and apps
Main computer parts coordinating memory, graphics, and processing, drawing sheet 12 from US 2026/0359441 A1
Sheet 12 Main computer parts coordinating memory, graphics, and processing
Browse all the drawings 12 drawing sheets
Patent filing page

Source. Full patent text and figures from the official USPTO publication PDF.
Reader comments

Be the first to weigh in

Start the discussion

Real name or a handle, either is fine. Comments are read by a person before they appear, so allow a little time. Keep it about the filing.