Tiny fixes

This commit is contained in:
Yoichi Hirai 2017-11-27 17:58:21 +01:00
parent 12257d516d
commit b550ed71b8
No known key found for this signature in database
GPG Key ID: E7B75D080FCF7992
1 changed files with 3 additions and 3 deletions

View File

@ -5,7 +5,7 @@
Author: Vitalik Buterin <vitalik@ethereum.org>, Christian Reitwiessner <chris@ethereum.org>; Author: Vitalik Buterin <vitalik@ethereum.org>, Christian Reitwiessner <chris@ethereum.org>;
Type: Standard Track Type: Standard Track
Category: Core Category: Core
Status: Draft Status: Accepted
Created: 2017-02-13 Created: 2017-02-13
## Simple Summary ## Simple Summary
@ -18,9 +18,9 @@ This proposal adds a new opcode that can be used to call another contract (or it
## Motivation ## Motivation
Currently, there is no restriction about what a called contract can do, as long as the computation can be performed with the amount of gas provided. This poses certain difficulties about smart contract engineers: After a regular call, unless you know the called contract, you cannot make any assumptions about the state of the contracts. Furthermore, because you cannot know the order of transactions before they are confirmed by miners, not even an outside observer can be sure about that in all cases. Currently, there is no restriction about what a called contract can do, as long as the computation can be performed with the amount of gas provided. This poses certain difficulties about smart contract engineers; after a regular call, unless you know the called contract, you cannot make any assumptions about the state of the contracts. Furthermore, because you cannot know the order of transactions before they are confirmed by miners, not even an outside observer can be sure about that in all cases.
This EIP adds a way to call other contracts and restrict what they can do in the simplest way. It can be safely assumed that the state of all contracts is the same before and after a static call. This EIP adds a way to call other contracts and restrict what they can do in the simplest way. It can be safely assumed that the state of all accounts is the same before and after a static call.
## Specification ## Specification