@@ -63,7 +63,7 @@ information is required:
63
63
```
64
64
{
65
65
"id": <node_id>,
66
- "address": https:// <ip:port or domain:port>,
66
+ "address": <ip:port or domain:port>,
67
67
"macaroon": <path_to_selected_macaroon>,
68
68
"cert": <path_to_tls_cert>
69
69
}
@@ -74,14 +74,13 @@ Whereas for CLN nodes, the following information is required:
74
74
```
75
75
{
76
76
"id": <node_id>,
77
- "address": https:// <ip:port or domain:port>,
77
+ "address": <ip:port or domain:port>,
78
78
"ca_cert": <path_to_ca_cert>,
79
79
"client_cert": <path_to_client_cert>,
80
80
"client_key": <path_to_client_key>
81
81
}
82
82
```
83
83
84
- ** Note that node addresses must be declare with HTTPS transport, i.e. < https://ip-or-domain:port > **
85
84
86
85
Payment activity can be simulated in two different ways:
87
86
* Random activity: generate random activity on the ` nodes ` provided,
@@ -102,13 +101,13 @@ not "drain" from the simulation.
102
101
"nodes": [
103
102
{
104
103
"id": "Alice",
105
- "address": "https:// 127.0.0.1:10011",
104
+ "address": "127.0.0.1:10011",
106
105
"macaroon": "/path/admin.macaroon",
107
106
"cert": "/path/tls.cert"
108
107
},
109
108
{
110
109
"id": "0230a16a05c5ca120136b3a770a2adfdad88a68d526e63448a9eef88bddd6a30d8",
111
- "address": "https:// localhost:10013",
110
+ "address": "localhost:10013",
112
111
"ca_cert": "/path/ca.pem",
113
112
"client_cert": "/path/client.pem",
114
113
"client_key": "/path/client-key.pem"
@@ -177,26 +176,26 @@ The example simulation file below sets up the following simulation:
177
176
"nodes": [
178
177
{
179
178
"id": "Alice",
180
- "address": "https:// localhost:10011",
179
+ "address": "localhost:10011",
181
180
"macaroon": "/path/admin.macaroon",
182
181
"cert": "/path/tls.cert"
183
182
},
184
183
{
185
184
"id": "0230a16a05c5ca120136b3a770a2adfdad88a68d526e63448a9eef88bddd6a30d8",
186
- "address": "https:// 127.0.0.1:10013",
185
+ "address": "127.0.0.1:10013",
187
186
"ca_cert": "/path/ca.pem",
188
187
"client_cert": "/path/client.pem",
189
188
"client_key": "/path/client-key.pem"
190
189
},
191
190
{
192
191
"id": "Erin",
193
- "address": "https:// localhost:10012",
192
+ "address": "localhost:10012",
194
193
"macaroon": "/path/admin.macaroon",
195
194
"cert": "/path/tls.cert"
196
195
},
197
196
{
198
197
"id": "Frank",
199
- "address": "https:// localhost:10014",
198
+ "address": "localhost:10014",
200
199
"macaroon": "/path/admin.macaroon",
201
200
"cert": "/path/tls.cert"
202
201
}
@@ -232,7 +231,6 @@ The example simulation file below sets up the following simulation:
232
231
}
233
232
```
234
233
235
- ** Note that node addresses must be declare with HTTPS transport, i.e < https://ip-or-domain > **
236
234
237
235
Nodes can be identified by their public key or an id string (as
238
236
described above). Activity sources and destinations may reference the
0 commit comments