I run a test node with an authorized identity to learn how it works. In the process, this node is disrupted many times. When I want to start with a clean slate, I stop/remove the docker container, delete all files where “app/config” is mounted, and then use the same identity to setup a new node with:
docker run --rm -e SETUP="true”…
which creates a new database and directory structure. And then I start the node. Each new setup shows a dashboard that seems to have been set zero, as if it is a new node with no history**. But is it?
- Does the network “remember” how inconsistently this identity have been running before the new setup?
- How does a node’s unreliability affect the reputation of the identity or the associated ip address, or even the email address in the prefix of the token used to authorize the identity?
- How does a dented reputation affect the node’s future performance and payouts?
**except for the “Disk Space Used This Month” measured in GB*h.