Add files via upload

Author: cyberkostyan

Diff for: abi-spec.rst

@@ -1,38 +1,4 @@
 [
-    {
-        "name": "ExpExponentCleanup",
-        "summary": "Using the ** operator with an exponent of type shorter than 256 bits can result in unexpected values.",
-        "description": "Higher order bits in the exponent are not properly cleaned before the EXP opcode is applied if the type of the exponent expression is smaller than 256 bits and not smaller than the type of the base. In that case, the result might be larger than expected if the exponent is assumed to lie within the value range of the type. Literal numbers as exponents are unaffected as are exponents or bases of type uint256.",
-        "fixed": "0.4.25",
-        "severity": "medium/high",
-        "check": {"regex-source": "[^/]\\*\\* *[^/0-9 ]"}
-    },
-    {
-        "name": "EventStructWrongData",
-        "summary": "Using structs in events logged wrong data.",
-        "description": "If a struct is used in an event, the address of the struct is logged instead of the actual data.",
-        "introduced": "0.4.17",
-        "fixed": "0.4.25",
-        "severity": "very low",
-        "check": {"ast-compact-json-path": "$..[?(@.nodeType === 'EventDefinition')]..[?(@.nodeType === 'UserDefinedTypeName' && @.typeDescriptions.typeString.startsWith('struct'))]"}
-    },
-    {
-        "name": "NestedArrayFunctionCallDecoder",
-        "summary": "Calling functions that return multi-dimensional fixed-size arrays can result in memory corruption.",
-        "description": "If Solidity code calls a function that returns a multi-dimensional fixed-size array, array elements are incorrectly interpreted as memory pointers and thus can cause memory corruption if the return values are accessed. Calling functions with multi-dimensional fixed-size arrays is unaffected as is returning fixed-size arrays from function calls. The regular expression only checks if such functions are present, not if they are called, which is required for the contract to be affected.",
-        "introduced": "0.1.4",
-        "fixed": "0.4.22",
-        "severity": "medium",
-        "check": {"regex-source": "returns[^;{]*\\[\\s*[^\\] \\t\\r\\n\\v\\f][^\\]]*\\]\\s*\\[\\s*[^\\] \\t\\r\\n\\v\\f][^\\]]*\\][^{;]*[;{]"}
-    },
-    {
-        "name": "OneOfTwoConstructorsSkipped",
-        "summary": "If a contract has both a new-style constructor (using the constructor keyword) and an old-style constructor (a function with the same name as the contract) at the same time, one of them will be ignored.",
-        "description": "If a contract has both a new-style constructor (using the constructor keyword) and an old-style constructor (a function with the same name as the contract) at the same time, one of them will be ignored. There will be a compiler warning about the old-style constructor, so contracts only using new-style constructors are fine.",
-        "introduced": "0.4.22",
-        "fixed": "0.4.23",
-        "severity": "very low"
-    },
     {
         "name": "ZeroFunctionSelector",
         "summary": "It is possible to craft the name of a function such that it is executed instead of the fallback function in very specific circumstances.",

Diff for: assembly.rst

@@ -56,19 +56,6 @@ conditions
     is an object that can contain a boolean value ``optimizer``, which
     means that the optimizer has to be switched on to enable the bug.
     If no conditions are given, assume that the bug is present.
-check
-    This field contains different checks that report whether the smart contract
-    contains the bug or not. The first type of check are Javascript regular
-    expressions that are to be matched against the source code ("source-regex")
-    if the bug is present.  If there is no match, then the bug is very likely
-    not present. If there is a match, the bug might be present.  For improved
-    accuracy, the checks should be applied to the source code after stripping
-    comments.
-    The second type of check are patterns to be checked on the compact AST of
-    the Solidity program ("ast-compact-json-path"). The specified search query
-    is a `JsonPath <https://github.com/json-path/JsonPath>`_ expression.
-    If at least one path of the Solidity AST matches the query, the bug is
-    likely present.
 
 .. literalinclude:: bugs.json
    :language: js