Pragma isn't specified correctly which can lead to nonfunctional/damaged contract when deployed on Arbitrum
Summary
It's been relayed in that Beedle is going to be uploaded on optimism and in the future would probably ne uploaded elsewhere, this means that it easily would get deployed on arbitrum, being that both arbitrum and optimism use optimistic roll ups
Vulnerability Detail
Floating pragma is used, allowing the contracts to be compiled with any 0.8.x compiler higher than the specified version. The problem with this is that Arbitrum is NOT compatible with 0.8.20 and newer due to the introduction of a new opcode PUSH0. 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 default it will be compiled with the 0.8.20 version which will produce broken code.
Impact
Damaged or nonfunctional contracts when deployed on Arbitrum.
Tool used
Manual Audit
Recommendation
Constrain pragma could be something as follows:
pragma solidity 0.8.19
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.