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: docs/root/manual/getting-started/run-signer-node.md
+97-1
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,7 @@ In this guide, you will learn how to set up a **Mithril Signer** within the stak
27
27
- On `mainnet`, you **must** run the **production** deployment where the **Mithril Signer** runs on the **Cardano block producer** machine and the **Mithril relay** runs on the **Cardano relay** machine. **Note** that you can run the **production** deployment on `testnet`.
28
28
- You can also run **naive** deployment, where the **Mithril Signer** runs on the **Cardano relay** machine. This is possible in the testnet environment only, and does not require setting up a **Mithril relay**.
29
29
30
+
In the current setup, you don't need to install a Mithril Aggregator.
30
31
:::
31
32
32
33
:::caution
@@ -231,6 +232,23 @@ Replace this value with the correct user. We assume that the user used to run th
231
232
*`RELAY_ENDPOINT=http://192.168.1.50:3128`**(optional)**: this is the endpoint of the **Mithril relay**, which is required for **production** deployment only. For **naive** deployment, do not set this variable in your environment file.
232
233
:::
233
234
235
+
:::tip
236
+
237
+
You can find below the `ERA_READER_ADAPTER_TYPE` and `ERA_READER_ADAPTER_PARAMS` values for **release-preprod**. Other values must be replaced as explained in the caution box above.
238
+
239
+
* In the `/opt/mithril/mithril-signer/service.env` env file:
You can verify that your signer node is correctly configured and registered by checking your signer node logs or by running this command :
489
+
490
+
```bash
491
+
if grep -q "STATE MACHINE: new cycle: Registered"**YOUR_SIGNER_NODE_LOGS_PATH**;then
492
+
echo">> Your signer node is registered"
493
+
else
494
+
echo">> Your signer node is not registered"
495
+
fi
496
+
```
497
+
430
498
There is a delay of `2` epochs between the registration of the signer node and its ability to generate individual signatures. This delay is further explained in the [Mithril certificate chain in depth](https://mithril.network/doc/mithril/mithril-protocol/certificates) documentation.
431
499
432
-
Once this delay has passed, you should be able to observe your `PoolId` listed in some of the certificates accessible on the [`Mithril Explorer`](https://mithril.network/explorer).
500
+
Once this delay has passed, you should be able to observe your `PoolId` listed in some of the certificates accessible on the [`Mithril Explorer`](https://mithril.network/explorer) or by running the following command :
0 commit comments