This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0712 [2020/05/05 20:49] nick ↷ Links adapted because of a move operation |
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0712 [2020/11/13 02:20] nick ↷ Page moved from dido:public:ra:xapend:xapend.stds:defact:ethereum:eip:erc_0712 to dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0712 |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ======== EIP 712: Ethereum typed structured data hashing and signing (DRAFT) ========= | + | ==== EIP 712: Ethereum typed structured data hashing and signing (DRAFT) ==== |
- | [[dido:public:apdx.stds:defact:ethereum| Return to Ethereum ERCs ]] | + | [[dido:public:ra:xapend:xapend.stds:defact:ethereum:eip| Return to Ethereum ERCs ]] |
- | : **Note**: The following is an excerpt from the official Ethereum site. It is provided here as a connivence and is not authoritative. Refer to the original document as the authoritative reference. | + | : **Note**: The following is an excerpt from the official Ethereum site. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. |
<table> | <table> | ||
Line 13: | Line 13: | ||
| Specification | [[http://eips.ethereum.org/EIPS/eip-712#Specification]] | | | Specification | [[http://eips.ethereum.org/EIPS/eip-712#Specification]] | | ||
| Category | Interface | | | Category | Interface | | ||
- | | Requires | [[dido:public:apdx.stds:defact:ethereum:eip:erc_0191| EIP 155]], [[dido:public:apdx.stds:defact:ethereum:eip:erc_0191| EIP 191]] | | + | | Requires | [[dido:public:ra:xapend:xapend.stds:defact:ethereum:eip:erc_0155|EIP155]], [[dido:public:ra:xapend:xapend.stds:defact:ethereum:eip:erc_0191|EIP191]] | |
</table> | </table> | ||
+ | === Simple Summary === | ||
+ | // Signing data is a solved problem if all we care about are bytestrings. Unfortunately in the real world we care about complex meaningful messages. Hashing structured data is non-trivial and errors result in loss of the security properties of the system.// | ||
- | ====== Simple Summary ====== | + | //As such, the adage “don’t roll your own crypto” applies. Instead, a peer-reviewed well-tested standard method needs to be used. This EIP aims to be that standard.// |
- | : // Signing data is a solved problem if all we care about are bytestrings. Unfortunately in the real world we care about complex meaningful messages. Hashing structured data is non-trivial and errors result in loss of the security properties of the system.// | + | === Abstract === |
- | + | //This is a standard for hashing and signing of typed structured data as opposed to just bytestrings. It includes a// | |
- | : //As such, the adage “don’t roll your own crypto” applies. Instead, a peer-reviewed well-tested standard method needs to be used. This EIP aims to be that standard.// | + | |
- | + | ||
- | ====== Abstract ====== | + | |
- | : //This is a standard for hashing and signing of typed structured data as opposed to just bytestrings. It includes a// | + | |
* //theoretical framework for correctness of encoding functions,// | * //theoretical framework for correctness of encoding functions,// | ||
Line 34: | Line 32: | ||
* //an optimized implementation of the hashing algorithm in EVM.// | * //an optimized implementation of the hashing algorithm in EVM.// | ||
- | : //It does not include replay protection.// | + | //It does not include replay protection.// |