[Core Protocol] <Feasibility and SOP for Adding Custom Predeploy Contract on OP Stack>

[HaoHaoLifeHack]

Did you check the documentation and specs?

• Yes

Was there anything unclear or missing?

Hi team,

I have a few questions regarding the usage and deployment of Predeploy Contracts on the OP Stack:

1. It is understood that the namespace (addresses starting with 0x42...xxx) for predeploy contracts is almost exclusively populated with Proxy contracts (except for a few non-Proxy designated addresses). Is it feasible to add a custom Predeploy Contract to an already running network?

2. If it is feasible, is there an established standard operating procedure (SOP) for doing so?

3. If adding a custom Predeploy Contract on a live network is not feasible, would it be possible to include a custom predeploy contract with a custom address prior to chain launch? If so, what risks or implications should we be aware of?

Thank you for your guidance.

Did you check for duplicate questions?

• Yes

Similar Questions or Issues Found

No response

Please select the type of request

• Bug Report
• Feature Request

Steps to Reproduce

No response

Expected vs. Actual Behaviour

No response

Software Versions

No response

Operating System

No response

Hardware Resources

No response

Configuration Files, Startup Flags & Environment Variables

No response

Error Messages / Logs

No response

Feature Description

Introduce the ability for network operators to deploy custom predeploy contracts within a live OP Stack network, allowing for enhanced customization without the need for a full network restart.

Purpose and Benefits

No response

Relevant Context or Examples

No response

[opfocus]

There is currently no official guidance on this matter. You can refer to your genesis.json file for reference and give it a try. We will report this issue to the team and see if there is any response.

[joohhnnn]

I believe that adding precompiling contract might result in a fork for your chain. You can refer to these two docs for methods on adding precompiles and modifying predeploys. If you still have any questions after reviewing them, feel free to tag me for further discussion. https://docs.optimism.io/operators/chain-operators/tutorials/adding-precompiles
https://docs.optimism.io/operators/chain-operators/tutorials/modifying-predeploys

[Chomtana]

Process is similar to optimism team introducing a new fork. You need to add a fork version flag (ecotone, etc but in your own name) and set a target timestamp in the future for your chain to fork and activate these new precompiles at that time.