[Core Protocol] How is precompile logic disputed in Cannon?

[PaulRBerg]

Did you check the documentation?

• Yes

Did you read the specs?

• Yes
• No

Did you check for duplicate questions?

• Yes

Issue Description

Precompiles are implemented natively in the client software, e.g. in go-ethereum they are implemented here.

How does Cannon (the default Fault Proof VM in OP Stack) work when there is a dispute for a transaction that calls a precompile, e.g. the ecrecover located at address 0x01?

How can the onchain MIPS.sol interpreter re-run precompile logic?

Additional Information

I've read the docs on Fault Proofs:

https://docs.optimism.io/stack/protocol/fault-proofs/overview

Feedback

No response

[opfocus]

https://specs.optimism.io/experimental/fault-proof/index.html#type-6-global-precompile-key This preimage key can be used to avoid running expensive precompile operations in the program.
This may be relevant content, if it doesn't answer your question please ask your question on github for that documentation

[PaulRBerg]

Thank you for sharing that link to the specs. It is indeed relevant.

I have moved this discussion to the specs repository:

ethereum-optimism/specs#211