waizkhan7 / smartmuv Goto Github PK

In reach_analysis function, code lines of input code are analyzed in the wrong order if there are more than one possible execution paths.

An error occurs in the state extraction of a struct variable if the type of the member variable is a mapping type.

In slot calculation, "immutable" variables are added in variables for extraction, but they should be treated as "constant" variables as their value is stored in the contract's bytecode.

Extraction fails for variables dynamic array of user-defined variable in a mapping like mapping(address => Stake[]) public userStakes;

Key backtracking fails to backtrack key source if the expression type is a "tuple expression".

(address token0, address token1) = tokenA < tokenB ? (tokenA, tokenB) : (tokenB, tokenA);

Before extracting state variable from the contract AST, SmartMuv should first check and resolve the "diamond inheritance problem". Otherwise variable declaration sequence and hence slot layout can be affected.

An error occurs while converting "bytes" type mapping key to "int" for slot calculation.

State Extraction fails if the key type of a mapping variable is a string type.

SmartMuv misses marking mapping key node, if new value is added to mapping in the following way:

Adapter storage adapter = adapters[aggregatorId];

aggregatorId must be marked in this case.