Ensure recipient address on l1 and l2 transactions are non zero
in the deposit tokens functions on l1 and l2, there should be a check to confirm that the recipient on the other chain is non zero. it's a trivial fix that could prevent loss of nfts
loss of nft if you bridge to the zero address from l2 to l1. since you cant cancel l2 to l1 txs
stress of cancellation if you bridge from l1 to l2
add this to the deposit_tokens
function in bridge.cairo
add this to the depositTokens
function in Bridge.sol
Please, do not suppose impacts, think about the real impact of the bug and check the CodeHawks documentation to confirm: https://docs.codehawks.com/hawks-auditors/how-to-determine-a-finding-validity A PoC always helps to understand the real impact possible.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.