In order for users to bridge their NFTs to another chain, KittyConnect
makes an external call to KittyBridge::bridgeNftWithData
after this function generates and forwards the message to the Router, the Router will attempt to charge a fee from the bridge, but it will no be able to move the tokens because the bridge never approves the Router during the call nor contains a function to do so. This means users will never be able to bridge their tokens.
Users cannot bridge their NFTs as the protocol intends.
Manual review
After the fees to send the message is computed is KittyConect::bridgeNftWithData
, include a call to the approve
method of the LINK token contract to give an allowance to the Router equivalent to the fees to pays.
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.