Skip to content

Commit b9b17a2

Browse files
committed
Clarify the usage of an announcer machine
1 parent 8642986 commit b9b17a2

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

source/guides/network/running-a-secure-symbol-node.rst

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -125,6 +125,12 @@ Then, on the **online machine**, the one that will run the node and be permanent
125125

126126
This command not only announces all required link transactions, it also checks if the links already exist, finds a good node to use for the announcement, calculates the appropriate fee and aggregates all links in a single transaction for added efficiency.
127127

128+
.. note::
129+
130+
This step (and the next one) can be performed from **any online machine**. It does not need to be the same machine that will be running the node. By doing so, the node will **never have the main private key**, not even encrypted.
131+
132+
The key will have been briefly present in *some* online machine, though. To completely avoid this use the guide in the `Offline signatures <secure-node-offline-signatures>`_ section.
133+
128134
8. If you want to enroll to any :doc:`Reward Program <../../concepts/reward-programs>`, do so now:
129135

130136
.. code-block:: bash

0 commit comments

Comments
 (0)