Pragma isn't specified correctly which can lead to nonfunction/damaged contract when deployed on Arbitrum
Summary
Pragma has been set to ^0.8.0 allowing the contracts to be compiled with any 0.8.x compiler. The problem with this is that Arbitrum is NOT compatible with 0.8.20 and newer. Contracts compiled with those versions will result in a nonfunctional or potentially damaged version that won't behave as expected. The default behavior of compiler would be to use the newest version which would mean by defualt it will be compiled with the 0.8.20 version which will produce broken code.
Vulnerability Detail
See summary
Impact
Damaged or nonfunctional contracts when deployed on Arbitrum
0x52
medium
Pragma isn't specified correctly which can lead to nonfunction/damaged contract when deployed on Arbitrum
Summary
Pragma has been set to ^0.8.0 allowing the contracts to be compiled with any 0.8.x compiler. The problem with this is that Arbitrum is NOT compatible with 0.8.20 and newer. Contracts compiled with those versions will result in a nonfunctional or potentially damaged version that won't behave as expected. The default behavior of compiler would be to use the newest version which would mean by defualt it will be compiled with the 0.8.20 version which will produce broken code.
Vulnerability Detail
See summary
Impact
Damaged or nonfunctional contracts when deployed on Arbitrum
Code Snippet
TxBuilderExtension.sol#L3
Tool used
Manual Review
Recommendation
Constrain pragma as follows: