From 9e58a568a936d83bf59ec9d2e7cc7e26a247e411 Mon Sep 17 00:00:00 2001 From: Harikrishnan Mulackal Date: Mon, 8 Feb 2021 14:30:09 +0100 Subject: [PATCH] Fixed links in Docs --- docs/security-considerations.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/security-considerations.rst b/docs/security-considerations.rst index d8dd645f6..54d4e9015 100644 --- a/docs/security-considerations.rst +++ b/docs/security-considerations.rst @@ -187,7 +187,7 @@ Call Stack Depth External function calls can fail any time because they exceed the maximum call stack size limit 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. Note that, since [Tangerine Whistle](https://eips.ethereum.org/EIPS/eip-608) hardfork, the [63/64 rule](https://eips.ethereum.org/EIPS/eip-150) makes call stack depth attack impractical. Also note that the call stack and the expression stack are unrelated, even though both have a size limit of 1024 stack slots. +before they interact with your contract. Note that, since `Tangerine Whistle `_ hardfork, the `63/64 rule `_ makes call stack depth attack impractical. Also note that the call stack and the expression stack are unrelated, even though both have a size limit of 1024 stack slots. Note that ``.send()`` does **not** throw an exception if the call stack is depleted but rather returns ``false`` in that case. The low-level functions