You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're trying to get the token address on the Orbit side, but we're using parentChainPublicClient instead of orbitChainWalletClient
Result is reading Orbit router address on the parent chain:
Deploying contract ChildToParentRouter...
error: Uncaught ContractFunctionExecutionError: The contract function "calculateL2TokenAddress" returned no data ("0x").
This could be due to any of the following:
- The contract does not have the function "calculateL2TokenAddress",
- The parameters passed to the contract function may be invalid, or
- The address is not a contract.
Contract Call:
address: 0x0a1f68F439288729f3cc9F0ca6EeA203393Eb57F
function: calculateL2TokenAddress(address)
args: (0x6aD2d2C22Bb58eA94Be18Cff11EF67e8bb97B652)
Docs: https://viem.sh/docs/contract/readContract
Version: [email protected]
at getContractError (file:///deno-dir/npm/registry.npmjs.org/viem/2.21.54/_esm/utils/errors/getContractError.js:26:12)
at readContract (file:///deno-dir/npm/registry.npmjs.org/viem/2.21.54/_esm/actions/public/readContract.js:58:15)
at eventLoopTick (ext:core/01_core.js:182:7)
at async feeRouterDeployChildToParentRewardRouter (file:///deno-dir/npm/registry.npmjs.org/@arbitrum/orbit-sdk/0.21.3/dist/feeRouterDeployChildToParentRewardRouter.js:81:40)
at async main (file:///app/setupAEPFeeRouterCustomGas.ts:129:5)
Caused by: ContractFunctionZeroDataError: The contract function "calculateL2TokenAddress" returned no data ("0x")
The text was updated successfully, but these errors were encountered:
In this line:
arbitrum-orbit-sdk/src/feeRouterDeployChildToParentRewardRouter.ts
Line 125 in d6ccb3b
We're trying to get the token address on the Orbit side, but we're using
parentChainPublicClient
instead oforbitChainWalletClient
Result is reading Orbit router address on the parent chain:
The text was updated successfully, but these errors were encountered: