Open michaelkaplan13 opened 1 year ago
FWIW, I also get the same error when going through example 2 on the second step to send tokens to the BasicMessageReceiver
instance that was deployed on the destination chain.
OK, we may need to update the docs on this one.
To mimic the current mainnet setup, LINK is supported as FeeTokenOnly
, i.e. it isn't available for bridging, and that's why it's failing. You can test with the CCIP-BnM
(burn & mint) token (0xD21341536c5cF5EB1bcb58f6723cE26e8D8E90e4 on Avax Fuji), which has public drip mint function and should be available for testing and bridging.
@andrevmatos, thanks. I was able to run the example successfully using the CCIP-BnM
token now.
I was attempting to go through the workflow for example, documented here.
I have a wallet (0xF759607ffee4B5482492927E51D3b7820DE4189d) that has native token balances on both Fuji and Sepolia, and also has LINK on each of those chains, and set the proper variables in the
.env
file.When I run the script however, I get this error:
The error is coming from the
getPoolBySourceToken
call to this contract. Looks like it could be an "Unsupport Token" error, but I checked that0x0b9d5D9136855f6FEc3c0993feE6E9CE8a297846
is the correct LINK token address for Fuji.Any idea why I'm hitting this error?