Enforcing multi-use constraints on a blockchain
US-2018139043-A1 · May 17, 2018 · US
US10291413B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10291413-B2 |
| Application number | US-201715595597-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 15, 2017 |
| Priority date | Feb 17, 2017 |
| Publication date | May 14, 2019 |
| Grant date | May 14, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 1. A method comprising: in a record entry hardware system: receiving, at a blockchain application programming interface (API) executing on blockchain management circuitry (BMC), a message from node circuitry in communication with client circuitry; determining, at the BMC, a correction for a previous record entry stored within a blockchain, the previous record entry associated with the client circuity, the correction comprising changing an original transaction date for the previous record entry to a corrected transaction date; at consensus logic within the BMC and in communication with the blockchain API: accessing, in memory within the BMC, an identifier of a consensus operating procedure; and selecting the consensus operating procedure responsive to the blockchain, the consensus operating procedure detailing a rule for application to block content prior to appending blocks to the blockchain; obtaining a previous accumulated value stored within a selected block of the blockchain and generated without the correction; applying the consensus operating procedure to generate a corrected accumulated value from the previous accumulated value, where the applying comprises performing a processor-level operation using the correction and the previous record entry as inputs; and generating a corrective indicator comprising: a reference to the previous accumulated value and the selected block, and the corrected accumulated value; generating a hash value using content of a previous block in the blockchain; after complying with the consensus operating procedure, generating a corrective block for the blockchain, the generating the corrective block responsive to the corrective indicator and the hash value generated using the content of the previous block in the blockchain; designating a period of review between the original transaction date and the corrected transaction date; and marking, for review, a specific existing block storing a specific record entry with an affected transaction date during the period of review by adding a review indicator for the specific existing block to metadata for the blockchain. 2. The method of claim 1 , further comprising: determining a change to the consensus operating procedure; and responsive to the change to the consensus operating procedure, determining to update the previous record entry. 3. The method of claim 1 , where generating the corrective block comprises correcting the previous record entry while maintaining storage of the previous accumulated value in the selected block. 4. The method of claim 1 , where applying the consensus operating procedure to generate the corrected accumulated value comprises marking the previous record entry as erroneous; and where performing the processor-level operation using the correction and the previous record entry as inputs comprises: adjusting the previous accumulated value to cancel an effect of the previous record entry. 5. The method of claim 1 , further comprising applying the consensus operating procedure to define a new threshold maximum. 6. The method of claim 5 , further comprising cancelling an effect of a transaction determined to occur after the new threshold maximum was exceeded. 7. The method of claim 5 , further comprising accounting for an effect of a transaction determined to occur before the new threshold maximum was exceeded. 8. A device comprising: memory configured to store a blockchain; blockchain management circuitry (BMC) in data communication with the memory and communication interface circuitry, the BMC configured to: with consensus logic within the BMC: access the blockchain in the memory; and access an identifier of a consensus operating procedure responsive to the blockchain, the consensus operating procedure detailing a rule for application to block content prior to appending blocks to the blockchain; receive, at blockchain application programming interface (API) executing on the BMC and in communication with consensus logic, a message from node circuitry in communication with client circuitry; determine a correction for a previous record entry, the correction comprising changing an original transaction date for the previous record entry to a corrected transaction date, the previous record entry associated with the client circuitry; obtain a previous accumulated value stored within a selected block of the blockchain and generated without the correction; apply the consensus operating procedure to generate a corrected accumulated value from a previous accumulated value by performing a processor-level operation using the correction and the previous record entry as inputs; and generate a corrective indicator comprising: a reference to the previous accumulated value and the selected block, and the corrected accumulated value; generate a hash value using content of a previous block on the blockchain; after complying with the consensus operating procedure, generate a corrective block for the blockchain responsive to the corrective indicator and the hash value; designate a period of review between the original transaction date and corrected transaction date; and mark, for review, a specific existing block storing a specific record entry with an affected transaction date during the period of review by adding a review indicator for the specific existing block to metadata for the blockchain. 9. The device of claim 8 , where the BMC is further configured to apply the consensus operating procedure to generate a corrected accumulated value by defining a new threshold maximum. 10. The device of claim 9 , where the BMC is configured to cancel an effect of a transaction determined to occur after the new threshold maximum was exceeded. 11. The device of claim 9 , where the BMC is configured to account for an effect of a transaction determined to occur before the new threshold maximum was exceeded. 12. A system comprising: a display configured to present a representation of specific data from a blockchain, the specific data comprising values from a previous transaction; input interface circuitry configured to accept input of an alteration to the specific data; client circuitry coupled to the input interface circuitry and the display, the client circuitry configured to: receive the alteration to the specific data from the input interface circuitry, the alteration comprising changing an original transaction date for the previous transaction to a corrected transaction date; receive the specific data, and generate the representation of the specific data; specific node circuitry in data communication with the client circuitry, the specific node circuitry configured to: receive the alteration to the specific data from the client circuitry, compile the alteration to the specific data into a correction for a previous record entry for the previous transaction, generate a request for the specific data, and after receiving the specific data, forwarding the specific data to the client circuitry; and blockchain management circuitry (BMC) in data communication with node circuitry, the BMC configured to: at a blockchain application programming interface (API) configured to execute on the BMC, receive the correction for the previous record entry from the node circuitry, at consensus logic within the BMC, the consensus logic in data communication with the blockchain API: access a definition for a consensus operating procedure, the consensus operating procedure detailing a rule for application to block content prior to appending blocks to the blockchain; and apply the consensus operating procedure to generate a corrected
using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263) · CPC title
Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM] · CPC title
Physics · mapped topic
Protecting personal data, e.g. for financial or medical purposes · CPC title
Office automation; Time management · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.