# US 2020/0201681 A1 · Method and system for virtualizing blockchains

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

- Number: US 2020/0201681 A1
- Document ID: US20200201681A1
- Status: Published application
- Kind: A1
- Application number: 16/732,073
- Filed: 2019-12-31
- Published: 2020-06-25
- Earliest claimed: 2017-10-16
- Assignees: Interbit Ltd.
- Applicants: Interbit Ltd.
- Inventors: Thomas Thompson; Dallas Hoffman
- Web page: https://patentgrep.com/patent/US20200201681A1

## CPC

- G06F 9/5027: {the resource being a machine, e.g. CPUs, Servers, Terminals}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3247: {involving digital signatures}
- G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing}
- G06F 2009/45579: {I/O management, e.g. providing access to device drivers or storage}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods, systems, and techniques for virtualizing blockchains. A hypervisor is run on a computer node. The hypervisor includes a host controller. At least one guest blockchain is also run on the hypervisor, and the host controller allocates at least some hardware resources of the node in response to requests from the at least one guest blockchain. The host controller may include a host blockchain, and some or all of the at least one guest blockchain may be stored within the host blockchain.

## Claims

### Claim 1

A method for virtualizing blockchains, the method comprising:
(a) running a hypervisor on a computer node, wherein the hypervisor comprises a host controller; and
(b) running at least one guest blockchain on the hypervisor, wherein the host controller allocates at least some hardware resources of the node in response to requests from the at least one guest blockchain,
wherein the host controller comprises a host blockchain.

### Claim 2 (depends on 1)

The method of claim 1, wherein the at least some hardware resources comprise input/output hardware.

### Claim 3 (depends on 2)

The method of claim 2, wherein the input/output hardware comprises disk access and network interface hardware.

### Claim 4 (depends on 1)

The method of claim 1, wherein the at least some hardware resources comprise processor resources of the node for compute operations that satisfy at least one of a processor time and processor intensity threshold.

### Claim 5 (depends on 1)

The method of claim 1, wherein the at least one guest blockchain is not stored in the host blockchain.

### Claim 6 (depends on 1)

The method of claim 1, wherein the host controller comprises a host blockchain, and wherein the at least one guest blockchain is stored in the host blockchain.

### Claim 7 (depends on 6)

The method of claim 6, wherein the at least one guest blockchain comprises a first guest blockchain and a second guest blockchain, and wherein the second guest blockchain is stored in the first guest blockchain.

### Claim 8 (depends on 6)

The method of claim 6, wherein the at least one guest blockchain comprises a first guest blockchain and a second guest blockchain, and wherein the second guest blockchain is stored in the host blockchain and not in the first guest blockchain.

### Claim 9 (depends on 1)

The method of claim 1, further comprising storing on the host blockchain a history of hardware operations using the hardware resources allocated by the host blockchain.

### Claim 10 (depends on 9)

The method of claim 9, wherein the at least one guest blockchain comprises a third guest blockchain and wherein the hardware operations result from running an application stored as computer program code on the third guest blockchain, and further comprising storing on the host blockchain a history of states of the application at different times.

### Claim 11 (depends on 1)

The method of claim 1, wherein the at least one guest blockchain comprises a third guest blockchain and wherein the hardware resources are allocated in response to running an application stored as computer program code on the third guest blockchain, and further comprising storing on the host blockchain a history of states of the application at different times.

### Claim 12 (depends on 10)

The method of claim 10, further comprising:
(a) accessing the history of states of the application; and
(b) reverting the application to a previous state that comprises part of the history of states.

### Claim 13 (depends on 12)

The method of claim 12, further comprising:
(a) permitting another computer node to connect to the host blockchain; and
(b) reverting the application in response to input from the other computer node.

### Claim 14 (depends on 12)

The method of claim 12, further comprising using the hypervisor to route to the third guest blockchain actions to be performed by the application.

### Claim 15 (depends on 14)

The method of claim 14, further comprising storing on the host blockchain a history of the actions routed to the third guest blockchain by the hypervisor at different times.

### Claim 16 (depends on 15)

The method of claim 15, wherein the at least one guest blockchain further comprises additional blockchains and the actions to be performed by the third guest blockchain comprise a proper subset of all actions routed by the hypervisor to the third guest blockchain and to the additional blockchains in an original order, and further comprising, after reverting the application to a previous state, routing at least some of the actions to the third guest and additional blockchains in an order different than the original order.

### Claim at position 17

-18. (canceled)

### Claim 19

A system for virtualizing blockchains, the system comprising:
(a) network interface hardware for interfacing with another computer node;
(b) non-volatile memory having stored on it the first blockchain;
(c) a processor communicatively coupled to the data store and network interface hardware; and
(d) a memory communicatively coupled to the processor and having stored on it computer program code that is executable by the processor and that when executed by the processor causes the processor to perform a method comprising:
(i) running a hypervisor on a computer node, wherein the hypervisor comprises a host controller; and
(ii) running at least one guest blockchain on the hypervisor, wherein the host controller allocates at least some hardware resources of the node in response to requests from the at least one guest blockchain,
wherein the host controller comprises a host blockchain.

### Claim 20

A non-transitory computer readable medium having stored thereon computer program code that is executable by a processor and that when executed by the processor causes the processor to perform a method for virtualizing blockchains, the method comprising:
(a) running a hypervisor on a computer node, wherein the hypervisor comprises a host controller; and
(b) running at least one guest blockchain on the hypervisor, wherein the host controller allocates at least some hardware resources of the node in response to requests from the at least one guest blockchain,
wherein the host controller comprises a host blockchain.
