@@ -63,7 +63,7 @@ information is required:
6363```
6464{
6565 "id": <node_id>,
66- "address": https:// <ip:port or domain:port>,
66+ "address": <ip:port or domain:port>,
6767 "macaroon": <path_to_selected_macaroon>,
6868 "cert": <path_to_tls_cert>
6969}
@@ -74,14 +74,13 @@ Whereas for CLN nodes, the following information is required:
7474```
7575{
7676 "id": <node_id>,
77- "address": https:// <ip:port or domain:port>,
77+ "address": <ip:port or domain:port>,
7878 "ca_cert": <path_to_ca_cert>,
7979 "client_cert": <path_to_client_cert>,
8080 "client_key": <path_to_client_key>
8181}
8282```
8383
84- ** Note that node addresses must be declare with HTTPS transport, i.e. < https://ip-or-domain:port > **
8584
8685Payment activity can be simulated in two different ways:
8786* Random activity: generate random activity on the ` nodes ` provided,
@@ -102,13 +101,13 @@ not "drain" from the simulation.
102101 "nodes": [
103102 {
104103 "id": "Alice",
105- "address": "https:// 127.0.0.1:10011",
104+ "address": "127.0.0.1:10011",
106105 "macaroon": "/path/admin.macaroon",
107106 "cert": "/path/tls.cert"
108107 },
109108 {
110109 "id": "0230a16a05c5ca120136b3a770a2adfdad88a68d526e63448a9eef88bddd6a30d8",
111- "address": "https:// localhost:10013",
110+ "address": "localhost:10013",
112111 "ca_cert": "/path/ca.pem",
113112 "client_cert": "/path/client.pem",
114113 "client_key": "/path/client-key.pem"
@@ -177,26 +176,26 @@ The example simulation file below sets up the following simulation:
177176 "nodes": [
178177 {
179178 "id": "Alice",
180- "address": "https:// localhost:10011",
179+ "address": "localhost:10011",
181180 "macaroon": "/path/admin.macaroon",
182181 "cert": "/path/tls.cert"
183182 },
184183 {
185184 "id": "0230a16a05c5ca120136b3a770a2adfdad88a68d526e63448a9eef88bddd6a30d8",
186- "address": "https:// 127.0.0.1:10013",
185+ "address": "127.0.0.1:10013",
187186 "ca_cert": "/path/ca.pem",
188187 "client_cert": "/path/client.pem",
189188 "client_key": "/path/client-key.pem"
190189 },
191190 {
192191 "id": "Erin",
193- "address": "https:// localhost:10012",
192+ "address": "localhost:10012",
194193 "macaroon": "/path/admin.macaroon",
195194 "cert": "/path/tls.cert"
196195 },
197196 {
198197 "id": "Frank",
199- "address": "https:// localhost:10014",
198+ "address": "localhost:10014",
200199 "macaroon": "/path/admin.macaroon",
201200 "cert": "/path/tls.cert"
202201 }
@@ -232,7 +231,6 @@ The example simulation file below sets up the following simulation:
232231}
233232```
234233
235- ** Note that node addresses must be declare with HTTPS transport, i.e < https://ip-or-domain > **
236234
237235Nodes can be identified by their public key or an id string (as
238236described above). Activity sources and destinations may reference the
0 commit comments