dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0191
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0191 [2020/11/13 02:20] nick ↷ Page moved from dido:public:ra:xapend:xapend.stds:defact:ethereum:eip:erc_0191 to dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0191 |
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0191 [2021/08/18 11:16] (current) murphy |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ==== EIP 191: Signed Data Standard (DRAFT) ==== | ==== EIP 191: Signed Data Standard (DRAFT) ==== | ||
| - | [[dido:public:ra:xapend:xapend.stds:defact:ethereum:eip| Return to Ethereum ERCs ]] | + | [[dido:public:ra:xapend:xapend.b_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 convenience 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. | ||
| Line 22: | Line 22: | ||
| * //Standard Ethereum transactions can be submitted as signed_data. An Ethereum transaction can be unpacked, into the following components: RLP<nonce, gasPrice, startGas, to, value, data> (hereby called RLPdata), r, s and v. If there are no syntactical constraints on signed_data, this means that RLPdata can be used as a syntactically valid presigned transaction.// | * //Standard Ethereum transactions can be submitted as signed_data. An Ethereum transaction can be unpacked, into the following components: RLP<nonce, gasPrice, startGas, to, value, data> (hereby called RLPdata), r, s and v. If there are no syntactical constraints on signed_data, this means that RLPdata can be used as a syntactically valid presigned transaction.// | ||
| - | * //Multisignature wallets have also had the problem that a presigned transaction has not been tied to a particular validator, i.e a specific wallet. Example:// \\ | + | * //Multisignature wallets have also had the problem that a presigned transaction has not been tied to a particular validator, i.e a specific [[dido:public:ra:xapend:xapend.a_glossary:w:wallet|wallet]]. Example:// \\ |
| //1. Users A, B and C have the 2/3-wallet X// \\ | //1. Users A, B and C have the 2/3-wallet X// \\ | ||
| //2. Users A, B and D have the 2/3-wallet Y// \\ | //2. Users A, B and D have the 2/3-wallet Y// \\ | ||
| //3. User A and B submites presigned transaction to X.// \\ | //3. User A and B submites presigned transaction to X.// \\ | ||
| //4. Attacker can now reuse their presigned transactions to X, and submit to Y.// | //4. Attacker can now reuse their presigned transactions to X, and submit to Y.// | ||
dido/public/ra/xapend/xapend.b_stds/defact/ethereum/eip/erc_0191.1605252033.txt.gz · Last modified: 2020/11/13 02:20 by nick
