I cloned the https://github.com/OpenZeppelin/workshops/tree/master/01-defender-meta-txs and deployed the contracts on kovan just for testing purposes but I keep getting this error down here in the autotask


invalid BigNumber value (argument="value", value=undefined, code=INVALID_ARGUMENT, version=bignumber/5.6.2)

2022-06-28T18:19:22.679Z INFO Relaying {
value: 0,
gas: 1000000,
nonce: '1',
to: '0x02f50082297c86E8c4D878D4c7dc68B236D3616c',
from: '0x84E5B4cf1B91EC15dD34E097B403B07175f72d35',
data: '0xf2c298be000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000044d617a6900000000000000000000000000000000000000000000000000000000'
2022-06-28T18:19:26.459Z ERROR Invoke Error {"errorType":"Error","errorMessage":"invalid BigNumber value (argument="value", value=undefined, code=INVALID_ARGUMENT, version=bignumber/5.6.2)","code":"INVALID_ARGUMENT","reason":"invalid BigNumber value","argument":"value","stack":["Error: invalid BigNumber value (argument="value", value=undefined, code=INVALID_ARGUMENT, version=bignumber/5.6.2)"," at Logger.makeError (/opt/nodejs/node_modules/@ethersproject/logger/lib/index.js:233:21)"," at Logger.throwError (/opt/nodejs/node_modules/@ethersproject/logger/lib/index.js:242:20)"," at Logger.throwArgumentError (/opt/nodejs/node_modules/@ethersproject/logger/lib/index.js:245:21)"," at Function.BigNumber.from (/opt/nodejs/node_modules/@ethersproject/bignumber/lib/bignumber.js:239:23)"," at DefenderRelaySigner.sendTransaction (/opt/nodejs/node_modules/defender-relay-client/lib/ethers/signer.js:88:45)"," at processTicksAndRejections (internal/process/task_queues.js:97:5)"]}
END RequestId: 01339f85-07b3-49f6-b445-74040d7a48c3

Hi @Jeon316upzx, apologies for the inconveniences.

This is a known issue. We recently added support for EIP1559 transactions under compatible relayers. Any relayer you created on a compatible after Thursday, June 23rd is flagged to send EIP1559 transactions whenever no other gas pricing parameter is provided.

This is fixed in the client after version 1.25.0 but our Autotask environment has not been updated yet, we're planning to release a fix as soon as possible but you'll require to delete and create your Autotask once we ship the fix.

In the meanwhile, you can disable EIP1559 on your relayer by going to Policies > EIP1559 so your relayer sends legacy transactions and the behavior is kept as expected.

Sharing some ss of how to get to the policy.


Thank you for the help!

1 Like


We have deployed a new version of the Defender that includes the latest packages needed for invoking EIP1559 transactions from an Autotask.

The Fix mentioned above is not required anymore.

In order to make it work you would need to recreate Autotask(create new one with needed logic).

Note: We are working on a solution for updating Autotask dependencies without recreating them.


1 Like