ALTUVesting Static Analysis Findings

ALU-01S: Illegible Numeric Value Representations

Type	Severity	Location
Code Style		ALTUVesting.sol: • I-1: L23 • I-2: L24

Description:

The linked representations of numeric literals are sub-optimally represented decreasing the legibility of the codebase.

Example:

Copy
23uint256 private constant BPS_DENOM = 10_000;

Recommendation:

To properly illustrate each 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).

ALU-02S: Multiple Top-Level Declarations

Type	Severity	Location
Code Style		ALTUVesting.sol: • I-1: L8 • I-2: L14

Description:

The referenced file contains multiple top-level declarations that decrease the legibility of the codebase.

Example:

Copy
8interface IALTU {
9    function mint(address to, uint256 amount) external;
10    function transferUnlockTime() external view returns (uint64);
11    function unlockTimeSet() external view returns (bool);
12}
13
14contract ALTURewardVestingController is AccessControl, ReentrancyGuard {

Recommendation:

We advise all highlighted top-level declarations to be split into their respective code files, avoiding unnecessary imports as well as increasing the legibility of the codebase.