diff options
| author | Alex Beregszaszi <alex@rtfs.hu> | 2016-10-06 20:24:36 +0800 |
|---|---|---|
| committer | Yoichi Hirai <i@yoichihirai.com> | 2016-10-06 22:34:41 +0800 |
| commit | 111d33d7aced317605fd88c74b01ffbc6ab266c7 (patch) | |
| tree | fb1b64e7b4a3f20327b8514baadae6151c1f19e4 /docs/security-considerations.rst | |
| parent | 34df80c502c5e20fda6db1d2152beccdfb3342cc (diff) | |
| download | dexon-solidity-111d33d7aced317605fd88c74b01ffbc6ab266c7.tar.gz dexon-solidity-111d33d7aced317605fd88c74b01ffbc6ab266c7.tar.zst dexon-solidity-111d33d7aced317605fd88c74b01ffbc6ab266c7.zip | |
Rename sha3 to keccak256 in the documentation
Diffstat (limited to 'docs/security-considerations.rst')
| -rw-r--r-- | docs/security-considerations.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/security-considerations.rst b/docs/security-considerations.rst index 3e7695c8..77e1bf08 100644 --- a/docs/security-considerations.rst +++ b/docs/security-considerations.rst @@ -207,7 +207,7 @@ Minor Details You can craft transactions that call a function ``f(uint8 x)`` with a raw byte argument of ``0xff000001`` and with ``0x00000001``. Both are fed to the contract and both will look like the number ``1`` as far as ``x`` is concerned, but ``msg.data`` will - be different, so if you use ``sha3(msg.data)`` for anything, you will get different results. + be different, so if you use ``keccak256(msg.data)`` for anything, you will get different results. *************** Recommendations |