[Core Protocol] SELFDESTRUCT traces in pre-bedrock optimism

[tmcgroul]

Did you check the documentation?

• Yes

Did you read the specs?

• Yes
• No

Did you check for duplicate questions?

• Yes

Issue Description

i noticed that SELFDESTRUCT traces are different in pre-bedrock and bedrock network parts:

pre-bedrock

https://optimistic.etherscan.io/tx/0xe1a45b1956659510400df24d57a068f10303e276b9f2ce97d5cff5f18a034b57
{"type":"SELFDESTRUCT"}

bedrock

https://optimistic.etherscan.io/tx/0x9a967f5cec4561d67c6d1c10b39c55a14350e0958e3ec63139cb035623a990e3
{"from":"0x168990be1124f14e1f3a0d2a6be6ea29bc132590","gas":"0x0","gasUsed":"0x0","to":"0x0000000000000000000000000000000000000000","input":"0x","value":"0x0","type":"SELFDESTRUCT"}

so i would like to know how could i annotate missing fields for the first case. is it correct to map fields like that:
value: '0x0' - hardcoded value
to: '0x0000000000000000000000000000000000000000' - hardcoded value
from: transaction.to - i assume that transaction destination is a target for self-destruction

Additional Information

No response

Feedback

No response