build(deps): Upgrade reth version 1.3.8 => 1.3.12 and alloy version 0.13 => 0.15#163
build(deps): Upgrade reth version 1.3.8 => 1.3.12 and alloy version 0.13 => 0.15#163RomanHodulak merged 4 commits intomainfrom
reth version 1.3.8 => 1.3.12 and alloy version 0.13 => 0.15#163Conversation
RomanHodulak
requested review from
Rjected,
fgimenez,
mattsse and
onbjerg
as code owners
…ersion `0.13` => `0.15`
The Isthmus maps to Prague hardfork, previously activated by the prague timestamp only
mattsse
left a comment
mattsse
left a comment
There was a problem hiding this comment.
nice, the diff is actually not too bad
I believe the failing e2e is now just because of some isthmus specific thing
likely just need to update kurtosis I think
will check
| REPLICA_EL_PORT=$(curl "http://127.0.0.1:9779/api/enclaves/$ENCLAVE_ID/services" | jq '."op-el-2-op-reth-op-node-op-kurtosis".public_ports.rpc.number') | ||
| SEQUENCER_EL_PORT=$(curl "http://127.0.0.1:9779/api/enclaves/$ENCLAVE_ID/services" | jq '."op-el-41144114-1-op-reth-op-node-op-kurtosis".public_ports.rpc.number') | ||
| curl "http://127.0.0.1:9779/api/enclaves/$ENCLAVE_ID/services" | jq '.' | ||
| REPLICA_EL_PORT=$(curl "http://127.0.0.1:9779/api/enclaves/$ENCLAVE_ID/services" | jq '."op-el-41144114-2-op-reth-op-node-op-kurtosis".public_ports.rpc.number') |
There was a problem hiding this comment.
curios, where do we get this identifier op-el-41144114 from
similar thing here
and not obvious where this is coming from
maybe @fgimenez knows?
There was a problem hiding this comment.
maybe @fgimenez knows?
@mattsse sorry for the late response, yep it comes from the network id as defined in kurtosis args file
Line 40 in 876b574
the id used in reth comes from the defaults in optimism kurtosis package https://github.com/ethpandaops/optimism-package/blob/e1d26204bcdb3f5bebc59a76b5f8aba566bcdb13/src/package_io/input_parser.star#L543
4 participants
Closes #162
Bumps all the
rethandalloydependencies to latest.Note the change in genesis configuration.