# US 2019/0245680 A1 · Blockchain based secure naming and update verification

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0245680 A1
- Document ID: US20190245680A1
- Status: Published application
- Kind: A1
- Application number: 16/270,534
- Filed: 2019-02-07
- Published: 2019-08-08
- Earliest claimed: 2018-02-07
- Inventors: Raouf Boutaba; Woojung Kim; Yuhao Dong
- Web page: https://patentgrep.com/patent/US20190245680A1

## CPC

- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- H04L 9/006: {involving public key infrastructure [PKI] trust models (network architecture or network communication protocol for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/3263: {involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A secure update is provided from a server to an end-point device. The server registers digital information, such as a name or a software package, and a verifiable key, such as a cryptographic hash, derived from the digital information. A publicly accessible transaction log stores the verifiable key in a block and provides an identifier of the block to the server. An end-point device receives the digital information and the identifier, and computes a separate verifiable key. The end-point device retrieves the verifiable key from the block of the publicly accessible transaction log, and compares the retrieved verifiable key to the separate verifiable key to determine whether the digital information has been compromised.

## Claims

### Claim 1

A method of providing a secure update from a server to an end-point device comprising:
registering, by a server, digital information and a verifiable key derived from the digital information;
transmitting, by the server, the verifiable key derived from the digital information to a publicly accessible transaction log, wherein the publicly accessible transaction log separately stores the verifiable key derived from the digital information in a block of the publicly accessible transaction log, wherein the block has an identifier;
adding, by the server, the identifier of the block to the registration of the digital information and the verifiable key derived from the digital information; and
providing, by the server, the digital information and the identifier of the block to an end-point device, wherein the end-point device uses the identifier of the block to retrieve the separately stored verifiable key derived from the digital information from the publicly accessible transaction log, and wherein the end-point device independently computes a separate verifiable key from the provided digital information, and wherein the end-point device determines whether the provided digital information has been compromised, by comparing the verifiable key derived from the digital information retrieved from the publicly accessible transaction log to the independently computed separate verifiable key from the retrieved digital information.

### Claim 2 (depends on 1)

The method of claim 1, wherein the end-point device is an internet of things (“IoT”) device.

### Claim 3 (depends on 2)

The method of claim 2, wherein the IoT device is one from a group consisting of: a smart thermostat, a smart vehicle, a smart speaker, a smart appliance, a smart security system, a wearable device, a smart camera, a smart entertainment system, a smart lock, and a smart lighting device.

### Claim 4 (depends on 1)

The method of claim 1, wherein the publicly accessible transaction log is a blockchain.

### Claim 5 (depends on 4)

The method of claim 4, wherein the blockchain is Bitcoin.

### Claim 6 (depends on 4)

The method of claim 4, wherein the blockchain is Ethereum.

### Claim 7 (depends on 1)

The method of claim 1, wherein the identifier of the block is a height of the block in the publicly accessible transaction log, the height of the block being relative to a reference block in the publicly accessible transaction log.

### Claim 8 (depends on 1)

The method of claim 1, wherein:
the digital information further comprises a software update.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
receiving the digital information from a remote computing device and wherein the digital information comprises a registered public key.

### Claim 10 (depends on 1)

The method of claim 1, wherein the verifiable key derived from the digital information comprises a hash of the digital information, wherein the hash of the digital information is received by the server from a remote computing device.

### Claim 11 (depends on 1)

The method of claim 1, wherein the verifiable key derived from the digital information comprises a cryptographic hash of the digital information, wherein the hash of the digital information is computed by the server.

### Claim 12 (depends on 1)

The method of claim 1, wherein the end-point device determines that the provided digital information has been compromised, responsive to the verifiable key derived from the digital information retrieved from the publicly accessible transaction log not matching the independently computed separate verifiable key from the retrieved digital information, and wherein the end-point device takes a security action in response to the determination that the digital information has been compromised.

### Claim 13 (depends on 1)

The method of claim 1, wherein the end-point device determines that the provided digital information has not been compromised, responsive to the verifiable key derived from the digital information retrieved from the publicly accessible transaction log matching the independently computed separate verifiable key from the retrieved digital information, and wherein the end-point device utilizes the digital information in response to the determination that the digital information has not been compromised.

### Claim 14 (depends on 13)

The method of claim 13, wherein the provided digital information comprises a software update for the end-point device and wherein utilizing the digital information comprises installing the software update on the end-point device.

### Claim 15 (depends on 1)

The method of claim 1, further comprising:
receiving a signature associated with the digital information, the signature being verifiable with a registered public key associated with the digital information;
determining from the digital information, a permissions threshold associated with the digital information, the permissions threshold representing a quantity of signatures; and
determining that the received signature satisfies the permissions threshold.

### Claim 16 (depends on 1)

The method of claim 1, wherein registering, by the server, the digital information and the verifiable key derived from the digital information further comprises:
inserting a first specific node in an index tree containing the digital information and the verifiable key derived from the digital information.

### Claim 17 (depends on 16)

The method of claim 16, further comprising:
registering, by the server, subsequent digital information corresponding to the digital information contained in the first specific node by inserting a second specific node in the index tree containing the subsequent digital information and a subsequent verifiable key derived from the subsequent digital information; and
referencing the second specific node by an update reference of the first specific node in an update chain.

### Claim 18 (depends on 16)

The method of claim 16, further comprising:
registering, by the server, subsequent digital information unrelated to the digital information contained in the first specific node by inserting a second specific node in the index tree containing the subsequent digital information and a subsequent verifiable key derived from the subsequent digital information; and
referencing the second specific node by a child reference of the first specific node in the index tree.

### Claim 19 (depends on 16)

The method of claim 16, wherein the index tree is a binary search tree.

### Claim 20

A method of providing a secure update to an end-point device comprising:
receiving, by the end-point device, digital information, a registered public key, an identifier of a block in a publicly accessible transaction log, and a transaction identifier associated with the block in the publicly accessible transaction log;
computing a verifiable key from the received digital information and the registered public key;
using the identifier of the block and the transaction identifier in the publicly accessible transaction log to retrieve a separate verifiable key from the block of the publicly accessible transaction log;
comparing the computed verifiable key to the retrieved separate verifiable key; and
determining whether the received digital information has been comprised based on the comparison.

### Claim 21 (depends on 20)

The method of claim 20, wherein the end-point device is an internet of things (“IoT”) device.

### Claim 22 (depends on 20)

The method of claim 20, wherein the publicly accessible transaction log is a blockchain.

### Claim 23 (depends on 22)

The method of claim 22, wherein the blockchain is one of Bitcoin and Ethereum.

### Claim 24 (depends on 20)

The method of claim 20, wherein the identifier of the block is a height of the block in the publicly accessible transaction log, the height of the block being relative to a reference block in the publicly accessible transaction log.

### Claim 25 (depends on 20)

The method of claim 20, wherein:
the digital information further comprises a software update.

### Claim 26 (depends on 20)

The method of claim 20, wherein the verifiable key derived from the digital information comprises a hash of the digital information.

### Claim 27 (depends on 20)

The method of claim 20, further comprising:
determining, by the end-point device, that the provided digital information has been compromised, responsive to the computed verifiable key not matching the retrieved separate verifiable key; and
taking a security action, by the end-point device, in response to the determination that the digital information has been compromised.

### Claim 28 (depends on 20)

The method of claim 20, further comprising:
determining, by the end-point device, that the provided digital information has not been compromised, responsive to the computed verifiable key matching the retrieved separate verifiable key; and
utilizing the digital information, by the end-point device, in response to the determination that the digital information has not been compromised.

### Claim 29

A method of providing a secure update from a server to an end-point device comprising:
receiving, by a server, a software package from a remote computing device;
encoding the software package as a transaction in a first node of an index tree, the first node of the index tree spending an unspent transaction output from a previous node of the index tree;
broadcasting the transaction to a publicly accessible blockchain, wherein the publicly accessible blockchain separately stores the transaction in a block identified by a height in the publicly accessible block chain;
receiving at the server, the height identifying the block in the publicly accessible blockchain;
updating the transaction stored in the first node of the index tree to include the height identifying the block in the publicly accessible blockchain; and
providing the transaction to an end-point device, wherein the end-point device uses the height identifying the block in the publicly accessible blockchain to retrieve the separately stored transaction, and wherein the end-point device derives a hash of the software package included within the provided transaction, and wherein the Fend-point device determines whether the software package has been compromised by comparing the hash derived from the software package to a separate hash included as part of the separately stored transaction retrieved from the publicly accessible blockchain.

### Claim 30 (depends on 29)

The method of claim 29, wherein the end-point device determines that the software package has not been compromised, responsive to the hash derived from the software package matching the separate hash included as part of the separately stored transaction retrieved from the publicly accessible blockchain, and wherein the end-point device installs the software package in response to the determination that the software package has not been compromised.

### Claim 31

A method of providing a secure naming system, the method comprising:
receiving, by a namespace administrator, a name registration;
registering a name-binding associated with the name registration in a node of an index tree, the name-binding comprising an index and a hash of the name registration and wherein the node spends an unspent transaction from a previous node in the index tree, wherein the unspent transaction is from a publicly accessible transaction log;
computing a verifiable random function of the name registration, the verifiable random function using a private key to compute and wherein the verifiable random function can be publicly verified;
determining a proof of existence of the name-binding in the node of the index tree, the proof of existence represented as a path of transaction from a root node to the node of the index tree;
receiving a query of the name registration from an end-point device; and
providing the verifiable random function, the proof of existence, and the name-binding to the end-point device and wherein the end-point device derives the index of the node of the index tree using the verifiable random function, verify the proof of existence, and determine whether the name-binding hashes to a value matching in the proof of existence.
