cerc-io/solidity
10
0
Fork 0
mirror of https://github.com/ethereum/solidity synced 2023-10-03 13:03:40 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Incorporate corrections

Browse Source
This commit is contained in:
Denton Liu 2016-07-07 13:53:57 -04:00
parent 811980afe6
commit ab3531ffc3
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/control-structures.rst
View File

@ -76,8 +76,8 @@ parentheses at the end perform the actual call.
do just about anything. Be prepared in case it calls into other contracts of
your system or even back into the calling contract before the first
call returns. This means
that the called contract can change the state variables of the calling contract
via its functions. Write your functions in a way that such that, for example, calls to
that the called contract can change state variables of the calling contract
via its functions. Write your functions in a way that, for example, calls to
external functions happen after any changes to state variables in your contract
so your contract is not vulnerable to a recursive call exploit.

4
docs/security-considerations.rst
View File

@ -129,7 +129,7 @@ Callstack Depth
===============
External function calls can fail any time because they exceed the maximum
call stack of 1023. In such situations, Solidity throws an exception.
call stack of 1024. In such situations, Solidity throws an exception.
Malicious actors might be able to force the call stack to a high value
before they interact with your contract.
@ -185,7 +185,7 @@ because of the re-entrancy problem explained above.
Note that, also, calls to known contracts might in turn cause calls to
unknown contracts, so it is probably better to just always apply this pattern.
Include a Fail-safe Mode
Include a Fail-Safe Mode
========================
While making your system fully decentralised will remove any intermediary,