Skip to content

Conversation

@aesedepece
Copy link
Member

@aesedepece aesedepece commented Jun 16, 2020

This is rebased upon #60

Close #62
Close #63

@aesedepece aesedepece marked this pull request as draft June 16, 2020 17:06
@aesedepece aesedepece force-pushed the fix-62 branch 2 times, most recently from d366d41 to 3a5dbfa Compare June 17, 2020 10:23
@aesedepece aesedepece marked this pull request as ready for review June 17, 2020 12:56
@aesedepece aesedepece force-pushed the fix-62 branch 4 times, most recently from 6599834 to e8d1338 Compare June 18, 2020 13:36
Copy link
Contributor

@mariocao mariocao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Super clear!!! 👍


As soon as the `witnet_node` container is up, it will do the following things in order:

1. Try to **open connections to other nodes** in the network. It needs 8 "outbound" connections. This should take from several seconds to a few minutes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. Try to **open connections to other nodes** in the network. It needs 8 "outbound" connections. This should take from several seconds to a few minutes.
1. Try to **open connections to other nodes** in the network. It needs 12 "outbound" connections. This should take from several seconds to a few minutes.

Now I think it is 12 by default, isn't it?

```


!!! tip "Reputation is tricky"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we could add that identity might appear as not active, which is perfectly normal in case the node wasn't lucky to mine a block or participate in a data request.

Comment on lines +203 to +206
!!! danger "Never use the same master key on multiple nodes at once"
Operating multiple nodes with the same master key is a terrible idea.
You may find your nodes exposed to double-spend issues and severe slashing.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤟

@aesedepece aesedepece merged commit 893466a into witnet:master Jul 23, 2020
gitbook-com bot pushed a commit that referenced this pull request Mar 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Documentation about node operator first steps Update run-a-node tutorial and re-sync medium post

3 participants