Mechanism for efficient validation of finality proof in lightweight distributed ledger clients

1. A method for validation of a finality proof in a distributed ledger system network, the method comprising:

requesting, by a support node, a finality proof from the distributed ledger system network, including a plurality of distributed ledger system network peers;

collecting, by the support node, a required number of confirmations from a plurality of peers in the distributed ledger system network indicating that a requested transaction is finalized;

determining, by the support node, a number of valid confirmations in the required number of confirmations;

determining, by the support node, a number of faulty peers in the plurality of peers;

executing, by the support node, a trusted application;

generating, by the support node, the finality proof based on the required number of collected confirmations, the number of valid confirmations, and the number of faulty peers;

verifying, by the support node, the finality proof inside the trusted application;

signing, by the support node, the finality proof validation inside the trusted application;

transmitting, by the support node, the signed finality proof validation to a client, wherein the client is one of an internet of things (IoT) device, an embedded hardware, a smartphone and a browser extension; and

supplying the validation result, a proof of execution, and the finality proof to the client, wherein the client confirms, based on the validation result, the proof of execution, and the finality proof, that the requested transaction is finalized in the distributed ledger, wherein the support node is an intermediary between the client and the distributed ledger system and the client does not participate in the distributed ledger system.

2. The method according to claim 1 further comprising:

confirming, by the trusted agent based on the verification, that the requested transaction is finalized in the distributed ledger.

3. The method according to claim 1 , wherein the executing, performing, signing, and transmitting steps are each performed by an executor.

4. The method according to claim 1 , wherein executing the trusted application further comprises:

implementing code in a form of the trusted application to be executed in a trusted execution environment (TEE);

instantiating the trusted application in the TEE;

attesting remotely the integrity of the trusted application;

establishing a secure and authenticated channel with the trusted application instance; and

provisioning of a secret key to the trusted application instance through the established channel.

5. The method according to claim 1 , wherein the signing step further comprises:

producing, with the secret provisioned to the trusted application instance, a digital signature over an input combined with a result of the trusted application instance execution.

6. The method according to claim 1 , further comprising:

verifying, with a public certificate corresponding to the provisioned secret, the digital signature produced by the trusted application instance as a proof of the trusted application execution.

7. The method according to claim 1 , wherein performing the finality proof validation inside the trusted application further comprises:

executing the finality proof validation using the trusted application instance to generate a result.

8. The method according to claim 1 , further comprising performing a finality proof validation inside a trusted application by a node in the distributed ledger system.

9. The method according to claim 1 , wherein the distributed ledger system network is a blockchain network.

10. A support node in a distributed ledger system network, the support node comprising one or more processors which, alone or in combination, are configured to provide for performance of the following steps:

requesting, by the support node, a finality proof from the distributed ledger system network, including a plurality of distributed ledger system network peers;

collecting, by the support node, a required number of confirmations from a plurality of peers in the distributed ledger system network indicating that a requested transaction is finalized;

determining, by the support node, a number of valid confirmations in the required number of confirmations;

determining, by the support node, a number of faulty peers in the plurality of peers;

executing, by the support node, a trusted application;

generating, by the support node, the finality proof based on the required number of collected confirmations, the number of valid confirmations, and the number of faulty peers;

verifying, by the support node, the finality proof inside the trusted application;

signing, by the support node, the finality proof validation inside the trusted application;

transmitting, by the support node, the signed finality proof validation to a client, wherein the client is one of an internet of things (IoT) device, an embedded hardware, a smartphone and a browser extension; and

supplying the result, a proof of execution, and the finality proof to the client, wherein the client confirms, based on the result, the proof of execution, and the finality proof, that the requested transaction is finalized in the distributed ledger, wherein the support node is an intermediary between the client and the distributed ledger system and the client does not participate in the distributed ledger system.

11. The system according to claim 10 , wherein the client includes one or more processors which, alone or in combination, are configured to provide for performance of the following step: verifying, by the client, the signature of the finality proof validation.