You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+44-8
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,21 @@ This repository offers Docker configurations for effortlessly running the Opstac
7
7
8
8
Please follow the steps below to get your Verse up and running. If you encounter any issues while building, please refer to the [QA](#frequently-asked-questions) section.
9
9
10
+
## About Versions
11
+
This repository follows semantic versioning with the major version fixed at `v1`(meaning Verse V1). Minor version updates correspond to OPStack protocol upgrades(hardforks). Patch version updates are releases focused on bug fixes and parameter changes. It is strongly recommended to pin to a specific version after git cloning, as tracking the main branch would result in automatic application of upgrades.
Before beginning, ensure that the L1 contract sets have already been deployed, and you possess the necessary configuration files (`addresses.json`, `deploy-config.json`). If not, please refer to the contract sets deployment section in our [technical documentation](https://docs.oasys.games/docs/verse-developer/how-to-build-verse/manual).
24
+
Before beginning, ensure that the L1 contract sets have already been deployed, and you possess the necessary configuration files (`addresses.json`, `deploy-config.json`). If not, please refer to the contract sets deployment section in our [technical documentation](https://docs.oasys.games/docs/category/build-verse).
12
25
13
26
### 1. Prepare Assets and Environment
14
27
#### Place Configuration Files
@@ -33,8 +46,13 @@ cp .env.sample.mainnet .env
33
46
34
47
# Sample for testnet
35
48
cp .env.sample.testnet .env
49
+
50
+
# Sample for private
51
+
cp .env.sample.private .env
36
52
```
37
53
54
+
> *Related project for building a private L2: [oasys-private-l1](https://github.com/oasysgames/oasys-private-l1)*
55
+
38
56
To configure the environment file with addresses sourced from `addresses.json`, use the following commands to extract the required addresses:
Add the block timestamps for L2 upgrades to the `.env` file. These timestamps must be set slightly in the future as `op-node` and `op-geth` must be launched before the specified times. All timestamps can be set to the same value, but due to specification constraints, `0` cannot be used.
133
+
```dotenv
134
+
# Block timestamps for upgrades (empty = no upgrade)
135
+
OP_OVERRIDE_CANYON=
136
+
OP_OVERRIDE_DELTA=
137
+
OP_OVERRIDE_ECOTONE=
138
+
OP_OVERRIDE_FJORD=
139
+
OP_OVERRIDE_GRANITE=
110
140
```
111
141
142
+
*Example command to get timestamp 10 minutes ahead*: `expr $(date +%s) + 600`
143
+
144
+
> [!IMPORTANT]
145
+
> **Do not modify timestamps after upgrades have been applied. In particular, never re-change to a future.**
146
+
112
147
#### Generate the Genesis Block
113
148
Ensure the successful generation of the genesis block (number=0):
114
149
```shell
115
-
docker-compose run --rm --no-deps op-geth init /assets/genesis.json
0 commit comments