[OP Stack Deployment] Invalid Sender

[ckorhonen]

Issue Description

Hey, I have an OP Stack running (Geth + OP Node + OP Batcher + OP Proposer + BlockScout) based on the Getting Started guide.

From the logs, each component appears to be doing its thing, and I'm able to send ETH from my L1 to L2. I’m also getting the expected response when I call eth_chainId.

However, when I attempt to send a TX (CLI, Metamask, JSON RPC) I get this message:

Served eth_sendRawTransaction            conn=192.168.207.1:51808 reqid=5749993899579 duration=219.257851ms err="invalid sender"

I've attempted sending the transaction to the nodes custom domain and via curl to localhost, so don't believe this is a vhosts issue.

Additional Information

No response

[sbvegan]

Hey @ckorhonen,

I'm not sure of the issue here, let me raise this internally and see what we can find out. Can you provide an example of how you're sending your transactions?

[ckorhonen]

I've tried multiple ways - either via Metamask or directly using cURL:

Works:

curl --location 'https://my.node.com' \
--header 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Invalid Sender:

curl --location 'https://my.node.com' \
--header 'Content-Type: application/json' \
--data '{"id":5749993899579,"jsonrpc":"2.0","params":["0x02f8748305713f808459682f008459682f3c8252089473144d7ab3254dd61b20cd9ac507c93913b63168872386f26fc1000080c001a0a763436f96027e1e2e4ff1475ed0c7ae30c0e3dcbfc6e0859e602881b4363d06a00b4014fcc31881790e8235238dbde091a85333317c58e86da0c48ee3d8d813e8"],"method":"eth_sendRawTransaction", "chainId": "356671"}'

[sbvegan]

Hmm a client engineer weighed in with the following when I shared the error you're getting:

The tx signature / address is borked in this case. I wonder if this is the result of using the wrong chain ID

Are you sure "chainId": "356671" is right?

Additional follow up:

Their signer is using the wrong chain ID. I’m pretty convinced when looking through the code that an incorrect chain ID is the only way to cause that error

[ckorhonen]

That was what I was leaning towards, however that is the one I have configured in my genesis/rollup JSON files, and it matches the network ID that I'm providing to Geth. Have I missed a step somewhere?

[sbvegan]

@ckorhonen can you provide your configurations, so we can take a look?

[sbvegan]

I had a client engineer take another look and they're confident your signing software is not using the right chain id, eth_sendRawTransaction is sending an already signed tx.

[sbvegan]

Hey @ckorhonen I'm going to mark this as answered. If you want us to reopen it, lmk!

[github-actions[bot]]

Hey @ckorhonen, We hope your recent question was resolved to your satisfaction. Your feedback is invaluable and helps us improve our support services. Could you spare a moment to fill out a short feedback survey. Thank you for helping us improve our developer community.