# US 2022/0045846 A1 · Blockchain platform service

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

- Number: US 2022/0045846 A1
- Document ID: US20220045846A1
- Status: Published application
- Kind: A1
- Application number: 17/366,437
- Filed: 2021-07-02
- Published: 2022-02-10
- Earliest claimed: 2019-11-13
- Assignees: First Genesis, Inc.
- Applicants: First Genesis, Inc.
- Inventors: Cedric Harris; Ronald Watty
- Web page: https://patentgrep.com/patent/US20220045846A1

## CPC

- 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/0819: {Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) (network architectures or network communication protocols for key distribution in a packet data network H04L63/062)}
- H04L 9/3247: {involving digital signatures}
- H04L 51/234: for tracking messages
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The present invention describes an architecture for increasing the performance of blockchain using a virtual actor model to provide stateful services that are highly scalable and responsive to events as they support publishing and/or subscribing to streaming messages and/or events. The architecture as described leverages established distributed design practices to achieve what would otherwise require costly resource intensive hardware.

## Claims

### Claim 1

A system comprising:
a plurality of decentralized servers, each server including at least one server processor, a server machine-readable medium, at least one server database, communication hardware and software, and server processor executable instructions encoded in hardware, firmware, software, or combinations thereof, and
one or more computing devices, each computing device including at least one computing device processor, a computing device machine-readable medium, computing device communication hardware and software, and computing device processor executable instructions encoded in hardware, firmware, software, or combinations thereof,
the one or more computing device processors are configured to:
implement a virtual actor architecture comprising:
a plurality of virtual actors resident on one or more virtual machines, each virtual actor including a mailbox, wherein the virtual actors comprise primitive, isolated, non-memory sharing or stateful units of computation, and
a messaging service resident on the one or more virtual machines;
create one or more queryable blockchain ledgers, each of the one or more queryable blockchain ledgers including unique cryptographic signatures, each of the unique cryptographic signatures correspond to a block of one or more blockchains, each block of the one or more blockchains including one or more transactions;
store the one or more queryable blockchain ledgers one the servers and the computing devices and virtual machines so that the one or more queryable blockchain ledgers are available to the virtual actors;
submit a query comprising an entry of the one or more queryable blockchain ledgers, via the messaging service, from any of the virtual actors corresponding to a given block in the one or more blockchains;
read a content of the given block of the one or more blockchains to analyze, research, or verify the content of the given block of the one or more blockchains;
write to the queryable blockchain ledger, via the messaging service, from any of the virtual actors, and
add a block to the one or more blockchains to which the added block pertains; and
broadcast, via the messaging service, to the other virtual actors and virtual machines the added block to the one or more blockchains and the one or more queryable blockchain ledgers,
wherein the virtual actor architecture facilitates a scalable echo system or an abstraction of the blockchain via the queryable blockchain ledger in order to alleviate blockchain mining latency.

### Claim at position 2

2-20. (canceled)

### Claim 21 (depends on 1)

The system of claim 1, wherein the one or more computing device processors are further configured to:
receive a web request in a HTTP protocol, from any of the virtual actors corresponding to a given block in the one or more blockchains;
convert the web request to a message form usable by the messaging service;
submit a query comprising an entry in one of the one or more queryable blockchain ledgers, via the messaging service;
read a content of the given block of one or more blockchains to analyze, research, or verify the content of the given block of the one blockchain;
write to the queryable blockchain ledger, via the messaging service, from any of the virtual actors, and
add a block to the one blockchain; and
broadcast, via the messaging service, to the other virtual actors and virtual machines the added block to the one blockchain and the corresponding queryable blockchain ledger.

### Claim 22 (depends on 1)

The system of claim 1, wherein the one or more computing device processors are further configured to:
form a NoSQL OLAP persistent storage retaining virtual actor states in real-time, and
maintain the one or more queryable blockchain ledgers,
whereby horizontal scaling of services is achieved through operations running inside one or more Kubemetes clusters that consist of multiple PODS run on the one or more virtual machines running containerized application images.

### Claim 23 (depends on 1)

The system of claim 1, wherein the message format is selected from the group consisting of JSON, XML, CSV, JSV, ProtoBuf, SOAP, MessageWire, HTML, Text, Byte Array, and Streams.

### Claim 24 (depends on 1)

The system of claim 1, wherein the one or more queryable blockchain ledgers comprises:
Merkle Trees.

### Claim 25 (depends on 24)

The system of claim 24, wherein the one or more computing device processors are further configured to:
when a parent Merkle Tree receives a message of the newly added transactions, the parent Merkle Tree updates its corresponding Merkle Tree root hash key,
whereby the updated Merkle Tree root hash key is broadcast to all other virtual actors via the messaging service.

### Claim 26 (depends on 1)

The system of claim 1, wherein the one or more computing device processors are further configured to:
restrict use of consensus algorithms to virtual actor node discoverability based on:
(a) the existence and location of virtual actor node within its cluster, and
(b) Raft consensus algorithms not to agree on transactions.

### Claim 27 (depends on 1)

The system of claim 1, wherein the system supports both Restful API and Server Sent Event (SSE).

### Claim 28 (depends on 27)

The system of claim 27, wherein the one or more computing device processors are further configured to:
the system supports Restful API, and
the topology of the architecture is configured to be hosted on the cloud and incorporate a series of decentralized servers via load balancers to distribute Restful API traffic across a cluster of containerized virtual actor node masters,
whereby communication with a specific virtual actor node is achieved via messaging over a series of Restful API connections.

