IP Library Granted Patent US 10,298,405
Granted Patent B2
US 10,298,405 · App. 16/000,028 · Granted May 21, 2019

Hardware blockchain consensus operating procedure enforcement

Inventors: Noel Vivek Ramathal (Chicago, IL); Kevin Bernard Greene (Miami Beach, FL)
Assignee: Accenture Global Solutions Limited
H04L9/3268G06F21/33G06F21/6245G06Q10/10G06Q20/02G06Q50/24G16H10/60G16H15/00H04L9/3239H04L63/102H04L63/0823H04L2209/38
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 10,298,405
App. No.
16/000,028
Granted
May 21, 2019
Kind
B2
Abstract

A system may provide hardware acceleration for corrective blockchain-based record entry. Blockchain management circuitry (BMC) may receive a correction to a record entry. The BMC may access a consensus operating procedure. The BMC may apply the consensus operating procedure to the record entry to determine a corrective indicator. After completing the consensus operating procedure, the BMC may append a corrective block generated based on the record entry and corrective indicator to the blockchain. Accordingly, the system may ensure that corrective blocks added to the blockchain were generated in compliance with the consensus operating procedure.

Claims (72)

1. A method including:

in a record entry hardware system:

determining, at blockchain management circuitry (BMC), that a previous record entry stored within a blockchain is erroneous;

after determining that the previous record entry is erroneous, determining, at the BMC, a correction for the previous record entry;

accessing, in memory within the BMC, an identifier of a particular consensus operating procedure;

selecting the particular consensus operating procedure from among multiple consensus operating procedures defined within the memory,

the particular consensus operating procedure selected responsive to the blockchain;

obtaining a previous accumulated value stored within a previous valid block of the blockchain and generated without the correction, the previous valid block being valid based on consistence between the previous valid block and a previous hash stored within the blockchain;

applying the particular consensus operating procedure to generate a corrected accumulated value from the previous accumulated value, where the applying includes:

marking the previous record entry as erroneous; and

performing a processor-level operation using the correction and the previous record entry as inputs; and

after the previous valid block is validly stored within the blockchain and after applying the particular consensus operating procedure, generating a corrective indicator including:

a reference to the previous accumulated value and the previous valid block, and the corrected accumulated value;

generating a preceding hash value using content of an immediately preceding block in the blockchain;

generating a corrective block for the blockchain,

the generating a corrective block for the blockchain responsive to the corrective indicator and the preceding hash value; and

appending the corrective block to the blockchain,

the previous valid block remaining valid after the corrective block is appended.

2. A device including:

a memory configured to store a blockchain; and

blockchain management circuitry (BMC) in data communication with the memory, the BMC configured to:

access the blockchain in the memory;

determine that a previous record entry stored within the blockchain is erroneous;

after determining that the previous record entry is erroneous, determine a correction for the previous record entry;

access an identifier of a particular consensus operating procedure;

select the particular consensus operating procedure from among multiple consensus operating procedures defined within the memory,

the particular consensus operating procedure selected responsive to the blockchain,

obtain a previous accumulated value stored within a previous valid block of the blockchain and generated without the correction, the previous valid block being valid based on consistence between the previous valid block and a previous hash stored within the blockchain;

apply the particular consensus operating procedure to generate a corrected accumulated value from the previous accumulated value, where the BMC is configured to apply the consensus operating procedure by:

marking the previous record entry as erroneous; and

performing a processor-level operation using the correction and the previous record entry as inputs;

after the previous valid block is validly stored within the blockchain and after applying the particular consensus operating procedure, generate a corrective indicator including:

a reference to the previous accumulated value and the previous valid block; and the corrected accumulated value;

generate a preceding hash value using content of a immediately preceding block in the blockchain;

generate a corrective block for the blockchain,

the corrective block generated responsive to the corrective indicator and the preceding hash value; and

append the corrective block to the blockchain, the previous valid block remaining valid after the corrective block is appended.

3. A product including:

machine-readable media other than a transitory signal; and

instructions stored on the machine-readable media, the instructions configured to, when executed, cause blockchain management circuitry (BMC) to:

determine that a previous record entry stored within a blockchain is erroneous;

after determining that the previous record entry is erroneous, determine a correction for the previous record entry;

access an identifier of a particular consensus operating procedure;

select the particular consensus operating procedure from among multiple consensus operating procedures defined within a memory;

the consensus operating procedure selected responsive to the blockchain;

obtain a previous accumulated value stored within a previous valid block of the blockchain and generated without the correction, the previous valid block being valid based on consistence between the previous valid block and a previous hash stored within the blockchain;

apply the particular consensus operating procedure to generate a corrected accumulated value from the previous accumulated value, where the BMC is configured to apply the consensus operating procedure by:

marking the previous record entry as erroneous; and

performing a processor-level operation using the correction and the previous record entry as inputs; and

after the previous valid block is validly stored within the blockchain and after applying the particular consensus operating procedure, generate a corrective indicator including:

a reference to the previous accumulated value and the previous valid block, and the corrected accumulated value;

generate a preceding hash value using content of a immediately preceding block in the blockchain;

generate a corrective block for the blockchain,

the corrective block generated responsive to the corrective indicator and the preceding hash value; and

append the corrective block to the blockchain, the previous valid block remaining valid after the corrective block is appended.

4. The product of claim 3 , where the previous record entry is erroneous due to an incorrect timestamp.

5. The product of claim 3 , where the previous record entry is erroneous due to an improper classification of a service associated with the previous record entry.

6. The product of claim 3 , where previous record entry is erroneous due to a update to the consensus operating procedure causing a range of affected dates.

7. The product of claim 3 , where the instructions are further configured to cause the BMC receive a message identifying that the previous record entry is erroneous.

8. The product of claim 7 , where the instructions are configured to cause the BMC to receive the message from node circuitry authorized by the BMC.

9. The product of claim 8 , where the instructions are configured cause the BMC to authorize the node circuitry responsive to a credential provided by the node circuitry.

10. The product of claim 3 , where the previous record entry is erroneous due to latency in transaction reporting.

11. The method of claim 1 , where the previous record entry is erroneous due to an incorrect timestamp.

12. The method of claim 1 , where the previous record entry is erroneous due to an improper classification of a service associated with the previous record entry.

13. The method of claim 1 , where previous record entry is erroneous due to a update to the consensus operating procedure causing a range of affected dates.

14. The method of claim 1 , further comprising receiving a message identifying that the previous record entry is erroneous.

15. The method of claim 14 , where the receiving the message comprises receiving the message from node circuitry authorized by the BMC.

16. The method of claim 15 , further comprising authorizing, via the BMC, the node circuitry responsive to a credential provided by the node circuitry.

17. The method of claim 1 , where the previous record entry is erroneous due to latency in transaction reporting.

18. The device of claim 2 , where the BMC is further configured to receive a message identifying that the previous record entry is erroneous.

19. The device of claim 18 , where the BMC is configured to receive the message from node circuitry authorized by the BMC.

20. The device of claim 19 , where the BMC is configured to authorize the node circuitry responsive to a credential provided by the node circuitry.

Continuity (3)
Continuation 15595537 · May 15, 2017
Provisional Application 62460355 · Feb 17, 2017
Related Publication 20180287805A1 · Oct 4, 2018