This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_1186 [2021/07/29 12:55] murphy |
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_1186 [2021/08/09 12:00] murphy |
||
---|---|---|---|
Line 21: | Line 21: | ||
: //Ethereum uses a [[ https://github.com/ethereum/wiki/wiki/Patricia-Tree |Merkle Tree]] to store the state of accounts and their storage. This allows verification of each value by simply creating a Merkle Proof. But currently, the standard RPC-Interface does not give you access to these proofs. This EIP suggests an additional RPC-Method, which creates Merkle Proofs for Accounts and Storage Values.// | : //Ethereum uses a [[ https://github.com/ethereum/wiki/wiki/Patricia-Tree |Merkle Tree]] to store the state of accounts and their storage. This allows verification of each value by simply creating a Merkle Proof. But currently, the standard RPC-Interface does not give you access to these proofs. This EIP suggests an additional RPC-Method, which creates Merkle Proofs for Accounts and Storage Values.// | ||
- | ://Combined with a stateRoot (from the blockheader) it enables offline verification of any account or storage-value. This allows especially IOT-Devices or even mobile apps which are not able to run a light client to verify responses from an untrusted source only given a trusted blockhash.// | + | ://Combined with a stateRoot (from the blockheader) it enables offline verification of any account or storage-value. This allows especially [[dido:public:ra:xapend:xapend.a_glossary:i:iot|IOT]]-Devices or even mobile apps which are not able to run a light client to verify responses from an untrusted source only given a trusted blockhash.// |
=== Motivation === | === Motivation === |