Issue description
If the address of an encoded contract is not verified on the explorer, you cannot interact with it through a contract call. In this case, the contract's methods will not be shown or correctly appear on the Policy rule or via Manage contract (if you purchased the Tokenization feature). Learn more about Policy rules for specific contract call methods.
Resolution
You must verify the contract address over the scanner as explained below.
Find the relevant contract on the blockchain explorer
Each blockchain has a scanner, so enter the one where the mentioned contract is deployed. Enter its address, open it, and navigate to the Contract tab.
Verify the contract
Note:
The contract might be a proxy. Look for the Read/Write as Proxy tabs under the Contract tab.
- If it is indeed a proxy contract, go to the More Options dropdown on the right side of the contract and select Is this a proxy?
- Select Verify.
- If it is not a proxy contract, and you do not see a “V” sign under the Contract tab, you must verify it by selecting Verify and Publish as shown below:
When the contract is verified, try interacting with it. If you still experience any issues with the contract, contact Fireblocks Support to manually scrape it or upload it privately (if you have purchased tokenization, you can follow this article to manually upload it).
Note:
The first interaction might fail, but Fireblocks scrapes the ABI, so the next interaction should be successful.