Start optimism network on old ethereum local fork ( pre bedrock)

[artificialintelligence4all]

Are you running the most up to date node software?

• Yes

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

Hi, i Ve a fork of ethereum (pre bedrock) that we use internally for development , we want to access to optimist network to Better understand l2 layers and help the development.
How can we start a local optimism node that will get the data from the local l1 and comunicate to our L1. Any hints?
Basically our simple porpose is to pass ETH from an our account on L1 to Layer2 perform a swap into a token that is already present in some pool and get back this token through the bridge. We can/want fully control the layer2 but the layer1 continus to work as the real ethereum.

Thanks

Steps to Reproduce

• L1 ethereum fork of march 2023

Which component is affected?

• op-geth
• op-node
• Other

Expected vs. Actual Behavior

we try to create/align a layer2 with our layer1 pre-bedrock fork

Environment Details

Ubuntu 22.04

Protocol Information

L1 chain fork of ethereum pre bedrock upgrade

Node Logs

No response

Troubleshooting Attempts

No response

Additional Information

No response

Feedback

No response

[Chomtana]

You means you want to deploy OP stack on ETH POW right?

You might need to deploy OP stack old version before ETH beacon node merge happen

[artificialintelligence4all]

Hi,

we've fork after the ETH fork of ETH POW, so our interal fork is based on ETH POS but before the bedrock upgrade of optimism.
i've read all the data of all the old layer2 op-mainnet with the legacy repository of optimism, now i want to resume this old implementation and resume optimism in our enviroment, using the old bridge but i see that the sequencer and the proposer seems blocked on specific addresses. Is it possible to force some transactions from directly the layer 1 even if the sequencer and the proposer are stopped?

Thanks

[opfocus]

https://github.com/ethereum-optimism/stack-docs/blob/main/src/docs/security/forced-withdrawal.md
I think this part of the content may be before the bedrock upgrade

[artificialintelligence4all]

https://github.com/ethereum-optimism/stack-docs/blob/main/src/docs/security/forced-withdrawal.md I think this part of the content may be before the bedrock upgrade

i've see that but i think it couldn't work because the layer 1 bridge check the state of scc that cannot be updated because there is the following line of code :

require(
IBondManager(resolve("BondManager")).isCollateralized(msg.sender),
"Proposer does not have enough collateral posted"
);

but doesn't really check if the proposer is collateralized but only checks this:

function isCollateralized(address _who) public view returns (bool) {
// Only authenticate sequencer to submit state root batches.
return _who == resolve("OVM_Proposer");
}

https://github.com/ethereum-optimism/optimism-legacy/blob/develop/packages/contracts/contracts/L1/rollup/StateCommitmentChain.sol

Maybe i miss something or am i correct?

Thanks

[opfocus]

This contract may not have been used before the bedrock upgrade. Please try to deploy and test