Internal Fireblocks error appears with the Fireblocks Web3 SDK.
This is the error that show after send the multicall tx using sepolia testnet.
I saw that someone had the same error using the RSK testnet: Error: Fireblocks transaction {transactionID} was not completed successfully. Final Status: FAILED (UNKNOWN_ERROR)
Error: Fireblocks transaction 40635336-a96f-46c7-9ba4-91c456aaa3bb was not completed successfully. Final Status: FAILED (UNKNOWN_ERROR)
at FireblocksWeb3Provider.createTransaction (/Users/cancuethereum/Projects/myproject/myproject-back/node_modules/@fireblocks/fireblocks-web3-provider/src/provider.ts:625:18)
at async FireblocksWeb3Provider.createContractCall (/Users/cancuethereum/Projects/myproject/myproject-back/node_modules/@fireblocks/fireblocks-web3-provider/src/provider.ts:547:39)
at async /Users/cancuethereum/Projects/myproject/myproject-back/node_modules/@fireblocks/fireblocks-web3-provider/src/provider.ts:308:26 {
code: -32603,
data: undefined,
payload: undefined
}
Tenderly:
fireblocks-web3-provider:error Simulate the failed transaction on Tenderly: https://dashboard.tenderly.co/simulator/new?gas=77412&from=0xff6ce5958598f81188c943f820ade98fcd6d8641&contractAddress=0x709ce4cb4b6c2a03a4f938ba8d198910e44c11ff&rawFunctionInput=0xd505accf000000000000000000000000ff6ce5958598f81188c943f820ade98fcd6d8641000000000000000000000000709ce4cb4b6c2a03a4f938ba8d198910e44c11ff00000000000000000000000000000000000000000000000000000000000000640000000000000000000000000000000000000000000000000000000065c57058000000000000000000000000000000000000000000000000000000000000001c20442930a8236c19caec39fbf2799549ea39f21462ff6790e556d1a6bd1a86411327d28dbd448d7997bb1d6f77c0115cc60fe1c2dcaf8b8f080f466936a7cdd3&network=11155111
Fireblocks tx id: 40635336-a96f-46c7-9ba4-91c456aaa3bb