User Tools

Site Tools


dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_1186

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_1186 [2021/07/26 13:46]
murphy
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_1186 [2021/08/09 12:00] (current)
murphy
Line 16: Line 16:
  
 === Simple Summary ==== === Simple Summary ====
-  : //One of the great features of Ethereum is the fact, that you can verify all data of the state. But in order to allow verification of accounts outside the client, we need an additional function delivering us the required proof. These proofs are important to secure Layer2-Technologies.//​+  : //One of the great features of Ethereum is the fact, that you can verify all data of the state. But in order to allow verification of accounts outside the [[dido:​public:​ra:​xapend:​xapend.a_glossary:​c:​client|client]], we need an additional function delivering us the required proof. These proofs are important to secure Layer2-Technologies.//​
  
 === Abstract ===  === Abstract === 
   : //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 === 
dido/public/ra/xapend/xapend.b_stds/defact/ethereum/eip/erc_1186.1627321562.txt.gz · Last modified: 2021/07/26 13:46 by murphy