chainId not set in contract calls on Linea Sepolia

[darshankabariya]

Bug: chainId not set → contract calls fail on Linea Sepolia

Summary

waku-network recently moving from sepolia to linea sepolia, all standard nim-web3 contract calls that used to work now fail because the built transaction does not include a chainId. We patched it locally by manually building the call with ethCallWithParams, ethCallWithoutParams but that’s brittle and hard to maintain.

Expected Behavior

let result = await contract.someFunction().call()

Current Workaround

let result = await ethCallWithParams(
  ethRpc = ethRpc,
  functionSignature = "someFunction()",
  params = paddedParam,
  fromAddress = ethRpc.defaultAccount,
  toAddress = contractAddress,
  chainId = chainId,
)

Impact

• Breaks the normal contract.fn().call() path.
• Forces us to manually craft transactions/calls.
• Adds complexity & duplication across the codebase (e.g., RLN-related code paths).