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: resources/plugins/simln/README.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ SimLN also requires access details for each node; however, the SimLN plugin will
13
13
14
14
````JSON
15
15
{
16
-
"id": <node_id>-lnd,
16
+
"id": <node_id>,
17
17
"address": https://<ip:port or domain:port>,
18
18
"macaroon": <path_to_selected_macaroon>,
19
19
"cert": <path_to_tls_cert>
@@ -22,11 +22,11 @@ SimLN also requires access details for each node; however, the SimLN plugin will
22
22
SimLN also supports Core Lightning (CLN). CLN nodes connection details are transfered from the CLN node to SimLN node during launch-activity processing.
### Launch activity definitions from within `network.yaml`
41
41
When you initialize a new Warnet network, Warnet will create a new `network.yaml` file. If your `network.yaml` file includes lightning nodes, then you can use SimLN to produce activity between those nodes like this:
@@ -75,7 +75,7 @@ nodes:
75
75
- id:
76
76
block: 300
77
77
index: 1
78
-
target: tank-0004-lnd
78
+
target: tank-0004-ln
79
79
capacity: 100000
80
80
push_amt: 50000
81
81
@@ -89,7 +89,7 @@ nodes:
89
89
- id:
90
90
block: 300
91
91
index: 2
92
-
target: tank-0005-lnd
92
+
target: tank-0005-ln
93
93
capacity: 50000
94
94
push_amt: 25000
95
95
@@ -103,7 +103,7 @@ plugins:
103
103
postDeploy:
104
104
simln:
105
105
entrypoint: "../../plugins/simln"# This is the path to the simln plugin folder (relative to the network.yaml file).
0 commit comments