[OP Stack Deployment] Withdrawal from l2 to l1(sepolia network) #853
Replies: 2 comments 8 replies
-
|
please read your OptimismPortalProxy contract method |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/ethereum-optimism/optimism/tree/develop/kurtosis-devnet |
Beta Was this translation helpful? Give feedback.
-
|
Can you give me more details, thanks in advance? After studying the code, I found a link to another repository where smart contracts are deployed. |
Beta Was this translation helpful? Give feedback.
-
|
The image location of the op-deployer they use is different. The local image should be used in the link I mentioned. This is why I think it is more convenient to modify the op-deployer code to build the iamge. but i haven't tried |
Beta Was this translation helpful? Give feedback.
-
I think its not need. Because then start kurkures scripts one of step build op-deployer. its my changes for op-deployer index 1c7bbbfc9..6fe89663f 100644
--- a/kurtosis-devnet/simple.yaml
+++ b/kurtosis-devnet/simple.yaml
@@ -69,6 +69,7 @@ ethereum_package:
participants:
- el_type: geth
cl_type: teku
+ cl_image: "consensys/teku:25.4.0"
network_params:
preset: minimal
genesis_delay: 5
diff --git a/op-deployer/pkg/deployer/standard/standard.go b/op-deployer/pkg/deployer/standard/standard.go
index 9149544c3..9040d6e68 100644
--- a/op-deployer/pkg/deployer/standard/standard.go
+++ b/op-deployer/pkg/deployer/standard/standard.go
@@ -20,17 +20,17 @@ const (
GasLimit uint64 = 60_000_000
BasefeeScalar uint32 = 1368
BlobBaseFeeScalar uint32 = 801949
- WithdrawalDelaySeconds uint64 = 302400
+ WithdrawalDelaySeconds uint64 = 30240
MinProposalSizeBytes uint64 = 126000
- ChallengePeriodSeconds uint64 = 86400
+ ChallengePeriodSeconds uint64 = 8640
ProofMaturityDelaySeconds uint64 = 604800
- DisputeGameFinalityDelaySeconds uint64 = 302400
+ DisputeGameFinalityDelaySeconds uint64 = 30240
MIPSVersion uint64 = 2
DisputeGameType uint32 = 1 // PERMISSIONED game type
DisputeMaxGameDepth uint64 = 73
DisputeSplitDepth uint64 = 30
- DisputeClockExtension uint64 = 10800
- DisputeMaxClockDuration uint64 = 302400
+ DisputeClockExtension uint64 = 1080
+ DisputeMaxClockDuration uint64 = 30240
Eip1559DenominatorCanyon uint64 = 250
Eip1559Denominator uint64 = 50
Eip1559Elasticity uint64 = 6
diff --git a/op-deployer/pkg/deployer/state/deploy_config.go b/op-deployer/pkg/deployer/state/deploy_config.go
index 2b5192694..f0ab5bff9 100644
--- a/op-deployer/pkg/deployer/state/deploy_config.go
+++ b/op-deployer/pkg/deployer/state/deploy_config.go
@@ -109,11 +109,11 @@ func CombineDeployConfig(intent *Intent, chainIntent *ChainIntent, state *State,
},
FaultProofDeployConfig: genesis.FaultProofDeployConfig{
UseFaultProofs: true,
- FaultGameWithdrawalDelay: 604800,
+ FaultGameWithdrawalDelay: 60480,
PreimageOracleMinProposalSize: 126000,
- PreimageOracleChallengePeriod: 86400,
- ProofMaturityDelaySeconds: 604800,
- DisputeGameFinalityDelaySeconds: 302400,
+ PreimageOracleChallengePeriod: 8640,
+ ProofMaturityDelaySeconds: 60480,
+ DisputeGameFinalityDelaySeconds: 30240,
},
}
and result is And even after these changes the release time is still 7 days |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks. Its work |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
Launched the network according to the instructions using op-deployer. From l1 -> l2 the output works. But from l2 -> l1 it does not work. There is no information in the logs. In the documentation I found the output time is 7 days.
op-challenger works correctly.
The screenshot shows resolve claim Credit and close
Events:
op-challenger see all games
I also launched op-dispute-mon and found an error in the logs
Logs
Logs op-challenger
op-dispute-mon
Additional Information
The network was deployed with the help of documentation
https://github.com/ethereum-optimism/developers/discussions/17#discussioncomment-12606204
All services (op-geth,op-node,op-challenger,op-proposer)was build from source using tag v1.13.0
Feedback
It would be nice if there was documentation on deploying op-challenger
Beta Was this translation helpful? Give feedback.
All reactions