[Core Protocol] Canceled system transaction (126) ans CALL type STOP

[kchojn]

Issue Description

Gm,
can someone explain to me what happens to these transactions (canceled tx type 126) from an EVM perspective??
Examples:

• https://optimistic.etherscan.io/tx/0x73029ab277d9b96542f76d5076f343ed4d190a6db3ee7f41460e166f5de12921
• https://optimistic.etherscan.io/tx/0xa47277b3d92384e70906bed705723a15c91d9f0fff2fc602824d14ea201801c1

It breaks my whole EVM logic, this is what I get from callTracer:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "from": "0x0000000000000000000000000000000000000000",
    "gas": "0x0",
    "gasUsed": "0x5208",
    "input": "0x",
    "type": "STOP"
  }
}

I use EVM from Ethereumjs and we want to add support for optimism, that's why I'm struggling with it.
Also, I am attaching a screenshot of the EVM debugger:

It would be great to find out what is happening here, I tried to find it in the op gh code, but I was unsuccessful. Thanks!

Additional Information

Edit: it happened only in these blocks:

• 107841237
• 107651229
• 106973772
• 106973322
• 106972986

[sbvegan]

So 126 is a special deposit transaction type and there is special logic around these types of transactions when they fail. For more details on this you can check out the deposit specs.

In one of these cases, it they were trying to deposit 100ETH but they didn't have that much to deposit.

[sbvegan]

Hey @kchojn does this answer your question?

[kchojn]

hey @sbvegan, will confirm in a few days, need to sort out some things. It is possible that I will have some more questions, thanks!

[sbvegan]

Hey @kchojn just checking back in. I'm going to close this for now, but when you're ready we can reopen the discussion.

[github-actions[bot]]

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