search

ithacaxyz / odyssey

A testnet open-source Layer 2 from the future, co-designed with the developer tools stack.
https://www.ithaca.xyz/updates/odyssey
Apache License 2.0
139 stars 29 forks source link

Investigate replica not being able to sync through P2P #53

Open klkvr opened 2 hours ago

klkvr commented 2 hours ago

ref https://github.com/ithacaxyz/odyssey/pull/52

This is mostly related to https://github.com/paradigmxyz/optimism-package

Right now in some cases when launching the kurtosis package replica is not being able to load sequencer address from L1:

t=2024-10-15T19:54:34+0000 lvl=info msg="loaded new runtime config values!" p2p_seq_address=0x0000000000000000000000000000000000000000

This results in CL syncing by reading batches from L1 until the point it tries to load sequencer address again:

t=2024-10-15T20:04:28+0000 lvl=warn msg="no configured p2p sequencer address, ignoring gossiped block" topic=blocksV3 peer=16Uiu2HAmEMg2fcevVBL1fktiLykmPsMmUmpspxtnkXQviLpgXNXx addr=0x196652bb4Fe58A500e1BB42936F70b58C59E1013
t=2024-10-15T20:04:29+0000 lvl=warn msg="no configured p2p sequencer address, ignoring gossiped block" topic=blocksV3 peer=16Uiu2HAmEMg2fcevVBL1fktiLykmPsMmUmpspxtnkXQviLpgXNXx addr=0x196652bb4Fe58A500e1BB42936F70b58C59E1013
t=2024-10-15T20:04:30+0000 lvl=warn msg="no configured p2p sequencer address, ignoring gossiped block" topic=blocksV3 peer=16Uiu2HAmEMg2fcevVBL1fktiLykmPsMmUmpspxtnkXQviLpgXNXx addr=0x196652bb4Fe58A500e1BB42936F70b58C59E1013
t=2024-10-15T20:04:31+0000 lvl=warn msg="no configured p2p sequencer address, ignoring gossiped block" topic=blocksV3 peer=16Uiu2HAmEMg2fcevVBL1fktiLykmPsMmUmpspxtnkXQviLpgXNXx addr=0x196652bb4Fe58A500e1BB42936F70b58C59E1013
t=2024-10-15T20:04:32+0000 lvl=warn msg="no configured p2p sequencer address, ignoring gossiped block" topic=blocksV3 peer=16Uiu2HAmEMg2fcevVBL1fktiLykmPsMmUmpspxtnkXQviLpgXNXx addr=0x196652bb4Fe58A500e1BB42936F70b58C59E1013
t=2024-10-15T20:04:33+0000 lvl=warn msg="no configured p2p sequencer address, ignoring gossiped block" topic=blocksV3 peer=16Uiu2HAmEMg2fcevVBL1fktiLykmPsMmUmpspxtnkXQviLpgXNXx addr=0x196652bb4Fe58A500e1BB42936F70b58C59E1013
t=2024-10-15T20:04:34+0000 lvl=warn msg="no configured p2p sequencer address, ignoring gossiped block" topic=blocksV3 peer=16Uiu2HAmEMg2fcevVBL1fktiLykmPsMmUmpspxtnkXQviLpgXNXx addr=0x196652bb4Fe58A500e1BB42936F70b58C59E1013
t=2024-10-15T20:04:34+0000 lvl=info msg="loaded new runtime config values!" p2p_seq_address=0x196652bb4Fe58A500e1BB42936F70b58C59E1013

Until CL founds a sequencer address the replica's EL is ~100 blocks behind the sequencer resulting in issues during testing

klkvr commented 2 hours ago

I would think that this is some kind of race condition occuring because L2 is being launched before the contracts deployment was completed but it seems that those are exeucted sequentially