IP Library › Granted Patent US 12,277,108
Granted Patent B2
US 12,277,108 · App. 17/549,941 · Granted Apr 15, 2025

High performance distributed system of record with ledger configuration system

Inventors: David C. Carver (Lexington, MA); Samuel Erb (Somerville, MA)
Assignee: Akamai Technologies, Inc.
G06F16/2379
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,277,108
App. No.
17/549,941
Filed
Dec 14, 2021
Granted
Apr 15, 2025
Kind
B2
Art Unit
2152
USPC
707/703
Abstract

A high-performance distributed ledger and transaction computing network fabric over which large numbers of transactions are processed concurrently in a scalable, reliable, secure and efficient manner. In one embodiment, the computing network core is configured to support a distributed blockchain network that organizes data in a manner that allows communication, processing and storage of blocks of the chain to be performed concurrently at very high performance and low latency, even when the transactions themselves originate from distant sources. This data organization relies on segmenting a transaction space within autonomous but cooperating computing nodes that are configured as a processing mesh. The system also provides for confidence-based consensus. A configuration system is provided to enable configuration updates to be securely implemented across various subsets of the computing nodes.

Claims (27)

1. A method, comprising:

configuring a set of transaction handling computing elements comprising hardware and associated software that receive and process transaction requests into an append-only immutable chain of data blocks, wherein a data block is a collection of transactions, and wherein presence of a transaction recorded within a data block is verifiable via a cryptographic hash;

responsive to a request to update a configuration associated with the append-only immutable chain of data blocks, issuing a key exchange request to a subset of the transaction handling computing elements, the subset of the transaction handling computing elements being responsible for executing a consensus that finalizes one or more data blocks for inclusion into the append-only immutable chain of data blocks;

responsive to issuing the key exchange request, determining whether key exchange material has been received from the subset of the transaction handling computing elements, the key exchange material being one or more keys used in the consensus;

upon a determination that key exchange material has been received, verifying the key exchange material;

responsive to verifying the key exchange material, embedding configuration information into the append-only immutable chain of data blocks, the configuration information comprising data block header annotations that, for a given data block, convey a network configuration for the given data block, the configuration information also including a valid from depth annotation that specifies a minimum depth at which the configuration is valid;

providing the configuration information, as a configuration update, to the set of transaction handling computing elements; and

activating the configuration update when a depth as specified in the valid from depth annotation is reached.

2. The method as described in claim 1 wherein the configuration information is instantiated at a given depth or time.

3. The method as described in claim 2 wherein instantiating the configuration information adds the configuration to a given block header.

4. The method as described in claim 1 wherein the append-only immutable chain of data blocks is a blockchain.

5. The method as described in claim 1 wherein a quorum of transaction handling computing elements must accept the configuration information as an update before the configuration is enforced.

6. The method as described in claim 1 further including generating the configuration.

7. The method as described in claim 6 wherein the configuration is generated using an administrative interface.

8. The method as described in claim 7 wherein the configuration comprises a unique epoch identifier.

9. The method as described in claim 8 wherein the unique epoch identifier is an annotation used in the block header to identify which network configuration was in-use when the data block was generated.

10. The method as described in claim 7 wherein the configuration also includes a network chain time, a restart depth and a restart block hash.

11. A configuration apparatus, configured in association with a set of transaction handling computing elements that comprise a network core that receive and process transaction requests into an append-only immutable chain of data blocks, wherein a data block is a collection of transactions, and wherein presence of a transaction recorded within a data block is verifiable via a cryptographic hash, the apparatus comprising:

a hardware processor;

computer memory holding computer program code executed by the hardware processor, the computer program code configured to:

responsive to a request to update a configuration associated with the append-only immutable chain of data blocks, issue a key exchange request to a subset of the transaction handling computing elements, the subset of the transaction handling computing elements being responsible for executing a consensus that finalizes one or more data blocks for inclusion into the append-only immutable chain of data blocks;

responsive to issuing the key exchange request, determine whether key exchange material has been received from the subset of the transaction handling computing elements, the key exchange material being one or more keys used in the consensus;

upon a determination that key exchange material has been received, verify the key exchange material;

