The mapping with users' tokens IDs is not updated when a token is minted through the bridge.
Although the variable KittyConnect.sol::s_ownerToCatsTokenId
is updated whenever a user mints or bridges an NFT, it remains stagnant when receiving NFTs from another chain.
When users bridge their NFTs, the mapping is solely updated in the source chain. Consequently, users are restricted from bridging a number of tokens equal to the native minted tokens minus the total minted using the bridge. This limitation arises because the function KittyConnect.sol::bridgeNftToAnotherChain()
throws an error due to the empty array. Refer to the example below for clarification.
Add the following to the current test suite and import the helper contract stdError
:
Manual review.
Add the following to KittyConnect.sol::mintBridgedNFT()
:
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.