[bisq-network/bisq-docs] Updating the "How to Seednode" docs (#148)

[Florian Reimair]

freimair commented on this pull request.



>  
-A default seed node can be blocked by a network message in case the seed node does not fulfill the required quality.
+- find yourself a deputy in case you are on not available (travel, holiday, others, ...). Usually, on of the developers is there to help. Just inform them on your setup and all is good.
+- keep the server up and running, including patching and hardening the operating system
+- keep the seed node software up to date
+- keep an eye on the Bisq's communication channels for updates, issues, countermeasures,... (see <<Getting in Touch>>)
+- keep an eye on the logs of the seed node and the operating system, and act if something shows up
+- if necessary, report and escalate (see <<Getting in Touch>>)
+- set up a bond of 2000 BSQ to get the privilege to run a seed node. In case of severe failure of service, the bond gets confiscated (burned).

you sure? I took the 2000 from the previous version (see line 105 of the original howto). If 20000 is the correct number, do you have any reference to back it up?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq-docs/pull/148#discussion_r308020427
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190728/e8a05105/attachment.html>