diff options
| author | Alex Beregszaszi <alex@rtfs.hu> | 2018-08-01 23:23:06 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-08-01 23:23:06 +0800 |
| commit | 1f832e068b2d2c79fff870742d867b655b62f691 (patch) | |
| tree | 92ced4e8c40fe9aecdcb77363dcd34802113e47f | |
| parent | ce99a5ce7f98b3dfb86ea8397a5117332af33f2a (diff) | |
| parent | 0ad646635f6970de266138d4bdb3f1970406adfb (diff) | |
| download | dexon-solidity-1f832e068b2d2c79fff870742d867b655b62f691.tar dexon-solidity-1f832e068b2d2c79fff870742d867b655b62f691.tar.gz dexon-solidity-1f832e068b2d2c79fff870742d867b655b62f691.tar.bz2 dexon-solidity-1f832e068b2d2c79fff870742d867b655b62f691.tar.lz dexon-solidity-1f832e068b2d2c79fff870742d867b655b62f691.tar.xz dexon-solidity-1f832e068b2d2c79fff870742d867b655b62f691.tar.zst dexon-solidity-1f832e068b2d2c79fff870742d867b655b62f691.zip | |
Merge pull request #4639 from ethereum/docs-fix-specify-limit
Small clarifications around the 2300 gas stipend from transfer and send
| -rw-r--r-- | docs/common-patterns.rst | 2 | ||||
| -rw-r--r-- | docs/contracts.rst | 5 | ||||
| -rw-r--r-- | docs/security-considerations.rst | 2 |
3 files changed, 6 insertions, 3 deletions
diff --git a/docs/common-patterns.rst b/docs/common-patterns.rst index 7c38b0e7..bc8286b2 100644 --- a/docs/common-patterns.rst +++ b/docs/common-patterns.rst @@ -93,7 +93,7 @@ Notice that, in this example, an attacker could trap the contract into an unusable state by causing ``richest`` to be the address of a contract that has a fallback function which fails (e.g. by using ``revert()`` or by just -consuming more than the 2300 gas stipend). That way, +consuming more than the 2300 gas stipend transferred to them). That way, whenever ``transfer`` is called to deliver funds to the "poisoned" contract, it will fail and thus also ``becomeRichest`` will fail, with the contract being stuck forever. diff --git a/docs/contracts.rst b/docs/contracts.rst index e87c8a67..2149167b 100644 --- a/docs/contracts.rst +++ b/docs/contracts.rst @@ -563,7 +563,10 @@ Ether (without data). Additionally, in order to receive Ether, the fallback func must be marked ``payable``. If no such function exists, the contract cannot receive Ether through regular transactions. -In the worst case, the fallback function can only rely on 2300 gas being available (for example when send or transfer is used), leaving not much room to perform other operations except basic logging. The following operations will consume more gas than the 2300 gas stipend: +In the worst case, the fallback function can only rely on 2300 gas being +available (for example when `send` or `transfer` is used), leaving little +room to perform other operations except basic logging. The following operations +will consume more gas than the 2300 gas stipend: - Writing to storage - Creating a contract diff --git a/docs/security-considerations.rst b/docs/security-considerations.rst index b997466b..5bb3d81d 100644 --- a/docs/security-considerations.rst +++ b/docs/security-considerations.rst @@ -135,7 +135,7 @@ Sending and Receiving Ether - If a contract receives Ether (without a function being called), the fallback function is executed. If it does not have a fallback function, the Ether will be rejected (by throwing an exception). During the execution of the fallback function, the contract can only rely - on the "gas stipend" (2300 gas) being available to it at that time. This stipend is not enough to access storage in any way. + on the "gas stipend" it is passed (2300 gas) being available to it at that time. This stipend is not enough to access storage in any way. To be sure that your contract can receive Ether in that way, check the gas requirements of the fallback function (for example in the "details" section in Remix). |