From 111d33d7aced317605fd88c74b01ffbc6ab266c7 Mon Sep 17 00:00:00 2001 From: Alex Beregszaszi Date: Thu, 6 Oct 2016 13:24:36 +0100 Subject: Rename sha3 to keccak256 in the documentation --- docs/security-considerations.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/security-considerations.rst') 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 -- cgit