[OP Stack Deployment] Non-EIP-155 transactions on Optimism-Sepolia

[ScreamingHawk]

Issue Description

I'm trying to deploy a contract with a pre-EIP-155 transaction on Optimism Sepolia. The request is failing with invalid sender. I suspect this is due to the node requiring the chain id in the encoding (EIP-155 compliance). Unfortunately in order to have a consistent address across chains, I need to send a transaction without EIP-155 enabled.

Note: This issue doesn't happen on other Optimism networks. It's only related to Sepolia

Additional Information

Details of transaction here: https://gist.github.com/Agusx1211/de05dabf918d448d315aa018e2572031

[sbvegan]

What RPC endpoint are you submitting it to? If its your own node, you need to specify --rpc.allow-unprotected-txs=true

[ScreamingHawk]

Gotcha. Same error when using only eth_sendRawTransaction.

(body="{\"jsonrpc\":\"2.0\",\"error\":{\"code\":-32000,\"message\":\"invalid sender\"},\"id\":42}\n", error={"code":-32000}, requestBody="{\"method\":\"eth_sendRawTransaction\",\"params\":[\"...\"],\"id\":42,\"jsonrpc\":\"2.0\"}", requestMethod="POST", url="https://sepolia-sequencer.optimism.io", code=SERVER_ERROR, version=web/5.7.1)

[sbvegan]

I'll get back to you on this next week when the devinfra engineer who would implement this will be back in office. It should be a quick fix for him, but I don't want to make any promises on his behalf.

[sbvegan]

Hey @ScreamingHawk, sorry for the delay, this is likely to land early next week.

[sbvegan]

Alright! @ScreamingHawk sorry for the delay. Pre-EIP-155 transactions are enabled for OP Sepolia and will be available on OP Mainnet by the end of the week.

[ScreamingHawk]

Sweet it's all working for me now. Thanks so much!

[github-actions[bot]]

Hey @ScreamingHawk, 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.