Blockchain-based transaction processing
US-11222011-B2 · Jan 11, 2022 · US
US12531876B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12531876-B2 |
| Application number | US-202218565362-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 16, 2022 |
| Priority date | May 31, 2021 |
| Publication date | Jan 20, 2026 |
| Grant date | Jan 20, 2026 |
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.
In known implementations of distributed ledgers, all of the transactions linked to a service are archived in nodes involved in the implementation of the service. This makes it possible to verify the authenticity and the integrity of the transactions and to ensure that the service that is provided is compliant. This poses a problem for nodes having limited storage capacities, some ledgers possibly reaching a significant size and ultimately potentially making it impossible for some modes to be able to record new transactions, thus causing a problem in terms of controlling the actual execution of the operations linked to these transactions. The present solution allows some nodes involved in the implementation of a service to be able to empty their local ledgers without this jeopardizing the correct operation of the associated distributed ledger. The transparency and the permanence of the transactions relating to the service are thus guaranteed.
Opening claim text (preview).
The invention claimed is: 1 . A method for managing a local ledger of a node belonging to a set of nodes contributing to an implementation of a service, the local ledger memorizing at least one first transaction comprising data generated during an execution, by the node, of a function contributing to the implementation of the service and at least one parameter proving the validity of the transaction and allowing adding the first transaction in a distributed ledger memorizing all of the transactions relating to the implementation of the service, the method being implemented by the node and comprising: receiving a message comprising an authorization to empty contents of the local ledger, the message being emitted by an archivist node, memorizing in an archivist node local ledger a copy of the transactions recorded in the distributed ledger; prior to emptying of the local ledger, recording a copy of a last state of the local ledger; and generating a second transaction serving as a reference transaction for the transactions intended to be memorized in the local ledger following the emptying, the data comprised in the second transaction depending on the copy of the last state of the local ledger. 2 . The method according to claim 1 , comprising verifying an authenticity of the message comprising the authorization to empty the contents of the local ledger by means of a reference transaction memorized in the distributed ledger, the reference transaction comprising at least one identifier of at least one authorized archiving node. 3 . The method according to claim 1 , comprising an emission step, to at least one archivist node, requesting authorization to empty the local ledger. 4 . The method according to claim 3 , wherein the message requesting authorization to empty the local ledger is emitted in response to detection of reaching a limit storage volume of the local ledger. 5 . The method according to claim 1 , wherein the message comprising the authorization to empty the contents of the local ledger is comprised in a transaction memorized in the distributed ledger. 6 . The method according to claim 1 , further comprising: verifying at least one condition for triggering emptying of the local ledger, the verification of the condition triggering an implementation of recording a copy of a last state of the local ledger. 7 . The method according to claim 1 , wherein the message comprising the authorization to empty the contents of the local ledger also comprises an identifier of the function. 8 . The method according to claim 1 , wherein, receiving the message comprising the authorization to empty the contents of the local ledger triggers execution of an archiving function leading to emptying of the local ledger. 9 . The method according to claim 8 , wherein the archiving function executed by the node is a smart contract. 10 . A method for managing a distributed ledger memorizing all transactions relating to a service implemented by a set of nodes, a node executing at least one function contributing to the implementation of the service and comprising a local ledger memorizing at least one first transaction comprising data generated during an execution of the function and at least one parameter proving a validity of the transaction and allowing adding the first transaction in the distributed ledger, the method being implemented by an archivist node, memorizing in an archivist node local ledger a copy of the distributed ledger, the method comprising: detecting a triggering event relating to the distributed ledger; in response to the detection of the triggering event, broadcasting, to the nodes of the set of nodes contributing to the implementation of the service, a message comprising an authorization to empty the contents of the local ledger of the nodes of the set of nodes; and memorizing, in the archivist node local ledger, a new reference transaction of the nodes of the set of nodes having emptied the local ledger. 11 . The method for managing a distributed ledger according to claim 10 , wherein the triggering event belongs to a group comprising: a regular time interval, a reception of a message, emitted by at least one node of the set of nodes, requesting authorization to empty the local ledger of the at least one node, a time schedule, a number of transactions memorized in the distributed ledger, a limit storage volume, an update of the function to be executed, an addition of another node to the set of nodes, a deletion of a node from the set of nodes, an addition of another archivist node, a deletion of an archivist node. 12 . A node belonging to a set of nodes contributing to an implementation of a service, and comprising a local ledger memorizing at least one first transaction comprising data generated during an execution, by the node, of a function contributing to the implementation of the service and at least one parameter proving a validity of the transaction and allowing adding the first transaction in a distributed ledger memorizing all of the transactions relating to the implementation of the service, the node comprising means for: receiving a message comprising an authorization to empty contents of the local ledger, the message being emitted by an archivist node, memorizing in an archivist node local ledger a copy of the transactions recorded in the distributed ledger; prior to emptying of the local ledger, recording a copy of a last state of the local ledger; and generating a second transaction serving as a reference transaction for the transactions intended to be memorized in the local ledger following the emptying, the data comprised in the second transaction depending on the copy of the last state of the local ledger. 13 . An archivist node memorizing in an archivist node local ledger a copy of a distributed ledger memorizing all transactions relating to a service implemented by a set of nodes, a node executing at least one function contributing to the implementation of the service and comprising a local ledger memorizing at least one first transaction comprising data generated during an execution of the function and at least one parameter proving a validity of the transaction and allowing adding the first transaction in the distributed ledger, the archivist node comprising means for: detecting a triggering event relating to the distributed ledger; in response to the detection of the triggering event, broadcasting, to the nodes of the set of nodes contributing to the implementation of the service, a message comprising an authorization to empty contents of the local ledger of the nodes of the set of nodes; and memorizing, in the archivist node local ledger, a new reference transaction of the nodes of the set of nodes having emptied the local ledger. 14 . A processing circuit comprising a processor and a memory, the memory storing program code instructions of a computer program for executing the method according to claim 1 , when the computer program is executed by the processor. 15 . A processing circuit comprising a processor and a memory, the memory storing program code instructions of a computer program for executing the method according to claim 10 , when the computer program is executed by the processor.
the source of the received data · CPC title
using hash chains, e.g. blockchains or hash trees · CPC title
involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title
received data contents, e.g. message integrity · CPC title
Protecting data integrity, e.g. using checksums, certificates or signatures · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.