### Claim 29 (depends on 27)

The system of claim 27, wherein the system supports SSE, further comprising
a persisted TCP/IP connection configured to persist a single bi-directional connection between a client and
a virtual node master within a Kubemetes cluster.

### Claim 30 (depends on 29)

The system of claim 29, wherein the virtual actors comprise a plurality of virtual actor cluster node communicates with each other via the messaging service over an SSE persistent connection.

### Claim 31

A method, implemented on a system comprising a plurality of decentralized servers including at least one server processor, a server machine-readable medium, at least one server database, communication hardware and software, and server processor executable instructions encoded in hardware, firmware, software, or combinations thereof, and one or more computing devices including at least one computing device processor, a computing device machine-readable medium, computing device communication hardware and software, and computing device processor executable instructions encoded in hardware, firmware, software, or combinations thereof, comprising:
implementing, via the one or more computing device processors, a virtual actor architecture, the virtual actor architecture comprises:
a plurality of virtual actors resident on one or more virtual machines, each virtual actor including a mailbox, wherein the virtual actors comprise primitive, isolated, non-memory sharing or stateful units of computation, and
a messaging service resident on the one or more virtual machines;
creating one or more queryable blockchain ledgers, each of the one or more queryable blockchain ledgers including unique cryptographic signatures, each of the unique cryptographic signatures correspond to a block of one or more blockchains, each block of the one or more blockchains including one or more transactions;
storing the one or more queryable blockchain ledgers the at least one servers and the one or more computing devices and the one or more virtual machines so that the one or more queryable blockchain ledgers are available to the virtual actors;
submitting a query comprising an entry in one of the one or more queryable blockchain ledgers, via the messaging service, from any of the virtual actors corresponding to a given block in the one blockchain;
reading a content of the given block of the one blockchain to analyze, research, or verify the transactions of the given block of the one blockchain;
writing to the queryable blockchain ledger, via the messaging service, from any of the virtual actors, and
adding a block to the one blockchain; and
broadcasting, via the messaging service, to the other virtual actors and virtual machines the one blockchain and the one queryable blockchain ledger,
wherein the virtual actor architecture facilitates a scalable echo system or an abstraction of the blockchain via the queryable blockchain ledger in order to alleviate blockchain mining latency.

### Claim 32 (depends on 31)

The method of claim 31, wherein the one or more computing device processors are further configured to:
receiving a web request in a HTTP protocol, from any of the virtual actors corresponding to a given block in the one or more blockchains;
converting the web request to a message form usable by the messaging service;
submitting a query comprising an entry in one of the one or more queryable blockchain ledgers, via the messaging service;
reading a content of the given block of one or more blockchains to analyze, research, or verify the content of the given block of the one blockchain;
writing to the queryable blockchain ledger, via the messaging service, from any of the virtual actors, and
adding a block to the one blockchain; and
broadcasting, via the messaging service, to the other virtual actors and virtual machines the added block to the one blockchain and the corresponding queryable blockchain ledger.

### Claim 33 (depends on 31)

The method of claim 31, wherein the one or more computing device processors are further configured to:
forming a NoSQL OLAP persistent storage retaining virtual actor states in real-time, and
maintaining the one or more queryable blockchain ledgers,
whereby horizontal scaling of services is achieved through operations running inside one or more Kubemetes clusters that consist of multiple PODS run on the one or more virtual machines running containerized application images.

### Claim 34 (depends on 31)

The method of claim 31, wherein the message format is selected from the group consisting of JSON, XML, CSV, JSV, ProtoBuf, SOAP, MessageWire, HTML, Text, Byte Array, and Streams.

### Claim 35 (depends on 31)

The method of claim 31, wherein the one or more queryable blockchain ledgers comprises:
Merkle Trees.

### Claim 36 (depends on 35)

The method of claim 35, wherein the one or more computing device processors are further configured to:
when a parent Merkle Tree receives a message of the newly added transactions, the parent Merkle Tree updates its corresponding Merkle Tree root hash key,
whereby the updated Merkle Tree root hash key is broadcast to all other virtual actors via the messaging service.

### Claim 37 (depends on 31)

The method of claim 31, wherein the one or more computing device processors are further configured to:
restricting use of consensus algorithms to virtual actor node discoverability based on:
(a) the existence and location of virtual actor node within its cluster, and
(b) Raft consensus algorithms not to agree on transactions.

### Claim 38 (depends on 31)

The method of claim 31, wherein the system supports both Restful API and Server Sent Event (SSE).

### Claim 39 (depends on 38)

The method of claim 38, wherein the one or more computing device processors are further configured to:
the system supports Restful API, and
the topology of the architecture is configured to be hosted on the cloud and incorporate a series of decentralized servers via load balancers to distribute Restful API traffic across a cluster of containerized virtual actor node masters,
whereby communication with a specific virtual actor node is achieved via the messaging services over a series of Restful API connections.

### Claim 40 (depends on 38)

The method of claim 38, wherein the system supports SSE, further comprising
a persisted TCP/IP connection configured to persist a single bi-directional connection between a client and
a virtual node master within a Kubemetes cluster.

### Claim 41 (depends on 40)

The method of claim 40, wherein the virtual actors comprise a plurality of virtual actor cluster node communicates with each other via the messaging service over an SSE persistent connection.