responsive to verifying the key exchange material, embed configuration information into the append-only immutable chain of data blocks, the configuration information comprising data block header annotations that, for a given data block, convey a network configuration for given data block, the configuration information also including a valid from depth annotation that specifies a minimum depth at which the configuration is valid;

provide the configuration information, as a configuration update, to the set of transaction handling computing elements; and

activate the configuration update when a depth as specified in the valid from depth annotation is reached.

12. The configuration apparatus as described in claim 11 wherein the computer program code is further configured to generate the configuration.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 17, 2021
From: CARVER, DAVID C.; ERB, SAMUEL
To: AKAMAI TECHNOLOGIES, INC.
Reel/Frame 058412/0155 →
Continuity (1)
Related Publication 20230185794A1 · Jun 15, 2023
References Cited (42)
US 5944779A · Blum · 1999 [cited by applicant]
US 6108703A · Leighton et al. · 2000 [cited by applicant]
US 7036146B1 · Goldsmith · 2006 [cited by applicant]
US 7111057B1 · Sherman et al. · 2006 [cited by applicant]
US 7240100B1 · Wein et al. · 2007 [cited by applicant]
US 7376716B2 · Dilley et al. · 2008 [cited by applicant]
US 7472178B2 · Lisiecki et al. · 2008 [cited by applicant]
US 7596619B2 · Leighton et al. · 2009 [cited by applicant]
US 9069610B2 · Chakravorty et al. · 2015 [cited by applicant]
US 9813343B2 · Williams et al. · 2017 [cited by applicant]
US 10250708B1 · Carver et al. · 2019 [cited by applicant]
US 10615971B2 · Acar · 2020 [cited by examiner]
US 10630769B2 · Carver et al. · 2020 [cited by applicant]
US 11018850B2 · Carver et al. · 2021 [cited by applicant]
US 20040093419A1 · Weihl et al. · 2004 [cited by applicant]
US 20070172235A1 · Snider et al. · 2007 [cited by applicant]
US 20120324472A1 · Rossbach et al. · 2012 [cited by applicant]
US 20150188943A1 · Williams et al. · 2015 [cited by applicant]
US 20170031676A1 · Cecchetti et al. · 2017 [cited by applicant]
US 20170109735A1 · Sheng et al. · 2017 [cited by applicant]
US 20170132620A1 · Miller et al. · 2017 [cited by applicant]
US 20170195161A1 · Ruel et al. · 2017 [cited by applicant]
US 20170337534A1 · Goeringer et al. · 2017 [cited by applicant]
US 20170344580A1 · King · 2017 [cited by applicant]
US 20170346693A1 · Dix et al. · 2017 [cited by applicant]
US 20170352012A1 · Hearn et al. · 2017 [cited by applicant]
US 20180053161A1 · Bordash et al. · 2018 [cited by applicant]
US 20180109541A1 · Gleichauf · 2018 [cited by applicant]
US 20180130050A1 · Taylor et al. · 2018 [cited by applicant]
US 20190190697A1 · Cunico et al. · 2019 [cited by applicant]
US 20190199516A1 · Carver et al. · 2019 [cited by applicant]
US 20190220324A1 · Carver et al. · 2019 [cited by applicant]
US 20200067774A1 · Saltsgaver et al. · 2020 [cited by applicant]
US 20200127813A1 · Millar et al. · 2020 [cited by applicant]
US 20200162239A1 · Carver et al. · 2020 [cited by applicant]
US 20200167341A1 · Carver et al. · 2020 [cited by applicant]
US 20200167779A1 · Carver et al. · 2020 [cited by applicant]
US 20200186568A1 · Erb et al. · 2020 [cited by applicant]
US 20200193432A1 · Millar et al. · 2020 [cited by applicant]
US 20200334674A1 · Youngblood et al. · 2020 [cited by applicant]
US 20210182277A1 · Carver et al. · 2021 [cited by applicant]
Thyagarajan, Sri Aravinda Krishnan et al., “Reparo: Publicly Verifiable Layer to Repair Blockchains”, Springer, appearing in Financial Cryptography and Data Security, 25th International Conference, FC 2021, Virtual Even… [cited by examiner]