Chip location verification

Proposed

Location verification aims to show that an AI chip is where its owner says, or at least not in a restricted region.

Trusted "landmark" servers at known places exchange cryptographic challenges with the chip, which signs its replies with a key unique to it. Signals cannot travel faster than light, so a fast reply caps the chip's distance from each landmark. A slow reply does not show that a chip is far away, because internet routes add delay.

A 2025 issue brief estimates under $1 million for firmware and software, plus $2.5–12.5 million a year for 100–500 landmarks. Ulyssean describes an H100 prototype on its demonstration website. NVIDIA is reportedly developing a version that uses its own servers.

The main weaknesses are extraction of a chip's key, manipulated network delay and compromised landmarks. The check says nothing about chips in transit or how they are used.

Development assessmentMedium confidence

The design is public and detailed, but the one reported prototype has a single published result, which cannot be checked.

Assessed use: bounding how far a chip is from trusted landmark servers when checked

Rubric assessment and gaps →

On this page

How it works

Chip location verification tries to establish where an AI chip physically is 1. Brass and Aarne judge delay-based methods, also called ping-based or latency-based verification, the most promising approach 1. A trusted "landmark" server at a known location sends the chip a cryptographic challenge, and the chip replies using a secret key unique to it 1. Signals cannot travel faster than light, so the reply time gives an upper bound on the chip's distance from the landmark 1 7. Measurements from several landmarks narrow the region where the chip can be 10.

Brass and Aarne separate a general problem, locating a chip anywhere, from a narrower anti-smuggling problem: checking only that a chip is not in a restricted location 1. They recommend solving the narrower problem first 1. Aarne, Fist and Withers illustrate it with a trusted server in Paris 7. A reply in under 9 ms would show that a chip lies inside a circle that excludes countries to which exports are restricted 7.

Estimates of the landmark network differ:

  • Brass and Aarne's 2024 report suggests several dozen landmarks at most 1.
  • An IAPS issue brief from 2025, summarising that report, assumes 100 to 500, depending on which countries are included 2.
  • Aarne, Fist and Withers expect hundreds worldwide 7.

For export control, Avellar and Grunewald place landmark servers in or near major data-centre hubs 4. The regulator would periodically ask exporters or end users to have chips ping the nearest landmark 4.

The chip's key must stay secret 1. Brass and Aarne write that per-chip keys would need secure storage, such as a TPM, and that the trusted execution environment on NVIDIA H100 GPUs "could likely be used to implement location attestation" 1. A draft industry specification, Lucid sovereignty (location) certificates, packages the approach as a remote-attestation protocol that issues short-lived location certificates 10. In it, an attester inside a trusted execution environment probes anchor servers and the verifier computes the feasible region 10. Related timing-based checks appear in Timed challenge-response and memory-occupation challenges.

What it establishes

What a timed reply can show:

  • A reply with one-way delay T ms shows that a device holding the chip's key was at most T × 200 km from the landmark at that moment, if signals travel no faster than light in fibre 1.
  • For the anti-smuggling problem, a fast enough reply to a landmark outside restricted regions shows that the chip is not in those regions 1 7.
  • Detours and tunnels add latency, so they generally cannot make a device appear closer to a landmark than it is 10. A path faster than the signal speed the verifier assumes can 1.

What it cannot show:

  • Distance from a slow reply. Internet traffic does not travel in straight lines, so an honest chip near a landmark may reply too slowly to be cleared 1. Under a hard time limit, a slow reply only means the chip cannot be ruled out of a restricted location 1.
  • A precise position. Delay-based methods give positions to within about 10 km to 1,000 km, depending on the algorithm 1.
  • The chip itself. The check binds the reply to whatever holds the key; an extracted key lets another device answer 9.
  • Location between checks. It shows nothing about where chips were between checks, and gives little visibility during shipping and warehousing 4.
  • Who uses the chips, or for what. Avellar and Grunewald treat end-location, end-user and end-use verification as separate problems 4.

Brass and Aarne suggest combining location checks with a centralized chip registry (Chip registries and manufacturing records) 1.

Threat model

Brass and Aarne define three adversary classes 1:

  • Minimally adversarial actors spend little and are very averse to discovery.
  • Covertly adversarial actors spend substantial resources but still want to avoid being caught.
  • Openly adversarial actors spend heavily and do not mind being discovered.

They argue that even an imperfect scheme has value, because it can occasionally catch cheaters and deter minimally adversarial actors 1.

The scheme assumes the following:

  • Chip keys stay secret. Each chip's key is provisioned and stored so that the owner cannot extract it 1. Tee and Happel question this against adversaries with physical access 9.
  • Signals are no faster than assumed. The bound holds only if no path beats the signal speed the verifier uses: the speed of light in fibre, or in a vacuum for a limit that cannot be beaten 1.
  • Landmarks are trustworthy. Landmarks are honest and correctly located 1. The draft Sovereignty Certificates specification requires a signed directory of anchors and keys protected in hardware security modules 10.
  • The chip hardware is trusted. The draft specification lets the attacker control the network and the host's root account, but trusts the hardware root of trust and TEE, and leaves sophisticated physical attacks as a residual risk 10.

Implementations

Search

Full search page