Unsupported opcodes in solidity >=0.8.24 prevent QuantAMM contracts from deploying on Arbitrum
Summary
QuantAMM use Solidity version >=0.8.24, which includes opcodes that are not supported on Arbitrum, specifically the BLOBBASEFEE opcode. This incompatibility could prevent contract deployment on Arbitrum One, one of QuantAMM's target chains.
Finding Description
QuantAMM plans to deploy on multiple chains including Ethereum Mainnet, Optimism, Arbitrum One, and Base. However, the contracts use:
This version introduces opcodes like BLOBBASEFEE that are not supported on Arbitrum One according to evmdiff.com. This creates a deployment blocker for Arbitrum One integration.
Impact
QuantAMM contracts cannot be deployed on Arbitrum One due to unsupported opcodes
Arbitrum is one of the major L2s with significant TVL and user base. Not being able to deploy there would mean missing out on a large market
The team would need to revise and retest contracts with a lower Solidity version, causing launch delays
Recommendation
Downgrade the Solidity version to a compatible one that's supported across all target chains. For example:
or alternatively:
Create separate contract versions for different chains
Or remove Arbitrum from the initial launch targets until they support the required opcodes
Lead Judging Commences
Informational or Gas / Admin is trusted / Pool creation is trusted / User mistake / Suppositions
Please read the CodeHawks documentation to know which submissions are valid. If you disagree, provide a coded PoC and explain the real likelyhood and the detailed impact on the mainnet without any supposition (if, it could, etc) to prove your point.
Prize pool breakdown
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.