SwapPair Static Analysis Findings

SPR-01S: Illegible Numeric Value Representation

Type	Severity	Location
Code Style		SwapPair.sol:L367, L368, L425

Description:

The linked representation of a numeric literal is sub-optimally represented decreasing the legibility of the codebase.

Example:

Copy
367if (amount0In > 0) _update0(amount0In * fee / 1e6); // accrue fees for token0 and move them out of pool

Recommendation:

To properly illustrate the value's purpose, we advise the following guidelines to be followed. For values meant to depict fractions with a base of 1e18, we advise fractions to be utilized directly (i.e. 1e17 becomes 0.1e18) as they are supported. For values meant to represent a percentage base, we advise each value to utilize the underscore (_) separator to discern the percentage decimal (i.e. 10000 becomes 100_00, 300 becomes 3_00 and so on). Finally, for large numeric values we simply advise the underscore character to be utilized again to represent them (i.e. 1000000 becomes 1_000_000).

Alleviation:

The Xcaliswap team has NOT made any changes in the source code for this issue.

SPR-02S: Inexistent Visibility Specifiers

Type	Severity	Location
Code Style		SwapPair.sol:L37, L48

Description:

The linked variables have no visibility specifier explicitly set.

Example:

Copy
37address immutable factory;

Recommendation:

We advise them to be set so to avoid potential compilation discrepancies in the future as the current behaviour is for the compiler to assign one automatically which may deviate between pragma versions.

Alleviation:

The Xcaliswap team has marked the factory variable as public.