wip: update opstack for jovian fork #223
Conversation
|
Is this ready for review? |
@julio4 is this working at the moment? If so then we should merge in main and push this change |
julio4
force-pushed
the
jovian-fix
branch
2 times, most recently
from
8fc17c3 to
0c0d13b
Compare
# Conflicts: # playground/components.go # Conflicts: # playground/components.go
|
Do we have to keep support of enableLatestFork? |
It looks like it would be useful for testing hard forks in the future. Do you want to remove it? |
Agree but I'm not sure how to correctly test activation of jovian here. Both op-node and op-geth should activate jovian at the same timestamp but get Invalid payload attributes err |
|
So the option to set the block number at which the hard fork activates doesn't work? |
It sets correctly the fork time for op-geth and op-node but when reaching it the activation is failing. I didn't spend much time debugging it as it works by activating by default at 0 |
3 participants
No description provided.