The
useAutoBurn
parameter has no effect and the NFT will not be automatically destroyed.fn deposit_tokens(ref self: ContractState,salt: felt252,collection_l2: ContractAddress,owner_l1: EthAddress,token_ids: Span<u256>,use_withdraw_auto: bool,use_deposit_burn_auto: bool,) {function depositTokens(uint256 salt,address collectionL1,snaddress ownerL2,uint256[] calldata ids,bool useAutoBurn)
During the user's cross-chain process, if L2 has issued a cross-chain request, but L1's _enabled is set to false, the user's NFT will be stuck.
The newOwners parameter is not used, and the NFT is not given to the corresponding newOwner.
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.