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_1102 [2020/05/07 18:56] nick ↷ Page moved from dido:public:xapend.stds:defact:ethereum:eip:erc_1102 to dido:public:ra:xapend.stds:defact:ethereum:eip:erc_1102 |
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_1102 [2020/11/13 02:21] (current) nick ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======== EIP 1102: Opt-in account exposure (DRAFT) ========= | + | ==== EIP 1102: Opt-in account exposure (DRAFT) ==== |
| - | [[dido:public:xapend.stds:defact:ethereum| 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 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 15: | Line 15: | ||
| </table> | </table> | ||
| - | + | === Simple summary === | |
| - | ====== Simple summary ====== | + | |
| : //This proposal describes a way for DOM environments to expose user accounts in a way that requires user approval.// | : //This proposal describes a way for DOM environments to expose user accounts in a way that requires user approval.// | ||
| - | ====== Abstract ====== | + | === Abstract === |
| : //The previous generation of Ethereum-enabled DOM environments follows a pattern of injecting a provider populated with accounts without user consent. This puts users of such environments at risk because malicious websites can use these accounts to view detailed account information and to arbitrarily initiate unwanted transactions on a user’s behalf.// | : //The previous generation of Ethereum-enabled DOM environments follows a pattern of injecting a provider populated with accounts without user consent. This puts users of such environments at risk because malicious websites can use these accounts to view detailed account information and to arbitrarily initiate unwanted transactions on a user’s behalf.// | ||
| : //This proposal outlines a protocol in which Ethereum-enabled DOM environments expose no accounts until the user approves account access.// | : //This proposal outlines a protocol in which Ethereum-enabled DOM environments expose no accounts until the user approves account access.// | ||