@@ -47,6 +47,7 @@ The following steps are expected to be done **before** the ceremony.
47
47
$ sudo cp -f ./dcld -t /usr/bin
48
48
$ sudo chown " <dcl-user>" /usr/bin/dcld
49
49
$ sudo chmod u+x /usr/bin/dcld
50
+
50
51
# verification
51
52
$ dcld version
52
53
` ` `
@@ -77,7 +78,8 @@ The following steps are expected to be done **before** the ceremony.
77
78
78
79
3.1. Share VN' s IP address
79
80
80
- 3.2. Share VN' s ` id` (` id` field in ` dcld status` command output)
81
+ 3.2. Share VN' s ` id` (` node_id` field in ` dcld init` command output
82
+ or ` id` field in ` dcld status` command output in case node is running)
81
83
82
84
4. ** Generate NodeAdmin keys**
83
85
@@ -93,9 +95,9 @@ The following steps are expected to be done **before** the ceremony.
93
95
94
96
4.3. Share generated ` address` and ` pubkey` (in Slack or in a special doc).
95
97
96
- ` address` and ` pubkey` can be found in the ` dcld keys show " <key-name>" ` output.
98
+ ` address` and ` pubkey` can be found in the ` dcld keys show --output text " <key-name>" ` output.
97
99
98
- 5. ** \ [ Optional] Generate Trustee keys**
100
+ 5. ** [Optional] Generate Trustee keys**
99
101
100
102
5.1. Choose a machine where Trustee keys will be hold (it can be either VN Node, or a separate machine with ` dcld` binary)
101
103
@@ -109,13 +111,13 @@ The following steps are expected to be done **before** the ceremony.
109
111
110
112
5.3. Share generated ` address` and ` pubkey` (in Slack or in a special doc).
111
113
112
- ` address` and ` pubkey` can be found in the ` dcld keys show " <key-name>" ` output.
114
+ ` address` and ` pubkey` can be found in the ` dcld keys show --output text " <key-name>" ` output.
113
115
114
- 6. ** \ [ Optional] Configure ON Nodes**
116
+ 6. ** [Optional] Configure ON Nodes**
115
117
116
118
Do steps 1.1 - 1.7 for all ON Nodes.
117
119
118
- 7. \ [ CSA Only] Create ` persistent_peers.txt` file containing ` < node1-ID> @< node1-IP> :26656,...` for all VNs. Share in Slack/doc.
120
+ 7. [CSA Only] Create ` persistent_peers.txt` file containing ` < node1-ID> @< node1-IP> :26656,...` for all VNs. Share in Slack/doc.
119
121
120
122
# # II. Ceremony: Genesis Node (CSA Only)
121
123
@@ -132,14 +134,14 @@ The following steps are expected to be done **during** the ceremony.
132
134
# fetch the helper script
133
135
curl -L -O https://raw.githubusercontent.com/zigbee-alliance/distributed-compliance-ledger/master/deployment/scripts/test_peers_conn
134
136
135
- # run, by default it expectes persistent_peers.txt in the current directory
137
+ # run, by default it expects persistent_peers.txt in the current directory
136
138
./test_peers_conn
137
139
` ` `
138
140
139
141
8.3. Run genesis VN
140
142
141
143
` ` ` bash
142
- ./run_dcl_node -t genesis -c testnet-2.0 --gen-key-name " <node-admin-key>" [--gen-key-name-trustee " <trustee-key>" ] node0
144
+ ./run_dcl_node -t genesis -c testnet-2.0 --gen-key-name " <node-admin-key>" [--gen-key-name-trustee " <trustee-key>" ] " <node-name> "
143
145
` ` `
144
146
145
147
8.4. Put genesis file to GitHub (` zigbee-alliance/distributed-compliance-ledger/master/deployment/persistent_chains/testnet-2.0/genesis.json` )
@@ -153,16 +155,30 @@ The following steps are expected to be done **during** the ceremony.
153
155
9.1. A Trustee proposes a NodeAdmin account
154
156
155
157
` ` ` bash
156
- dcld tx auth propose-add-account --address=" <bench32 encoded string>" --pubkey=" <protobuf JSON encoded>" --roles=NodeAdmin --from=" <account-name>"
158
+ dcld tx auth propose-add-account --address=' <bench32 encoded string>' --pubkey=' <protobuf JSON encoded>' --roles=NodeAdmin --from=' <account-name>'
157
159
` ` `
158
160
159
161
9.2. Trustees approve the NodeAdmin account
160
162
161
163
` ` ` bash
162
- dcld tx auth approve-add-account --address=" <bench32 encoded string>" --from=" <account-name>"
164
+ dcld tx auth approve-add-account --address=' <bench32 encoded string>' --from=' <account-name>'
165
+ ` ` `
166
+
167
+ 10. ** [Optional] Add Trustee account**
168
+
169
+ 12.1. A Trustee proposes Trustee account
170
+
171
+ ` ` ` bash
172
+ dcld tx auth propose-add-account --address=' <bench32 encoded string>' --pubkey=' <protobuf JSON encoded>' --roles=Trustee --from=' <account-name>'
173
+ ` ` `
174
+
175
+ 12.2. Trustees approve Trustee account
176
+
177
+ ` ` ` bash
178
+ dcld tx auth approve-add-account --address=' <bench32 encoded string>' --from=' <account-name>'
163
179
` ` `
164
180
165
- 10 . ** Run VN node**
181
+ 11 . ** Run VN node**
166
182
167
183
10.1. Download genesis
168
184
@@ -179,7 +195,7 @@ The following steps are expected to be done **during** the ceremony.
179
195
# fetch the helper script
180
196
curl -L -O https://raw.githubusercontent.com/zigbee-alliance/distributed-compliance-ledger/master/deployment/scripts/test_peers_conn
181
197
182
- # run, by default it expectes persistent_peers.txt in the current directory
198
+ # run, by default it expects persistent_peers.txt in the current directory
183
199
./test_peers_conn
184
200
` ` `
185
201
@@ -199,7 +215,7 @@ The following steps are expected to be done **during** the ceremony.
199
215
200
216
(once transaction is successfully written you should see ` " code" : 0` in the JSON output.)
201
217
202
- 11 . ** VN Deployment Verification**
218
+ 12 . ** VN Deployment Verification**
203
219
204
220
11.1. Check the account presence on the ledger: ` dcld query auth account --address=" <address>" ` .
205
221
@@ -209,20 +225,6 @@ The following steps are expected to be done **during** the ceremony.
209
225
210
226
11.4. Make sure the VN participates in consensus: ` dcld query tendermint-validator-set` must contain the VN' s address.
211
227
212
- 12. **\[Optional] Add Trustee account**
213
-
214
- 12.1. A Trustee proposes Trustee account
215
-
216
- ```bash
217
- dcld tx auth propose-add-account --address="<bench32 encoded string>" --pubkey="<protobuf JSON encoded>" --roles=Trustee --from="<account-name>"
218
- ```
219
-
220
- 12.2. Trustees approve Trustee account
221
-
222
- ```bash
223
- dcld tx auth approve-add-account --address="<bench32 encoded string>" --from="<account-name>"
224
- ```
225
-
226
228
## IV. Post-Ceremony: For every Observer Node
227
229
228
230
The following steps can be done **after** the ceremony.
@@ -278,7 +280,7 @@ The following steps can be done **after** the ceremony.
278
280
```
279
281
* Useful commands
280
282
* keys:
281
- * `dcld keys show "<name>"`: to get address and pubkey for a keyname
283
+ * `dcld keys show --output text "<name>"`: to get address and pubkey for a keyname
282
284
* node status:
283
285
* `systemctl status dcld`: to get the node service status.
284
286
* `journalctl -u dcld.service -f`: to see node logs.
0 commit comments