Op-Conductor Localnet #267
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
area: bfg
ClaytonNorthey92
force-pushed
the
clayton/op-conductor
branch
3 times, most recently
from
c05e15a
to
6957f44
Compare
github-actions
bot
added
the
area: ci
ClaytonNorthey92
force-pushed
the
clayton/op-conductor
branch
from
de75ea4
to
4130b97
Compare
ClaytonNorthey92
force-pushed
the
clayton/op-conductor
branch
from
4130b97
to
6b382b2
Compare
ClaytonNorthey92
requested review from
jcvernaleo,
max-sanchez,
marcopeereboom and
joshuasing
|
Needs a rebase. |
ClaytonNorthey92
force-pushed
the
clayton/op-conductor
branch
from
6b382b2
to
56f415a
Compare
|
hang tight on this one, localnet test is failing after rebase, looking into it 🧑💻 |
ClaytonNorthey92
force-pushed
the
clayton/op-conductor
branch
from
56f415a
to
36fdfb6
Compare
marcopeereboom
approved these changes
Oct 15, 2024
joshuasing
approved these changes
Oct 24, 2024
set up 3 sequencers, each controlled by op-conductors p2p'd via raft consensus update localnet tests CI to kill 1 op-node, another should take over sequencing decrease the initial btc blocks because 3000 is excessive (this will need testing over time) updated l2 block time to 2 seconds, instead of 1, it's easier to follow this way IMO
ClaytonNorthey92
force-pushed
the
clayton/op-conductor
branch
from
36fdfb6
to
a2c63e8
Compare
web3cryptoguy
pushed a commit
to web3cryptoguy/heminetwork
that referenced
this pull request
Nov 1, 2024
* prove out op-conductor in localnet set up 3 sequencers, each controlled by op-conductors p2p'd via raft consensus update localnet tests CI to kill 1 op-node, another should take over sequencing decrease the initial btc blocks because 3000 is excessive (this will need testing over time) updated l2 block time to 2 seconds, instead of 1, it's easier to follow this way IMO * test fixes * remove references of op-geth-l1 in docker-compose
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
set up 3 sequencers, each controlled by op-conductors p2p'd via raft consensus
update localnet tests CI to kill 1 op-node, another should take over sequencing
decrease the initial btc blocks because 3000 is excessive (this will need testing over time)
updated l2 block time to 2 seconds, instead of 1, it's easier to follow this way IMO
depends on hemilabs/op-geth#10
Changes
(Same as summary)