Trustless stateless incentivized remote node network using minimal verification clients
A system and a method are disclosed for using a client that is unsynchronized with a blockchain network to validate blockchain transactions for IoT devices, web apps, mobile apps, and other applications. The client retrieves a register of nodes (acting as information provider or validator) that are synchronized with the blockchain network, selects a node from the register, and transmits an information request to the selected node. The client receives a response to the request, the response including the requested information and validation indicia (e.g., proofs), and determines whether the response is valid based on the validation indicia. The client transmits, in response to determining that the response is valid, a confirmation to the IoT device, web app, mobile app or other applications.
1 . A computer-implemented method comprising acts of:
receiving at least one cryptographic proof;
receiving at least one validation indicium with a signature of a trusted entity; and
verifying the at least one cryptographic proof, at least in part by:
feeding data through the at least one cryptographic proof, thereby obtaining a processed result of the at least one cryptographic proof;
determining whether the processed result of the at least one cryptographic proof matches the at least one validation indicium; and
using the signature of the trusted entity to validate the at least one validation indicium.
2 . The method of claim 1 , wherein:
the at least one cryptographic proof comprises an alleged proof for an interaction on a distributed ledger; and
the act of verifying the at least one cryptographic proof is performed to determine whether the interaction on the distributed ledger has been performed correctly.
3 . The method of claim 2 , wherein:
the distributed ledger comprises a blockchain; and
the at least one validation indicium comprises a blockhash.
4 . The method of claim 2 , wherein:
the act of verifying the at least one cryptographic proof is performed by a client that is unsynchronized with the distributed ledger.
5 . The method of claim 2 , wherein:
the trusted entity comprises a node that is synchronized with the distributed ledger; and
the at least one validation indicium comprises a validation indicium signed by the node.
6 . The method of claim 5 , wherein:
the node comprises a first node that is synchronized with the distributed ledger; and
the method further comprises an act of:
sending, to a second node that is synchronized with the distributed ledger, a request to perform the interaction, the second node being different from the first node.
7 . The method of claim 6 , wherein:
the alleged proof for the interaction is received from the second node; and
the second node sends the alleged proof for the interaction in response to the request to perform the interaction.
8 . The method of claim 5 , further comprising an act of:
selecting the node from a register of nodes that are synchronized with the distributed ledger.
9 . The method of claim 8 , further comprising an act of:
in response to determining that the processed result of the at least one cryptographic proof does not match the at least one validation indicium, sending a report to an entity maintaining the register.
10 . The method of claim 9 , wherein:
the entity maintaining the register comprises a smart contract on the distributed ledger.
11 . The method of claim 5 , further comprising an act of:
maintaining performance information associated with the node that is synchronized with the distributed ledger.
12 . The method of claim 11 , wherein:
the performance information comprises trust information associated with the node; and
the method further comprising an act of:
in response to determining that the processed result of the at least one cryptographic proof does not match the at least one validation indicium, updating the trust information associated with the node.
13 . The method of claim 11 , wherein:
the performance information comprises a value indicative of a recency of one or more incorrect results received from the node.
14 . The method of claim 11 , wherein:
the performance information comprises a value indicative of a frequency and/or an amount of one or more incorrect results received from the node; and
the method further comprises acts of:
determining whether the value has reached a selected threshold; and
in response to determining that the value has reached the selected threshold, blacklisting or reporting the node.
15 . The method of claim 11 , wherein:
the performance information is based, at least in part, on how fast the node responds to one or more requests.
16 . The method of claim 5 , further comprising an act of:
selecting the node from a plurality of nodes that are synchronized with the distributed ledger, based at least in part on a size of a stake deposited by the node and/or a score indicative of how the node performed in connection with past requests.
17 . The method of claim 16 , wherein:
the score indicates correctness of the node's responses to the past requests.
18 . The method of claim 16 , wherein:
the score indicates timeliness of the node's responses to the past requests.
19 . The method of claim 2 , wherein:
the interaction comprises an interaction selected from a group consisting of:
accessing transaction information from the distributed ledger;
interacting with an account on the distributed ledger; and
calling a function in a smart contract on the distributed ledger.
20 . The method of claim 1 , further comprising an act of:
in response to successfully verifying the at least one cryptographic proof, causing a lightweight device to perform a selected action.
21 . A non-transitory computer-readable medium having stored thereon instructions which, when executed by a processor, causes the processor to perform a method comprising acts of:
receiving at least one cryptographic proof;
receiving at least one validation indicium with a signature of a trusted entity; and
verifying the at least one cryptographic proof, at least in part by:
feeding data through the at least one cryptographic proof, thereby obtaining a processed result of the at least one cryptographic proof;
determining whether the processed result of the at least one cryptographic proof matches the at least one validation indicium; and
using the signature of the trusted entity to validate the at least one validation indicium.
22 . A device comprising:
a processor configured to execute instructions; and
a non-transitory computer-readable medium having stored thereon instructions which, when executed by a processor, causes the processor to:
receive at least one cryptographic proof;
receive at least one validation indicium with a signature of a trusted entity; and
verify the at least one cryptographic proof, at least in part by:
feeding data through the at least one cryptographic proof, thereby obtaining a processed result of the at least one cryptographic proof;
determining whether the processed result of the at least one cryptographic proof matches the at least one validation indicium; and
using the signature of the trusted entity to validate the at least one validation indicium.
23 . The device of claim 22 , wherein:
the at least one cryptographic proof comprises an alleged proof for an interaction on a distributed ledger; and
the processor is programmed by the instructions to verify the at least one cryptographic proof to determine whether the interaction on the distributed ledger has been performed correctly.
24 . The device of claim 23 , wherein:
the distributed ledger comprises a blockchain; and
the at least one validation indicium comprises a blockhash.
25 . The device of claim 23 , wherein:
the processor that is programmed by the instructions to verify the at least one cryptographic proof is executing on a client that is unsynchronized with the distributed ledger.
26 . The device of claim 23 , wherein:
the trusted entity comprises a node that is synchronized with the distributed ledger; and
the at least one validation indicium comprises a validation indicium signed by the node.
27 . The device of claim 26 , wherein:
the node comprises a first node that is synchronized with the distributed ledger; and
the processor is further programmed by the instructions to:
send, to a second node that is synchronized with the distributed ledger, a request to perform the interaction, the second node being different from the first node.
28 . The device of claim 27 , wherein:
the alleged proof for the interaction is received from the second node; and
the second node sends the alleged proof for the interaction in response to the request to perform the interaction.
29 . The device of claim 26 , wherein the processor is further programmed by the instructions to:
select the node from a register of nodes that are synchronized with the distributed ledger.
30 . The device of claim 29 , wherein the processor is further programmed by the instructions to:
in response to determining that the processed result of the at least one cryptographic proof does not match the at least one validation indicium, send a report to an entity maintaining the register.
31 . The device of claim 30 , wherein:
the entity maintaining the register comprises a smart contract on the distributed ledger.
32 . The device of claim 26 , wherein the processor is further programmed by the instructions to:
maintain performance information associated with the node that is synchronized with the distributed ledger.
33 . The device of claim 32 , wherein:
the performance information comprises trust information associated with the node; and the processor is further programmed by the instructions to:
in response to determining that the processed result of the at least one cryptographic proof does not match the at least one validation indicium, update the trust information associated with the node.
34 . The device of claim 32 , wherein:
the performance information comprises a value indicative of a recency of one or more incorrect results received from the node.
35 . The device of claim 32 , wherein:
the performance information comprises a value indicative of a frequency and/or an amount of one or more incorrect results received from the node; and
the processor is further programmed by the instructions to:
determine whether the value has reached a selected threshold; and
in response to determining that the value has reached the selected threshold, blacklist or report the node.
36 . The device of claim 32 , wherein:
the performance information is based, at least in part, on how fast the node responds to one or more requests.
37 . The device of claim 26 , wherein the processor is further programmed by the instructions to:
select the node from a plurality of nodes that are synchronized with the distributed ledger, based at least in part on a size of a stake deposited by the node and/or a score indicative of how the node performed in connection with past requests.
38 . The device of claim 37 , wherein:
the score indicates correctness of the node's responses to the past requests.
39 . The device of claim 37 , wherein:
the score indicates timeliness of the node's responses to the past requests.
40 . The device of claim 23 , wherein:
the interaction comprises an interaction selected from a group consisting of: accessing transaction information from the distributed ledger;
interacting with an account on the distributed ledger; and
calling a function in a smart contract on the distributed ledger.
41 . The device of claim 22 , wherein the processor is further programmed by the instructions to:
in response to successfully verifying the at least one cryptographic proof, cause a lightweight device to perform a selected action.