Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
N
nebula
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
exchain
nebula
Commits
5bbe7170
Unverified
Commit
5bbe7170
authored
Jun 20, 2024
by
Marcel
Committed by
GitHub
Jun 20, 2024
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
remove dead code (#10939)
parent
a3eb9c31
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
0 additions
and
55 deletions
+0
-55
Makefile
op-chain-ops/Makefile
+0
-3
README.md
op-chain-ops/README.md
+0
-52
No files found.
op-chain-ops/Makefile
View file @
5bbe7170
...
...
@@ -3,9 +3,6 @@ ifeq ($(shell uname),Darwin)
FUZZLDFLAGS
:=
-ldflags
=
-extldflags
=
-Wl
,-ld_classic
endif
op-version-check
:
go build
-o
./bin/op-version-check ./cmd/op-version-check/main.go
ecotone-scalar
:
go build
-o
./bin/ecotone-scalar ./cmd/ecotone-scalar/main.go
...
...
op-chain-ops/README.md
deleted
100644 → 0
View file @
a3eb9c31
# op-chain-ops
This package contains utilities for working with chain state.
## op-version-check
A CLI tool for determining which contract versions are deployed for
chains in a superchain. It will output a JSON file that contains a
list of each chain's versions. It is assumed that the implementations
that are being checked have already been deployed and their contract
addresses exist inside of the
`superchain-registry`
repository. It is
also assumed that the semantic version file in the
`superchain-registry`
has been updated. The tool will output the semantic versioning to
determine which contract versions are deployed.
### Configuration
#### L1 RPC URL
The L1 RPC URL is used to determine which superchain to target. All
L2s that are not based on top of the L1 chain that corresponds to the
L1 RPC URL are filtered out from being checked. It also is used to
double check that the data in the
`superchain-registry`
is correct.
#### Chain IDs
A list of L2 chain IDs can be passed that will be used to filter which
L2 chains will have their versions checked. Omitting this argument will
result in all chains in the superchain being considered.
#### Deploy Config
The path to the
`deploy-config`
directory in the contracts package.
Since multiple L2 networks may be considered in the check, the
`deploy-config`
directory must be passed and then the particular deploy config files will
be read out of the directory as needed.
#### Outfile
The file that the versions should be written to. If omitted, the file
will be written to stdout
#### Usage
It can be built and run using the
[
Makefile
](
./Makefile
)
`op-version-check`
target. Run
`make op-version-check`
to create a binary in
[
./bin/op-version-check
](
./bin/op-version-check
)
that can be executed, optionally providing the
`--l1-rpc-url`
,
`--chain-ids`
,
`--superchain-target`
, and
`--outfile`
flags.
```
sh
./bin/op-version-check
```
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment